[Python-Dev] What is the rationale behind source only releases? (original) (raw)
Alex Walters tritium-list at sdamon.com
Wed May 16 00:35:54 EDT 2018
- Previous message (by thread): [Python-Dev] Making Tcl/Tk more suitable for embedding (was: [issue33479] Document tkinter and threads)
- Next message (by thread): [Python-Dev] What is the rationale behind source only releases?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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?
- Previous message (by thread): [Python-Dev] Making Tcl/Tk more suitable for embedding (was: [issue33479] Document tkinter and threads)
- Next message (by thread): [Python-Dev] What is the rationale behind source only releases?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]