placeholder
peps
placeholder | peps | |
---|---|---|
9 | 36 | |
668 | 4,140 | |
- | 0.9% | |
4.6 | 9.8 | |
4 months ago | 6 days ago | |
Python | reStructuredText | |
GNU General Public License v3.0 or later | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
placeholder
-
Gnome developer proposes removing the X11 session
This guy wasn't maintaining Python, he as creating a new version incompatible with either Python 2.7 or Python 3.
Red Hat and other large companies have maintained Python for years after 2.7 died (EOL date was January 1st, 2020). IBM/Red Hat offer Python 2.7 including security fixes and bug fixes until 2024 (https://access.redhat.com/solutions/4455511).
Had he just provided patches to Python 2.7, nobody would've batted an eye. Instead, they created an alternative language that was completely different (https://web.archive.org/web/20161210161837/https://www.nafta...).
Founders and core devs indicated that the name was the only problem (https://github.com/naftaliharris/tauthon/issues/47#issuecomm...) and that even things like the header file names could continue to be named Python because of API compatibility.
You can fork any open source project you like, but you still need to stick follow trademark law. You can't just release Linux 2.7 because you disagree with breaking changes in 3.0 either, but you're free to take the Linux code and release Twonux if you really care.
-
Debian 12 python2 install
If that doesn't work for some reason, there's this project which claims to be an "active" fork of Python 2, but it also has a lot of backports and additions so I worry a bit about backward compatibility and stability: https://github.com/naftaliharris/tauthon You would have to build this from source as well.
-
Don't carelessly rely on fixed-size unsigned integers overflow
Without developers of the compilers all others groups are pretty much irrelevant. There were lots of people who were telling that Python3 is abomination and some even attempted to fork it but fork haven't caught enough interest thus Python2 is, for all intends and purposes, dead.
-
Blog post: Rust in 2023
Python developers noticed that people are not in any hurry to switch but instead of trying to understand “why” they have drawn the line in the sand and spent their efforts trying to kill unofficial attempts to create a fork.
-
Ubuntu Pro
WinAmp 2 (1998) was widely liked. WinAmp 3 (2002) was considered bloated, and flopped.
So Nullsoft followed it up with WinAmp 5 – because 2+3=5 – in 2003, which was very broadly the codebase of WinAmp 2 (small and lean) plus the skin support from WinAmp 3 (the only part people liked).
This won people back, and WinAmp is still around and got an update this year, 20 years on.
I think it's too late for there to be a Python 5, but I did read a blog post long ago – which I can't find again, or I'd link to it – which proposed a similar compromise fix to Python, in considerable technical detail.
I am with @blagie on this: the Python world handled the 2→3 transition spectacularly badly. V3 didn't deliver enough, and strong-arming people by just end-of-lifing Python 2 and expecting the world to move on was foolhardy and short-sighted.
(And I don't even use the language myself. I'm just observing.)
It's a real shame Tauthon didn't get more traction and support.
https://github.com/naftaliharris/tauthon
If it had got enough support and continued, maybe the Python maintainers would have learned something, but I've not seen any sign that they have.
This is nothing new. For comparison, Perl 6 went so badly that Perl 5 now looks likely to continue as Perl 7:
https://www.perl.com/article/announcing-perl-7/
And PHP 6 didn't really happen -- AFAICT as a total outsider, Unicode support proved too hard and it was never released; the community backported the important bits to PHP 5, and then a new PHP 7, more modest in scope, developed from PHP 5.
The Python world could have done the same, and Tauthon was an effort in that direction.
It's too late now. I suspect that, just as Perl has lost a massive amount of interest and use, partly from the nearly-two-decade-long effort to release Perl 5, Python has done the same -- sabotaged its own community with this high-handed "your leaders know best" approach.
-
Will GIL ever be gone?
I just can't see a major fork happening (see: Tauthon, a fork of 2.7 to keep it alive, but no updates in a year or so).
- What happens if we don't migrate Python 2 code to python 3
-
Pip has dropped support for Python 2
If you want forks there are forks. Off the top of my head, Redhat is supporting Python 2 for several more years and there's a project called Tauthon [1] that is "Python 2.8" in spirit. I'm sure there's more efforts I'm not aware of.
[1] https://github.com/naftaliharris/tauthon
peps
- PEP 722: Python dependencies for single-file scripts
-
Getting started with the Mojo programming language
If you have suggestions that could improve the Python experience, consider proposing these through the Python Enhancement Proposal (PEP) process. The Mojo team actively encourages this, as it views Mojo as a new member of the Python family.
- PEP 684 was accepted – Per-interpreter GIL in Python 3.12
- Disallow import * for your Python package
-
Ask HN: Just Finished Stroustrup's 'Practice and Principles'. What Next?
after 1-6, should have a good idea of what type of documentation / coding standards / tools / levels of abstraction want to have/see for a projects source code/deliverable. :-)
[1] : http://github.com/Blackgu/ebooks/blob/master/ebooks/2012-2-1...
[2] : http://peps.python.org
[3] http://medium.com/codex/say-goodbye-to-loops-in-python-and-w...
-
Don't carelessly rely on fixed-size unsigned integers overflow
Yet development is carried via consensus between developers and users, there are places where users come to discuss thinks and ask questsion, there are place where resolutions are described in a POSITA-understandable terms and so on.
-
Show HN: Python framework is faster than Golang Fiber
Oh, I have a pretty fresh news for you.
https://github.com/python/peps/pull/2955
- PEP703 Making the Global Interpreter Lock Optional in CPython
- PEP 703: Making the Global Interpreter Lock Optional in CPython
-
Are there any published articles about Python that I can reference?
You mean like PEPs? https://peps.python.org
What are some alternatives?
awesome-buttplug - A list of awesome projects that use the Buttplug Sex Toy Control Library
materials - Bonus materials, exercises, and example projects for our Python tutorials
AntiqueAtlas - A Minecraft mod that adds a fancy interactive map item.
pyenv-virtualenv - a pyenv plugin to manage virtualenv (a.k.a. python-virtualenv)
CraftTweaker - Tweak your minecraft experience
gcc
pyupgrade - A tool (and pre-commit hook) to automatically upgrade syntax for newer versions of the language.
DIPs - D Improvement Proposals
xdg-desktop-portal - Desktop integration portal
faster-cpython - How to make CPython faster.
kpatch - kpatch - live kernel patching
MLStyle.jl - Julia functional programming infrastructures and metaprogramming facilities