then some common pain points became obvious once people started actually porting. that's why 2to3 says what it does too
"many libraries have already done so, and if you find it difficult for some reason, we are open to further 3/
-
-
changes in both py2.7 and py3.x to smooth the transition path" 4/4
-
fwiw single code base is now documented as the right way - https://docs.python.org/3/howto/pyporting.html …
-
reading through this -- no strong statement of what to do. modernize + six seems like the right porting default
-
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/ …
-
I don't think you're trolling. Serious Q: How much of Ruby is touched by what Rails does.
-
From the outside it looks like as Rails goes so does Ruby.
-
e.g. If Rails is pushing people to migrate people will do it to avoid losing compat with Rails.
- 10 more replies
New conversation -
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.