New submission from mrx23dot:
setuptools Windows installer doesn't look for HKEY_LOCAL_MACHINE:
only looks in: HKEY_CURRENT_USER for Python:
[HKEY_LOCAL_MACHINE\Software\Python\PythonCore\2.7]
(problem on Win7 x64 Python 2.7 installed for All users)
Also it doesn't add Python\Scripts to PATH.
On 2 March 2014 07:25, Nick Coghlan ncogh...@gmail.com wrote:
I've just posted updated versions of PEP 426 and 459 that defer the
metadata hooks feature. The design and behaviour of that extension
is still way too speculative for me to approve in its current form,
but I also don't want to
On 3 Mar 2014 04:34, Oscar Benjamin oscar.j.benja...@gmail.com wrote:
On 2 March 2014 07:25, Nick Coghlan ncogh...@gmail.com wrote:
I've just posted updated versions of PEP 426 and 459 that defer the
metadata hooks feature. The design and behaviour of that extension
is still way too
On 2 March 2014 21:05, Nick Coghlan ncogh...@gmail.com wrote:
I think this approach may also encourage a design where projects do
something sensible *by default* (e.g. NumPy defaulting to SSE2) and
then use the (not yet defined) post-installation hooks to potentially
*change away* from
A required preliminary task is to create a revision of PEP 425 that
expands its scope to also handle the parts of the file/directory
naming scheme that are common across sdist, wheel and the installation
database (with compatibility tags becoming a subsection)
can you elaborate a bit.
On Sat, Mar 1, 2014 at 9:22 PM, Nick Coghlan ncogh...@gmail.com wrote:
On 27 February 2014 10:46, Marcus Smith qwc...@gmail.com wrote:
that would be good. If you did, I would link to the tasks from the PUG
future page.
OK, these are the things I consider blockers for an accepted metadata
On 3 March 2014 16:12, Marcus Smith qwc...@gmail.com wrote:
A required preliminary task is to create a revision of PEP 425 that
expands its scope to also handle the parts of the file/directory
naming scheme that are common across sdist, wheel and the installation
database (with compatibility
