4 ms·
The problem is, any such whats-now guide is very soon already outdated, at least in some aspects. It should be a Wiki which everyone can edit. And btw, such Wi
by albertzeyer 5y ago
The problem is, any such whats-now guide is very soon already outdated, at least in some aspects. It should be a Wiki which everyone can edit.
And btw, such Wiki exists, even officially: https://wiki.python.org/moin/FrontPage https://wiki.python.org/moin/FrontPage
Although, as you might expect, it is a mixture of outdated, more recent, messy, detailed, lists or guides and everything.
What are the current common libraries also doesn't really have a simple answer. Maybe this should be auto-generated based on Google or GitHub trends.
- zerkten 5y ago>> What are the current common libraries also doesn't really have a simple answer. Maybe this should be auto-generated based on Google or GitHub trends. I followed the Python and PSF community very closely for about 12 years through 2018. I haven't kept up for personal reasons. I suspect they are uncomfortable with doing this because they don't want to feel like they are picking winners. Whatever they list will be "blessed" no matter how many disclaimers are attached. In a way, I observe a similar problem impacting how they've approached ecosystem problems like packaging. There is a clear issue and a central authority was needed to sort it out and that never emerged when it was originally required. Right now PyPI highlights some trends (https://pypi.org https://pypi.org), but there is more they could do. Python success stories at https://www.python.org/success-stories/ https://www.python.org/success-stories/ could probably be evolved to highlight some of the libraries and tools which get serious usage. Anything that's autogenerated from other sources probably has value, but would only be something that would be compatible if it's detached from python.org. Expanding PyPI trend information would be more compatible with python.org.