[Python-Dev] What is the rationale behind source only releases?

[Steven D'Aprano]

On Tue, May 15, 2018 at 10:55:07PM -0700, Chris Jerdonek wrote:
> What does “no release at all” mean? If it’s not released, how would people
> use it?

I've been using Python 1.7 for years now. It is the perfect Python, with 
exactly all the features I want, and none that I don't want, and so much 
faster than Python 2.7 or 3.7 it is ridiculous.

Unfortunately once I've woken up and tried to port my code to an actual 
computer, it doesn't work.

*wink*

In principle, we could continue adding fixes to a version in the source 
repository, but never cut a release with a new version. But I don't 
think we do that: once a version hits "no release", we stop adding fixes 
to the repo for that version:

- full source and binary releases
- source only releases
- accumulate fixes in the VCS but don't cut a new release
- stop making releases at all (the version is now unmaintained)

The third (second from the bottom) doesn't (as far as I am aware) occur.



-- 
Steve