From issues-reply at bitbucket.org Tue Mar 8 20:15:08 2016 From: issues-reply at bitbucket.org (Nicholas Serra) Date: Wed, 09 Mar 2016 01:15:08 -0000 Subject: [Pytest-commit] Issue #319: Way to silence passenv variable output, or a -v 0 output param? (hpk42/tox) Message-ID: <20160309011508.1180.62293@celery-worker-101.ash1.bb-inf.net> New issue 319: Way to silence passenv variable output, or a -v 0 output param? https://bitbucket.org/hpk42/tox/issues/319/way-to-silence-passenv-variable-output-or Nicholas Serra: Hello, apologies if this has been brought up before. I'm running tox in an open source repo with Travis CI builds. I use travis's environment vars to configure some things. Issue is that tox seems to output the keys and values of any env vars specified via the passenv config. So: - Is there a way to silence the passenv env var output during a tox run? - if not, is there a way to silence all debug output? I see a verbosity flag, but it seems to only have an on and off. Thanks! From issues-reply at bitbucket.org Thu Mar 17 16:29:08 2016 From: issues-reply at bitbucket.org (Robert Collins) Date: Thu, 17 Mar 2016 20:29:08 -0000 Subject: [Pytest-commit] Issue #320: fails to detect changed dependencies, and inappropriately upgrades other dependencies. (hpk42/tox) Message-ID: <20160317202908.30607.30737@celery-worker-103.ash1.bb-inf.net> New issue 320: fails to detect changed dependencies, and inappropriately upgrades other dependencies. https://bitbucket.org/hpk42/tox/issues/320/fails-to-detect-changed-dependencies-and Robert Collins: When a venv already exists, and a projects dependencies change, tox fails to detect that, which leads to ez-install running - and thats both slower as well as liable to break because of the differences between ez-install and pip. The underlying issue is this if test:https://bitbucket.org/hpk42/tox/src/4dbfb1f1eb86b35cbd2c83461e1e294651e89cf6/tox/venv.py?at=default&fileviewer=file-view-default#venv.py-226 For a new venv, the sdist (or develop equivalently) is installed with no special parameters, which leaves it up to pip to ensure its installed properly. On subsequent tox invocations however, -U --no-deps is passed. This has two separate, interacting effects: - things installed by other commands (e.g. the installdeps commands) are inappropriately upgraded. pip does not remember that e.g. foo<5 was passed, only that foo is installed, and if foo is in the transitive dependency set of the packages dependencies, -U will cause it to be upgraded. This matters in that it can invalidate lower-bounds testing by causing deliberately-set-low versions to be upgraded. - new dependencies of the package are not installed at all if the recreation-on-changes- is not detected - this happens build systems that have metadata outside of setup.py, so that the automatic recreation is not triggered. e.g. d2to1, pbr, ... They may get installed via easy-install, so its not obvious to users that this is happening, but it certainly does. I'm not entirely sure of the history of adding these options, but since pip only installs things that are missing or incompatible, there is really no reason for them to be passed at all: just always installing as-is should be both fast and correct IMO. Separately we should look at teaching tox to more reliably detect when to recreate the venv, but as noted - this current behaviour is incorrect even when the package dependencies haven' changed. From issues-reply at bitbucket.org Wed Mar 23 02:49:42 2016 From: issues-reply at bitbucket.org (Ben Finney) Date: Wed, 23 Mar 2016 06:49:42 -0000 Subject: [Pytest-commit] Issue #321: Use HTTPS for URLs, and current home page URL (hpk42/tox) Message-ID: <20160323064942.65424.80999@celery-worker-102.ash1.bb-inf.net> New issue 321: Use HTTPS for URLs, and current home page URL http://link.bitbucket.org/wf/click?upn=8USRlNyft-2BCzk2l4Ywl6gIMTZA3-2FkNU005YAXwZhBUxuPejyQG2SYPZnI-2BfHXdmycdwisvcU9Qz-2Fds2mxjVpsZArbI9QAfyDIyUE4oNkJB4gbeHQSD-2BJpP6MPAqEssdk_S7uyiKQSq4IGfvL9cgBZOP2oUtic8BjsEXlgSOcqtlpLeHZgCtGdad5W3ia192DQ0pZtBpzP0LNwcfUs0K-2F1GqDTrbVFR2VoCEAuy9rLSzWHL6vssZ20N0aP0s-2FTQ2jQfzjw9cJQWCi0EaATD1gmOmM0Z6xLXdhjjpxXu5LEsYme0BxCPE9JlToHac0ZAO-2B3pKZLIOFc35P-2FSLRRzDJOTi2SQ3rGD5qVO5Kuwif0taE-3D Ben Finney: The URL in various documentation uses HTTP. Please discourage HTTP URLs where HTTPS ones are available. I suggest updating to the current canonical URL, ?http://link.bitbucket.org/wf/click?upn=8USRlNyft-2BCzk2l4Ywl6gBf-2FH-2FrXiTIIL-2FPAjltBDzJsy-2FTwAWbsiauoE-2FAZykjR_S7uyiKQSq4IGfvL9cgBZOP2oUtic8BjsEXlgSOcqtlpLeHZgCtGdad5W3ia192DQ0pZtBpzP0LNwcfUs0K-2F1GvuZEQTknePozkjWpkJtYYC2d3jqlSZh2BEp1zp7nB6ZLKWqVywrzbQglnf0wvTUTPKm9pToD5-2Bu9BNfZG8SVzInuuWd04UiPKt3J2U4eEwKeiYgR98HWrkhr9N05zNvIzBbeomGxHrIzKo33bpDenw-3D throughout the code base. My suggested patch for this is attached. -------------- next part -------------- An HTML attachment was scrubbed... URL: