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.

Sign up for GitHub

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

Jump to bottom

Decide python 3 strategy #27

Closed
jamescasbon opened this issue Feb 19, 2012 · 1 comment
Closed

Decide python 3 strategy #27

jamescasbon opened this issue Feb 19, 2012 · 1 comment

Comments

@jamescasbon
Copy link
Owner

Should we try and use the same codebase or use one of the tools? Should we use six to help with the codebase? Which versions of python2 so we need to support?

I ran 2to3 and applied a few more fixes on the python3 branch. Nothing much to worry about except next(gen) rather than gen.next(), also some utf problems with the gzip code.
@jamescasbon jamescasbon mentioned this issue Feb 22, 2012
Closed
@jamescasbon
Copy link
Owner Author

Fixed in 0.4.4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jamescasbon