Earlier quoted context omitted.
It’s journalistic, but is not misleading. “[python-committers] Transfer of power - Guido van Rossum” would be more verbatim, but I think the title is okay.
Sigh I'm not saying it's not okay in this case, I'm saying that I believe this would've been disallowed before because we didn't want it to be up to people's judgement whether it is okay or not.
“I'm basically giving myself a permanent vacation from being BDFL”
251–260 of 764 posts
Re: “I'm basically giving myself a permanent vacation from being BDFL”
#252Earlier quoted context omitted.
> The problem with the C-style of assignments is that it leads to this classic error: if(x = 0) {...} yeah, if you code on 20 years old compilers with no warnings. GCC 4.1 warns about this (with -Wall) and Clang 3.4 warns about this too, without any warning flag.
Not having a problem in the first place is preferable to fighting it with tools. == vs = is a classic mistake that I'm sure every C programmer has wasted some time on. (I'm just undecided if I prefer dealing with this very problem occasionally, or choosing either of the verbosity of := assignments or the non-orthogonality of = assignment statements plus := assignment expressions.)
Re: “I'm basically giving myself a permanent vacation from being BDFL”
#253> I don't ever want to have to fight so hard for a PEP and find that so many people despise my decisions. Leading a large open source project must be terrible in this age of constant outrage :-(
It's not the outrage, it's the entitlement. People have always been outraged, the major difference I've seen is the rampant sense of entitlement. I'm not sure if it's a result of bad parenting or something else, but it's slowly becoming a major issue for the entirety of the human race.
I think social media is responsible for breeding this sense of entitlement among people.
Re: “I'm basically giving myself a permanent vacation from being BDFL”
#254Earlier quoted context omitted.
> Python 3 breakage and async turned out to be prescient, fantastic decisions. Async maybe. Python 3 breakage? Did you forgot the /s tag?
No, the bad decision was treating bytes and strings interchangeably in the first place. 99% of the hardest to fix breakage was due to that, and it was the right call to pay that price all at once.
Until way too recently essentially all Python code couldn't handle basic SSL/TLS certificate validation for Internationalized Domain Names. Once you understand what's going on, this situation is a no brainer: In order to connect to a machine named X, we must have turned X into DNS A-labels that we could look up, and we can treat those as bytes. The certificate must have SAN dnsNames matching its names, and those too are written as A-labels. So we can almost just compare the literal bytes (actually DNS A-labels are "case-insensitive" so we need to handle that, and the asterisk "wild card")
But Python, in its wisdom, defined this API to take a string, and strings, as you observe, aren't bytes. So instead of the above unarguable approach they wasted precious months trying to figure out how best to turn the A-labels from a SAN dnsName into Unicode strings, which isn't even the right problem to solve.
Eventually sanity prevailed: https://bugs.python.org/issue28414
Re: “I'm basically giving myself a permanent vacation from being BDFL”
#255Earlier quoted context omitted.
Yeah vacation isn't work time
It depends. My experience has been that contractors usually don't mind working on vacation while on a cruise whereas salaried people are like "I'm dead; don't reach me."
Re: “I'm basically giving myself a permanent vacation from being BDFL”
#256Earlier quoted context omitted.
I'll probably never switch for personal use. The print statement change is intolerable to me. It would have cost them nothing to just leave the old syntax in. It's supposed to be a quick and convenient scripting language and they're actively working to make it more verbose and less convenient. I also still don't like not being able to use "string" objects as dumb byte containers, like I do with an IRC bot that doesn'…
Syntax regularity is infinitely more important than scripting convenience.
You should be supporting return being made into a function too, right? That would be much more regular.
Reminder that a guideline of python was supposed to be "practicality beats purity" which is in stark contrast to the changes to print and strings. [1] Reminds me of the gradual shift of the message on the wall in Animal Farm from "four legs good, two legs bad" to "four legs good, two legs better."
Re: “I'm basically giving myself a permanent vacation from being BDFL”
#257Earlier quoted context omitted.
> Python 3 breakage and async turned out to be prescient, fantastic decisions. The jury is still out on the Python 3 decision, to be honest. Heck, Python 2 is still officially supported until 2020. Python 3 adoption is increasing, but the instability and breakage that it introduced caused a lot of knock-on effects throughout the Python community that held it back and hindered its adoption and mindshare. It'll take a…
> The jury is still out on the Python 3 decision, to be honest. It's not. Python 3 has overtaken 2 and there is no stopping migration to it now. Python 3.7 is a lot better than 2.7. Just on memory use alone, 3.7 is massively better. Sure, there will be some hold outs on 2.7 for a long time. That's fine. Also, this is not the say that migration from 2 to 3 was handled well. It wasn't. Python 3.0 should have had backwa…
The Python 3 Readiness Project now lists [341](http://py3readiness.org/) of the 360 most common packages as Python 3 compatible.
Even that's underselling it really. For example it lists BeautifulSoup as not converted, but the link goes to BeautifulSoup 3.2.1. However, BeautifulSoup4 works great on Python 3. And for MySQL there's mysqlclient and several others, and since database packages usually follow PEP 249 pretty closely its very easy to switch. So in reality, rather than 341/360, its more like "everything worth converting has been converted." Or just "everything" for short.
Re: “I'm basically giving myself a permanent vacation from being BDFL”
#258Earlier quoted context omitted.
It was controversial syntax, inline assignment-as-expression. There's always a tension between "keep it simple stupid" and "let's make it better", especially when a large user demographic of Python are non-professional-programmers. Interestingly, C++ is going through the same process, with lots of great ideas being proposed, but the sum total of them being an even more complicated language (on top of what is probably…
> Python 3 breakage and async turned out to be prescient, fantastic decisions. The jury is still out on the Python 3 decision, to be honest. Heck, Python 2 is still officially supported until 2020. Python 3 adoption is increasing, but the instability and breakage that it introduced caused a lot of knock-on effects throughout the Python community that held it back and hindered its adoption and mindshare. It'll take a…
Meanwhile C22 work is ongoing.
Re: “I'm basically giving myself a permanent vacation from being BDFL”
#259Earlier quoted context omitted.
O_o I wonder how many times I've spoken to someone and didn't realize who it was/how important they were because of the anonymity of the internet.
When I was much younger I started building a ray casting engine. I was having trouble wrapping my brain around how to render the floors so ... I emailed Ken Silverman. It escapes me now _why_ I emailed him. I certainly had no idea the gravity of who he was (for those also unaware, he is perhaps most famous for creating the Build engine used in games like Duke Nukem 3D). I believe I was under the false assumption at t…
Re: “I'm basically giving myself a permanent vacation from being BDFL”
#260Earlier quoted context omitted.
OTOH, way back, when I had a TV receiver card by Hauppage, and a new Linux kernel broke something, I posted a description of my troubles on Usenet, and within 24 hours, the person who had written the Video4Linux subsystem replied asking for more details (which I gladly provided), and a few days later, the bug was fixed. That, I think, was the most awesome "customer support" experience of my life. I did make a point o…
I had the same experience. Suddenly Emacs Gnus reader stopped working, about 11:00 on a Friday morning. I posted the bug and had a reply from Lars Ingebrigtsen with an explanation and a workaround by 13:00. I think it was fixed by the beginning of the following week. My experience of trying to get help from Microsoft on the other hand is, well let's just say not quite so impressive; they kept me on hold for 45 minute…