Did Python3's more strict handling of byte and string catch any bugs? (I'm guessing "not many" because hg mostly handles byte strings)
-
-
-
Your guess is correct. The port introduced bugs because Unicode is being forced on us in areas that were previously all bytes. There are arguably some long-term benefits to Windows support, but that’s due to Python switching Windows APIs, not stricter type handling per se.
- Još 1 odgovor
Novi razgovor -
-
-
one of the big realizations I had when designing the migration tooling for rust 2018 was that it HAD to be two-step. It HAD to have a first step that gives you potentially icky code that must compile on both editions
-
And the second step can actually clean it up to be idiomatic, and also perhaps make it only work on the newer edition after figuring out and implementing this I had a much better understanding of why Python 3 went so badly
- Još 5 drugih odgovora
Novi razgovor -
-
-
wait, Python core doesn’t have consensus that the Python 3 transition was a disaster? that is a terrifying thought!


pic.twitter.com/X1DuuUkyaJ
-
Wait - there's been a transition to python3?

- Još 1 odgovor
Novi razgovor -
-
-
That was an excellent post.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
> The initial approach of Python 3 mirrors a folly that many developers and projects make: attempting a rewrite instead of performing incremental evolution. So many great insights in your write-up - Thank you for sharing!
-
The
@angular team made a similar mistake, which cost them a TON of market share
Kraj razgovora
Novi razgovor -
-
-
When I read your blog post, I was amazed how similar your experience was to mine many years ago when porting SymPy: https://ondrejcertik.blogspot.com/2013/08/how-to-support-both-python-2-and-3.html …. It truly lowered my enthusiasm for Python for years to come. I also agree with you regarding Rust.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
Č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.