[Python-Dev] What is the rationale behind source only releases?
Chris Jerdonek
chris.jerdonek at gmail.com
Wed May 16 01:55:07 EDT 2018
More information about the Python-Dev mailing list
Wed May 16 01:55:07 EDT 2018
- Previous message (by thread): [Python-Dev] What is the rationale behind source only releases?
- Next message (by thread): [Python-Dev] What is the rationale behind source only releases?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
What does “no release at all” mean? If it’s not released, how would people use it? —Chris On Tue, May 15, 2018 at 9:36 PM Alex Walters <tritium-list at 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. I have an opinion on their utility and perhaps > an > idea about changing them, but I'd like to know why they are done (as > opposed > to source+binary releases or no release at all) before I head over to > python-ideas. Is this documented somewhere where my google-fu can't find > it? > > > [1]: https://en.wikipedia.org/wiki/Wikipedia:Chesterton%27s_fence > > _______________________________________________ > Python-Dev mailing list > Python-Dev at python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > https://mail.python.org/mailman/options/python-dev/chris.jerdonek%40gmail.com > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20180515/192e8123/attachment.html>
- Previous message (by thread): [Python-Dev] What is the rationale behind source only releases?
- Next message (by thread): [Python-Dev] What is the rationale behind source only releases?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list