➜
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2012-07-07 15:52 by pitrou, last changed 2022-04-11 14:57 by admin. This issue is now closed.
| Messages (4) | |||
|---|---|---|---|
| msg164887 - (view) | Author: Antoine Pitrou (pitrou) *  |
Date: 2012-07-07 15:52 | |
It seems to have eschewed the packaging removal.
$ rm /home/antoine/opt/bin/pysetup3.3
$ make altinstall > /dev/null
$ pysetup3.3
Traceback (most recent call last):
File "/home/antoine/opt/bin/pysetup3.3", line 3, in <module>
from packaging.run import main
File "<frozen importlib._bootstrap>", line 1294, in _find_and_load
File "<frozen importlib._bootstrap>", line 1245, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 1294, in _find_and_load
File "<frozen importlib._bootstrap>", line 1258, in _find_and_load_unlocked
ImportError: No module named 'packaging'
|
|||
| msg164896 - (view) | Author: Éric Araujo (eric.araujo) * |
Date: 2012-07-07 16:07 | |
grep only finds one reference to pysetup, in the MSI code. Are you sure you built from a clean checkout? (i.e. no build dir with a leftover pysetup script) |
|||
| msg164900 - (view) | Author: Éric Araujo (eric.araujo) * |
Date: 2012-07-07 16:09 | |
An older Makefile* can also explain this. |
|||
| msg164903 - (view) | Author: Antoine Pitrou (pitrou) * |
Date: 2012-07-07 16:11 | |
> Are you sure you built from a clean checkout? (i.e. no build dir with > a leftover pysetup script) Ach, that was it. Sorry for the false alarm. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:57:32 | admin | set | github: 59487 |
| 2012-07-07 16:11:19 | pitrou | set | status: open -> closed resolution: not a bug messages: + msg164903 stage: resolved |
| 2012-07-07 16:09:55 | eric.araujo | set | messages: + msg164900 |
| 2012-07-07 16:07:15 | eric.araujo | set | messages: + msg164896 |
| 2012-07-07 15:52:26 | pitrou | create | |