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

Either don't use six or support an older version (like 1.4) #583

Closed
d0ugal opened this Issue Jun 2, 2015 · 3 comments

Comments

Projects
None yet
2 participants
@d0ugal
Member

d0ugal commented Jun 2, 2015

This is causing quite a few users problems, particularly on OSX.

See #576, #590 and a mailing list post. There are possible workarounds for this in the issues and email thread.

@d0ugal d0ugal added the Bug label Jun 2, 2015

@d0ugal d0ugal added this to the 0.14.0 milestone Jun 2, 2015

@d0ugal d0ugal modified the milestone: 0.14.0 Jun 2, 2015

@samhatfield

This comment has been minimized.

Contributor

samhatfield commented Jun 3, 2015

For what it's worth, I'm working on Linux Mint and I also had some issues. My system was using the six stored in /usr/lib/python2.7/dist-packages, which was about 1.5, even if a newer one was installed to /usr/local/lib/python2.7/dist-packages via pip. Eventually I had to rename the six files in the first directory to force it to use pip's version.

@d0ugal

This comment has been minimized.

Member

d0ugal commented Jun 3, 2015

@samhatfield Thanks, we are trying to resolve this ASAP in #585. I'll probably roll a new release shortly after as this is causing issues for lots of people. I had no idea six was treated specially by different OSes.

@d0ugal

This comment has been minimized.

Member

d0ugal commented Jun 5, 2015

This is now fixed in master, I'll be working on releasing very soon.

@d0ugal d0ugal closed this Jun 5, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment