Conversation
Big +1 to flake8! On 30 Jul 2016 5:04 p.m., "Bo Bayles" notifications@github.com wrote:
|
This is in so more drastic changes to solve #25 (keys are strings) can go forward. |
👍 I think the most difficult part of the Python 3 support is the unicode/str/bytes confusion indeed. At the time people started to request support for 3 here I didn't even use it yet (I do regularly now), so it was very hard for me to not only spot, but to correctly solve all the corner cases. Thanks for all the great work and thorough approach! |
@@ -2,6 +2,9 @@ sudo: false | |||
language: "python" | |||
python: | |||
- "2.7" | |||
- "3.3" | |||
- "3.4" | |||
- "3.5" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎉 🎉
This PR builds upon the ideas in #22 and introduces partial support for Python 3. I'm not ready to consider Python 3 "well-supported" quite yet, as #25 (keys are coerced to strings) is more visible on Python 3.
Notes:
six
as the compatibility layer, rather than writing and testing a custom compatibility layer.__future__
imports for Python 2 to try to keep behaviors between the major versions as similar as possible (I don't think they're doing much work in practice)bytes
objects in Python 3 (previously it was difficult to retrievestr
objects on Python 3).