5 ms·
No GIL should be "python 4.0"
by justahuman74 4y ago
No GIL should be "python 4.0"
- deleted 4y ago[deleted]
- __turbobrew__ 4y agoPlease no. I will quit python if they do another breaking major version change.
- nhumrich 4y agoIt doesn't have to be breaking for a 4.0 label.
- orangepurple 4y agoSemantic Versioning 2.0.0 Summary Given a version number MAJOR.MINOR.PATCH, increment the: MAJOR version when you make incompatible API changes -------- Considering semver and that this is a COMPATIBLE API change, it does not warrant an increment to 4.x
- kzrdude 4y agoPython doesn't follow semver anyway (and it's fine IMO).
- deleted 4y ago[deleted]
- stjohnswarts 4y agoSemantic Versioning is basically dead on most open source projects these days. I don't think most even used it right back in the day.
- threatripper 4y agoThis would totally make sense. A major change in architecture with some libraries breaking. While many people are still store from the 2->3 transition I would not expect this change to be that severe Most code should work for python 3 and 4 without changes.
- divbzero 4y agoIt could be done in incremental steps: 1. python3.x nogil as a compiler flag 2. python3.y nogil as a runtime flag 3. python4.0 nogil as the default (if we’re really ready for it)