RFH with a problem with pip 10 on Windows (AppVeyor)
Hi, since some time, the CI job on AppVeyor for a package I maintain fails in a way I was not able to reproduce in my local demo Win7 VM. This is a link to the error: https://ci.appveyor.com/project/lelit/python-rapidjson/build/1.0.184#L66 and as you can see, it happens when cibuildwheel tries to install the "wheel" package, and the following happens: + pip install wheel Using default MSVC build environment for 32 bit architecture Executing: pip install wheel Traceback (most recent call last): File "c:\python34\lib\runpy.py", line 170, in _run_module_as_main "__main__", mod_spec) File "c:\python34\lib\runpy.py", line 85, in _run_code exec(code, run_globals) File "C:\Python34\Scripts\pip.exe\__main__.py", line 5, in <module> ImportError: cannot import name 'main' The problem may be related to something different in version 10 of pip, but that's just a guess: as always, on Windows there are no certainties :-) It used to work as expected, this is a link to latest successful run: https://ci.appveyor.com/project/lelit/python-rapidjson/build/1.0.181?fullLog... and since then the only (apparent) difference is the pip version... Can anybody understand what's going on? Thanks in advance, ciao, lele. -- nickname: Lele Gaifax | Quando vivrò di quello che ho pensato ieri real: Emanuele Gaifas | comincerò ad aver paura di chi mi copia. lele@metapensiero.it | -- Fortunato Depero, 1929.
Hello Lele, you need to upgrade with: python -m pip install --upgrade pip E.g. take a look at this https://github.com/ogrisel/python-appveyor-demo/pull/46 On Wed, Apr 25, 2018 at 4:25 PM Lele Gaifax <lele@metapensiero.it> wrote:
Hi,
since some time, the CI job on AppVeyor for a package I maintain fails in a way I was not able to reproduce in my local demo Win7 VM.
This is a link to the error:
https://ci.appveyor.com/project/lelit/python-rapidjson/build/1.0.184#L66
and as you can see, it happens when cibuildwheel tries to install the "wheel" package, and the following happens:
+ pip install wheel Using default MSVC build environment for 32 bit architecture Executing: pip install wheel Traceback (most recent call last): File "c:\python34\lib\runpy.py", line 170, in _run_module_as_main "__main__", mod_spec) File "c:\python34\lib\runpy.py", line 85, in _run_code exec(code, run_globals) File "C:\Python34\Scripts\pip.exe\__main__.py", line 5, in <module> ImportError: cannot import name 'main'
The problem may be related to something different in version 10 of pip, but that's just a guess: as always, on Windows there are no certainties :-)
It used to work as expected, this is a link to latest successful run:
https://ci.appveyor.com/project/lelit/python-rapidjson/build/1.0.181?fullLog...
and since then the only (apparent) difference is the pip version...
Can anybody understand what's going on?
Thanks in advance, ciao, lele. -- nickname: Lele Gaifax | Quando vivrò di quello che ho pensato ieri real: Emanuele Gaifas | comincerò ad aver paura di chi mi copia. lele@metapensiero.it | -- Fortunato Depero, 1929.
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
-- Cosimo Lupo
Cosimo Lupo <cosimo@anthrotype.com> writes:
Hello Lele,
you need to upgrade with:
python -m pip install --upgrade pip
E.g. take a look at this https://github.com/ogrisel/python-appveyor-demo/pull/46
Thank you, will report to the cibuildwheel folks then. ciao, lele. -- nickname: Lele Gaifax | Quando vivrò di quello che ho pensato ieri real: Emanuele Gaifas | comincerò ad aver paura di chi mi copia. lele@metapensiero.it | -- Fortunato Depero, 1929.
On 25 April 2018 at 17:17, Lele Gaifax <lele@metapensiero.it> wrote:
Cosimo Lupo <cosimo@anthrotype.com> writes:
Hello Lele,
you need to upgrade with:
python -m pip install --upgrade pip
E.g. take a look at this https://github.com/ogrisel/python-appveyor-demo/pull/46
Thank you, will report to the cibuildwheel folks then.
It might be worth noting that cibuildwheel does "pip install --disable-pip-version-check --user --upgrade pip" - see https://github.com/joerick/cibuildwheel/blob/master/cibuildwheel/windows.py#... In principle this does work (i.e., it does install a correct pip.exe), but it's likely that the location of this pip.exe is not on PATH, so the system version is being picked up, and that's for an older version of pip, hence the error. So an alternative to changing the command to upgrade the system installed Python would be to ensure that the user scripts directory is at the front of PATH. But TBH, how they choose to fix the issue is up to the cibuildwheel project. I genuinely don't know which option would be best for them. Paul
Paul Moore <p.f.moore@gmail.com> writes:
But TBH, how they choose to fix the issue is up to the cibuildwheel project. I genuinely don't know which option would be best for them.
Cosimo already alerted them, and proposed this: https://github.com/joerick/cibuildwheel/pull/62 Let's see what happens... thanks&bye, lele. -- nickname: Lele Gaifax | Quando vivrò di quello che ho pensato ieri real: Emanuele Gaifas | comincerò ad aver paura di chi mi copia. lele@metapensiero.it | -- Fortunato Depero, 1929.
participants (3)
-
Cosimo Lupo
-
Lele Gaifax
-
Paul Moore