-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
updated python 2 vs 3 (fixes #48) #488
Conversation
It's 2014 and the core developers are still back-pedaling on APIs and other things to make the transition easier, because it's still realistically hard. |
true in some cases, which is why i only changed the following phrase
to
instead of to
:) |
|
||
`Further Reading <http://wiki.python.org/moin/Python2orPython3>`_ | ||
|
||
The difference between Python 3 and Python 2 is much greater, therefore |
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 is still true
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.
i think this paragraph is redundant, as the following one pretty much says the same.
also usually “writing code that works in both Python 2 and Python 3 is not a very complicated process.” it’s actually pretty trivial for most small libraries or programs. just import everything from __future__
and create some wrappers around APIs that use bytes on python 2 and strs on python 3, and you’re set. i think the following paragraph serves to explain that.
We're so close to getting to this point, but I don't feel that we're quite there yet. Honestly, I have been wanting to update this section for quite some time now. But, I feel like this is a little too one-sided, perhaps. Of course, the guide should be very opinionated, and rightfully so. However, I think we need to do a bit more to paint the picture of the current state of things for the readers. |
I am going to merge this, and drastically edit it. |
updated python 2 vs 3 (fixes #48)
a typo!
still a bit one-sided in one place, too, although much better than before!
eh, and many are grateful for them and can’t imagine living without them. maybe call them “controversial”? also, the two phrases “Use Python x if you love Python x” are pretty redundant, don’t you think? if they love a version, we won’t sway them with this guide! but i’m happy with it now! |
it’s 2014.