This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ned.deily
Recipients BreamoreBoy, NaCl, bwanamarko, larry, ncoghlan, ned.deily, paul.moore, r.david.murray, steve.dower, terry.reedy, tim.golden, zach.ware
Date 2015-03-21.23:24:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1426980286.87.0.697749735167.issue22516@psf.upfronthosting.co.za>
In-reply-to
Content
Bringing an umbrella distribution into the CPython release process seems to me like a very big leap and would that requires very careful consideration.  It would introduce a whole load of other dependencies into our release process, i.e. that the third-party packages (e.g. numpy, et al) included in Portable Python would become gating factors and dependencies for CPython releases.  Frankly, I don't thing we want to go there.  I don't have an objection to referring to users to other distributions like Portable Python (or Anaconda or whatever) but actually bringing it into the release process would need a *lot* of careful thought and planning and co-ordination.  Sounds like an interesting discussion for the language summit.
History
Date User Action Args
2015-03-21 23:24:46ned.deilysetrecipients: + ned.deily, terry.reedy, paul.moore, ncoghlan, larry, tim.golden, r.david.murray, BreamoreBoy, zach.ware, steve.dower, bwanamarko, NaCl
2015-03-21 23:24:46ned.deilysetmessageid: <1426980286.87.0.697749735167.issue22516@psf.upfronthosting.co.za>
2015-03-21 23:24:46ned.deilylinkissue22516 messages
2015-03-21 23:24:46ned.deilycreate