https://wiki.python.org/moin/PortingPythonToPy3k … also, why are Django's custom additions to six not upstreamed?
@ubernostrum I'm happy to admit that my perspective on this was missing details; however 1/
-
-
I'm pretty keyed in on stuff like this, and am often forced to use Python through dependencies (gyp, e.g.) 2/
-
and despite trying to keep on top of this, I have never found a canonical description of the current 3/
-
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/
- 19 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.