because it has taken so long, and mostly I've seen people blaming "doomsdayers", I stopped assuming it would 5/
-
-
eventually get better. But it seems it has. I think a strong statement from core about this would help. 6/6
2 replies 0 retweets 0 likes -
I'm not entirely sure what the strong statement you're looking for would actually include.
1 reply 0 retweets 2 likes -
"we made some mistakes in the py3.0 timeframe, but have since changed our philosophy about the migration" 1/
1 reply 0 retweets 0 likes -
"our new philosophy is that single-codebase + six is the best migration strategy." 2/
1 reply 0 retweets 0 likes -
"many libraries have already done so, and if you find it difficult for some reason, we are open to further 3/
1 reply 0 retweets 0 likes -
changes in both py2.7 and py3.x to smooth the transition path" 4/4
1 reply 0 retweets 0 likes -
fwiw single code base is now documented as the right way - https://docs.python.org/3/howto/pyporting.html …
2 replies 0 retweets 3 likes -
reading through this -- no strong statement of what to do. modernize + six seems like the right porting default
1 reply 0 retweets 0 likes -
in Ruby, one of the hardest things was getting C libs updated. http://yehudakatz.com/2010/05/05/ruby-1-9-encodings-a-primer-and-the-solution-for-rails/ …
2 replies 0 retweets 1 like
The really boring thing in the previous tweet was a lot of work but made a huge diff in porting success.
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.