"our new philosophy is that single-codebase + six is the best migration strategy." 2/
-
-
"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 -
1 reply 0 retweets 0 likes
-
I don't think you're trolling. Serious Q: How much of Ruby is touched by what Rails does.
2 replies 0 retweets 0 likes -
From the outside it looks like as Rails goes so does Ruby.
2 replies 0 retweets 0 likes -
hm I think that's a misunderstanding. The Ruby core team has always been pretty disconnected from Rails dev
1 reply 0 retweets 1 like
for the longest time, there was an intractable language barrier between the two teams. Thanks @tenderlove!
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.