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

Don't use six for a configparser. #26

Merged
merged 1 commit into from Mar 14, 2014
Merged

Don't use six for a configparser. #26

merged 1 commit into from Mar 14, 2014

Conversation

Wilfred
Copy link
Collaborator

@Wilfred Wilfred commented Mar 14, 2014

setup.py develop installs our dependencies, including six. So we can't
use six's configparser to parse our dependencies, because we haven't
installed it yet!

`setup.py develop` installs our dependencies, including six. So we can't
use six's configparser to parse our dependencies, because we haven't
installed it yet!
@Wilfred
Copy link
Collaborator Author

Wilfred commented Mar 14, 2014

Jenkins is happy; I'm happy.

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.

None yet

1 participant