simple example: restore support for the old-style print statement.
-
-
new-style print is already supported in 2.6+ and is one of the easiest things to translate automatically
2 replies 0 retweets 5 likes -
auto-translation wouldn't have worked for Rails and hasn't worked for Python. Single codebase is important.
1 reply 0 retweets 0 likes -
it IS single codebase. print() works in both python 2 and python 3.
1 reply 0 retweets 4 likes -
I'd ask the Django folks what would help, but the philosophy of "don't try to maintain one codebase" (in the docs) 1/
1 reply 0 retweets 1 like -
actually does reflect the status quo wrt Django, which is in fact slowing adoption down quite a bit. 2/
2 replies 0 retweets 0 likes -
Django is 2/3 in single codebase and has been for years. So, um, lolwut?
1 reply 0 retweets 0 likes -
some of what I said was wrong, but a lot was pointing at an earlier timeframe.
2 replies 0 retweets 0 likes -
Meanwhile people who read manufactured-controversy pieces about it are prob still on Py1.5.
2 replies 0 retweets 1 like -
Replying to @ubernostrum @wycats and
"new-style classes" were fatal mistake, y'know. Or would've been if Medium and Twitter existed back then.
1 reply 0 retweets 2 likes
you're not asking me, but I think new-style classes were great; I'm talking about compat and NSC had it.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.