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

from __future__ import absolute_import, unicode_literals #77

Closed
behdad opened this issue Jan 8, 2014 · 1 comment
Closed

from __future__ import absolute_import, unicode_literals #77

behdad opened this issue Jan 8, 2014 · 1 comment

Comments

@behdad
Copy link
Member

behdad commented Jan 8, 2014

So we get more uniform behavior between 2 and 3.
behdad added a commit that referenced this issue Jan 14, 2014
@behdad
from __future__ import absolute_import
1ae2959 
Such that our Python 2 is closer to Python 3.

Part of #77
@behdad
Copy link
Member Author

behdad commented Jan 14, 2014

Pushed absolute_import. unicode_literals is tricky and not useful.

@behdad behdad closed this as completed Jan 14, 2014
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
@behdad