Path: csiph.com!eternal-september.org!feeder.eternal-september.org!border1.nntp.ams1.giganews.com!nntp.giganews.com!newsfeed.xs4all.nl!newsfeed8.news.xs4all.nl!nzpost1.xs4all.net!not-for-mail
MIME-Version: 1.0
In-Reply-To: <CABcoaSB=w+6QZqwGbJSvvxyY8Cukz3P2HfYBLtp9c0+FH2XXjA@mail.gmail.com>
References: <f0876c48-010e-4bf0-b687-dceefba97637@googlegroups.com> <mailman.106.1441325161.8327.python-list@python.org> <3b82cc84-d51b-4b62-bf84-47a06c585bc3@googlegroups.com> <mailman.120.1441336314.8327.python-list@python.org> <7c793e45-3a4c-4b37-8111-ed16382e1551@googlegroups.com> <CACL+1at+Bhst=E_hRCfPbfF687B2EDkw+KN1yZTyyS9c=MQK7Q@mail.gmail.com> <CABcoaSB=w+6QZqwGbJSvvxyY8Cukz3P2HfYBLtp9c0+FH2XXjA@mail.gmail.com>
From: eryksun <eryksun@gmail.com>
Date: Fri, 4 Sep 2015 17:48:14 -0500
Subject: Re: Need Help w. PIP!
To: Steve Burrus <steveburrus28@gmail.com>
Cc: python-list@python.org
Content-Type: text/plain; charset=UTF-8
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.159.1441433067.8327.python-list@python.org>
Lines: 28
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:96044

On Fri, Sep 4, 2015 at 5:10 PM, Steve Burrus <steveburrus28@gmail.com> wrote:
> so what is my hopefully sinple solution anyway? i do n't see myself anytime
> soon getting off of Build 10074 of Win 10.

Script wrappers such as pip.exe are simple versions of the py launcher
that execute an embedded script. For example, here's the script
embedded in pip.exe on my system:

    #!"C:\Program Files\Python34\python.exe"
    # -*- coding: utf-8 -*-
    import re
    import sys
    from pip import main
    if __name__ == '__main__':
        sys.argv[0] = re.sub(r'(-script\.pyw|\.exe)?$', '', sys.argv[0])
        sys.exit(main())

So, as with py.exe, the child python.exe process has to be assigned to
a job object. That won't work as long as you're using build 10074 of
Windows 10. But you can still run pip using `python -m pip`.

Also, since the py launcher doesn't work on your system, you'll have
to ensure that scripts are associated with python.exe / pythonw.exe
instead of py.exe / pyw.exe. If you installed for all users you can do
that in an elevated command prompt (cmd.exe) using the ftype command:

    ftype Python.File="C:\Python34\python.exe" "%1" %*
    ftype Python.NoConFile="C:\Python34\pythonw.exe" "%1" %*