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

Upgrade setuptools prior to installing dependencies #194

Closed
wants to merge 1 commit into from
Closed

Upgrade setuptools prior to installing dependencies #194

wants to merge 1 commit into from

Conversation

jaraco
Copy link

@jaraco jaraco commented Jan 25, 2017

Avoids issues where setuptools isn't in a viable state during build of other packages.

Avoids issues where setuptools isn't in a viable state during build of other packages.
@coveralls
Copy link

coveralls commented Jan 25, 2017

Coverage Status

Coverage remained the same at 57.914% when pulling aa14324 on jaraco:patch-1 into 8cd0339 on python-excel:master.

@cjw296
Copy link
Member

cjw296 commented Jan 25, 2017

That's great, but can you go through and do this on all of the affected projects?
This workaround isn't practical when you maintain as many libraries as I do :-(

@cjw296 cjw296 closed this Jan 25, 2017
@jaraco
Copy link
Author

jaraco commented Jan 25, 2017

@cjw296 I do sympathize. I maintain dozens of projects as well, and it's a real pain when there's a common mode in the methodology. I'm wondering if there's a way to automate the application of the workaround to the projects (and the subsequent removal of the workaround when it's no longer needed).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants