right but the same shims would likely be useful for other projects, and help aid the transition.
-
-
perspective of the core team, especially around changes in mind from strong statements made around 3.0 4/
-
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
-
I'm not entirely sure what the strong statement you're looking for would actually include.
-
"we made some mistakes in the py3.0 timeframe, but have since changed our philosophy about the migration" 1/
-
"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/
-
changes in both py2.7 and py3.x to smooth the transition path" 4/4
- 17 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.