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

Using django six rather then maintaining one #112

Closed
auvipy opened this issue May 29, 2016 · 3 comments
Closed

Using django six rather then maintaining one #112

auvipy opened this issue May 29, 2016 · 3 comments

Comments

@auvipy
Copy link
Contributor

auvipy commented May 29, 2016

is there any reason still to maintain one? @mtford90 @avelis looking for inputs and I will work to update the code to django six if both of you agree

@avelis
Copy link
Collaborator

avelis commented May 31, 2016

@auvipy One reason I think this is this way is to ensure a version of six a the library is using vs being overridden to a different version in a virtualenv.

With that said, if you feel it is easier to move onto a newer version of six I am not against that either.

@auvipy
Copy link
Contributor Author

auvipy commented May 31, 2016

I will try my proposed changes and send a PR. then lets see

@hanleyhansen
Copy link
Member

The old six should be completely removed now. The last remnants were taken care of in my pr: #122

@auvipy auvipy closed this as completed Jul 8, 2016
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

No branches or pull requests

3 participants