Guido van Rossum steps down as Python's BDFL, thoughts?

Well, I didn't see that one coming...but then, reading it, I'm not surprised. Having to fight tooth and nail with the community to get stuff done sucks. Good for him for taking care of himself. The Python community is strong, I have little doubt they'll pick it up from here and be awesome.

OSS burnout is real. This reeks of the feelings that are certainly very common across many projects.

I'm more involved in following the activities of the Ruby and Rails communities and I find the dialog in that community with regards to health and burnout to be pretty good at the top. I think it helps things not get so bad.

I didn't see this one coming.

Python's community is definitely a very opinionated one (but which one isn't?). It's not the first time that Guido indirectly mentions how stubborn and divided the community becomes around some PEPs.

I didn't follow closely but it seems like the process around PEP 572 has been taxing for everyone in the core team and especially Guido.

I definitely didn't see this one coming. I thought he would leave for old age or something.

Agree with @rhymes, definitely didn't see this coming. I was honestly surprised to see how divisive the PEP572 announcement was.

After attending my first PyCon this year, I was pleasantly surprised at getting confirmation of how welcoming and great the community was in general, especially after seeing a lot of toxicity in other communities. Sad to see such stress for Guido and his permanent vacation happening on a negative note vs a friendly, open transition plan.

I'm very curious what the community will look like in 2019 after a governance model and PEP approval process will be in place (hopefully?), as well as the 2.7 EOL schedule in 2020.

The core team is pretty strong and Python has a lot of interest from big companies.

In 2010 they were even talking about merging a branch of Python created by Google into the mainline: python.org/dev/peps/pep-3146/ and Guido himself worked for Google for a while, now he works at Dropbox: techcrunch.com/2012/12/07/dropbox-...

As Guido hints the core team is pretty independent from himself. I like the idea of democratizing a little bit more the PEP governance, which could also help in lowering the burnout for a single individual in charge.

If you have to fight tooth and nail to get something into your own language, are you really even its "dictator" anymore? Seems that it has very nearly transitioned to being a community project already. He is just making it official. I hope he enjoys retirement. He has earned it.

I'm excited for the positive change that will undoubtedly come in his life as a result of this choice. Project ownership is exhausting and frustrating, and I'm familiar with the way it can overwhelm a project owner's life if they aren't extremely diligent about taking time for rest and renewal. I hope he writes about his experience some day!

In India, we have a saying that "Even the gods cannot please everyone". Given that Python community is so huge and Python is being used for multiple niches like web-dev, ops, data science, embedded scripting, infosec etc many major new features may not be received in the same way. Language development is a trade-off between developer productivity and performance. Some features may increase the learning curve or be seen as against the Zen of Python.

GvR has done a great job guiding the development of Python for over 20 years. Python has probably "scaled" in the sense that it needs more people managing its future mission and goals. It will be a challenge because different people will have different visions for its future. Now that there is no BDFL, we will need to see how the PEPs are approved. Python can take some inspiration from Rust which has very active community participation in their "RFCs".

There has to be more to the story with this than what's being said in the announcement.

So true, Ben! Open-source is, and always will be community driven. Once toxicity seeps into a community, it can frustrate people!