-
Notifications
You must be signed in to change notification settings - Fork 472
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Broken package name (since commit [754b9a52f7bb83d8d356050a14caebc6fbaccc85]) #2547
Comments
In short, it looks like the system package
|
@Gelma Does the above fix the problem? Yet we need a different solution, because installing codespell fails both on Ubuntu 18.04 and Ubuntu 22.04. /Log of installation failure on Ubuntu 18.04
|
Of course, not. My python-setuptools is not broken. Anyway, even installing the latest version via pip, the issue change, but is still broken. I don't want to waste your precious time trying to replicate it, so I made a video starting from install of Ubuntu 22.04, trying to compile with packaged setuptools, and also after upgrading it. |
Indeed I cannot reproduce the problem any more today, whatever the version of
Yet, I managed to fix this From my #2532 (comment), 5 days ago on my Ubuntu 22.04 machine:
Today, on the same Ubuntu 22.04 machine:
I was convinced the version of |
Starting again, after uninstalling all modules installed by
Now I can again reproduce the
Installing the new version of
In your case, which version of
Then back to your specific command:
According to No module named pkg_resources:
So let's update
Now it works, more or less. The setup process does find the name (no more
Not sure how to fix the version for now. Perhaps stick to |
It's enough to revert these file before the commit in subject and it works like a charm:
|
The whole point of #2523 was to migrate from the traditional In this context, the real solution is to understand why the name and version of the project are not properly picked by the versions of And again, the proper way to install is not |
Just for the record, a few notes.
a) did you watch my video? In that you can see that even installing the latest setuptools (not packaged, by pip), the problem change, is not fixed (the version number is picked as 0.0.0);
Ok, so this is not the right way (btw, first time you tell me this). Bring us the light: which one to use? The funny thing is every time you try to blame something else, and each time is not the solution. Let's recap: and now, guess what next? You can keep it broken and blame the rest of the world. No drama. Mine is working because I reverted.
|
I am sorry I haven't been clear enough. The proper way to install is I have been discovering all this myself in the last few days, because of similar issues I had while trying installing codespell. This is still new for me, so please bear with me if I am not making myself clear enough, I am still learning. Again, the right thing to do is to use
Nowhere does it instruct running Now, this is where it gets complex, even
Now back to the issues you (and I) have been experiencing:
In short, the legacy installation now works for me, provided I update first:
But again, the standard installation process would rather be:
Of course, you are free to revert as you did to run the legacy And by the way, I am not the maintainer and I haven't made the choices you complain about. I am just trying to help on my spare time. You have been barking up the wrong tree – if barking was ever needed here. |
After many tests described at the end of #2523, it appears that the requirements for installing
The question remains why |
Hi,
since commit in subject the package name is UNKNOWN. Tested on different laptops, bisected on fresh Ubuntu 22.04.
The text was updated successfully, but these errors were encountered: