(original) (raw)

On 14 Oct 2013 04:26, "Paul Moore" <p.f.moore@gmail.com> wrote:
\>
\> On 13 October 2013 13:43, Nick Coghlan <ncoghlan@gmail.com> wrote:
\> > Accordingly, in addition to adding the option to extract and install \`\`pip\`\`
\> > during installation, this PEP proposes that the Windows installer (and
\> > \`\`sysconfig\`\`) in Python 3.4 and later be updated to:
\> >
\> > - install scripts to PythonXY\\bin rather than PythonXY\\Tools\\Scripts
\> > - add PythonXY\\bin to the Windows PATH (in addition to PythonXY) when the
\> > � PATH modification option is enabled during installation
\>
\> Then implication of this is that venv (and virtualenv, but that's less
\> relevant to python-dev) should be updated to use a "bin" directory on
\> Windows rather than the current "Scripts" directory. This would only
\> be for 3.4, which means that virtualenv will need to make the
\> directory name conditional on version, I guess.

The sysconfig directory scheme will change accordingly, so it may be possible to leverage that by basing the virtualenv layout on the default scheme.

Cheers,
Nick.

>
\> Paul.