Author ncoghlan
Recipients BreamoreBoy, NaCl, bwanamarko, ncoghlan, paul.moore, r.david.murray, steve.dower, terry.reedy, tim.golden, zach.ware
Date 2015-03-21.22:58:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I agree the migration to Program Files & a different installer build process is more than ambitious enough for 3.5.

For the embedding case, it's not that it *can't* be done, it's just a PITA.

Perhaps for the per-user no-admin-rights needed case, we could direct folks to the big bundle as a vendor neutral all inclusive bulk distribution?

To be completely clear, I'm talking "invite Perica Zivkovic to become part of CPython release management and include Portable Python release timelines in the CPython release PEPs" levels of engagement. "Is Portable Python fully operational yet?" could become one of the key gating criteria for leaving the beta phase and entering the release candidate phase.
Date User Action Args
2015-03-21 22:58:51ncoghlansetrecipients: + ncoghlan, terry.reedy, paul.moore, tim.golden, r.david.murray, BreamoreBoy, zach.ware, steve.dower, bwanamarko, NaCl
2015-03-21 22:58:50ncoghlansetmessageid: <>
2015-03-21 22:58:50ncoghlanlinkissue22516 messages
2015-03-21 22:58:50ncoghlancreate