On May 16, 2018, at 00:35, Alex Walters <tritium-l...@sdamon.com> wrote:
> 
> In the spirit of learning why there is a fence across the road before I tear
> it down out of ignorance [1], I'd like to know the rationale behind source
> only releases of cpython.

Historically, it was a matter of resources.  Making binary releases incurs 
costs and delays on the release process and release managers, including the 
folks who actually have to produce the binaries.  As a version winds down, we 
wanted to impose less work on those folks and less friction and delay in 
cutting a release.  There is still value in spinning a tarball though, for 
downstream consumers who need a tagged and blessed release.

Cheers,
-Barry

Attachment: signature.asc
Description: Message signed with OpenPGP

_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Reply via email to