[Distutils] Specific packaging goals and a tentative timeline

[Nick Coghlan]

On 20 July 2013 02:31, Marcus Smith <qwcode at gmail.com> wrote:
>
>>     * decide on a bundling or explicit bootstrapping scheme for pip
>> (this still needs a PEP to help clarify the pros and cons of the
>> various alternatives)
>
>
> if we improve things enough so that the get-pip.py experience is reliable
> and robust (and handles setuptools if not bundled), then might that be
> enough for now?
> (see the options here: https://github.com/pypa/pip/issues/1049)
> i.e. improve pip's installer experience, and then come back around to
> bundling/bootstrap with python.

If we can figure out a consistent download-and-run experience that
doesn't assume the availability of curl or wget, I think so.
Alternatively (as I think Donald suggested?) a simple download-and-run
Windows executable or installer would be friendlier for people that
may not be used to configuring the Windows command line (even if it
still relied on get-pip.py to do the heavy lifting in terms of
actually getting pip onto the system). It doesn't help that the
Microsoft provided UI for configuring environment variables hasn't
seen any serious improvements in the better part of two decades :P

Also, if we'd like to do cert verification in the bootstrap script,
keep in mind the fact that Python 2.6+ supports executable zip
archives, so long as they have a __main__.py file at the top level.

Cheers,
Nick.

--
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia