Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update to distribute 0.6.21 #15

Closed
pytoxbot opened this issue Sep 17, 2016 · 4 comments
Closed

update to distribute 0.6.21 #15

pytoxbot opened this issue Sep 17, 2016 · 4 comments

Comments

@pytoxbot
Copy link

@pytoxbot pytoxbot commented Sep 17, 2016

Currently 0.6.19 is required, but 0.6.21 has been released upstream. If tox can't be made to use whatever the latest is, it should at least be updated to 0.6.21.

@pytoxbot
Copy link
Author

@pytoxbot pytoxbot commented Sep 17, 2016

Original comment by @hpk42

tox' setup.py on trunk now depends on virtualenv (>= 1.6.4) so this should be fixed.

@pytoxbot pytoxbot closed this Sep 17, 2016
@pytoxbot
Copy link
Author

@pytoxbot pytoxbot commented Sep 17, 2016

Original comment by @hpk42

tox' setup.py on trunk now depends on virtualenv (>= 1.6.4) so this should be fixed.

@pytoxbot
Copy link
Author

@pytoxbot pytoxbot commented Sep 17, 2016

Original comment by sybren

In the mean time 0.6.24 is releases as well. My tests won't run because an indirect dependency of my code requires at least version 0.6.21

It would be very nice if we could choose/configure which version of distribute to use. Right now the install script is hardcoded in BASE64-encoding in virtualenv.py, making it virtually impossible to swap for a newer version.

@pytoxbot
Copy link
Author

@pytoxbot pytoxbot commented Sep 17, 2016

Original comment by @warsaw

Following this now that I've logged it. I reported the bug.

@tox-dev tox-dev locked and limited conversation to collaborators Jan 14, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant