This blog post about mercurial’s Python 3 port is definitely worth reading. https://gregoryszorc.com/blog/2020/01/13/mercurial%27s-journey-to-and-reflections-on-python-3/ …
-
Quoting: "Look, I know it is easy for me to armchair quarterback and critique with the benefit of hindsight/ignorance. I'm sure there is a lot of nuance here. I'm sure there was disagreement within the Python community over a lot of these issues"
Actually there was too little pushback early on. People generally didn't really anticipate this. We can safely conclude the language developers didn't anticipate it fully, otherwise they wouldn't have bet on 2to3.
-
-
There were quite a few people who pushed back myself included. However a lot of why that was not more vocal was that there was just no platform to voice these concerns. It was considered fouling one's own nest.
-
I know you pushed back, and others did too (thank you). I was referring to the early days. I remember Guido polling the audience at a EuroPython about who was going to use Python 3 (not out yet) and just about everyone raised their hand. The question might have been ambiguous.
- Još 6 drugih odgovora
Novi razgovor -
-
-
Speaking truth to power is costly. So even some of those who had doubts did not speak. But I think most really didn't anticipate it enough and couldn't comprehend the few warnings there were.
-
The excitement to do cool new stuff also can blind people a little. Same for me concerning Zope 3 initially.
Kraj razgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.