-
Notifications
You must be signed in to change notification settings - Fork 24
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
My meta data is not recognized #94
Comments
Hey, so for projects in a local directory (as opposed to on PyPI, or distribution archives), while it's been improved substantially over the past couple versions, and #92 should fix the final lingering issues, you can check out the current released code here, but in summary, the following approaches are attempted, in order:
Approach 1 is what is should be using nearly all of the time for any package with at least semi-modern packaging, and only falling back to 2 or 3 in case of a really old packaging config. It should work with any project using a properly configured PEP 517 build backend, or Setuptools by default (per the fallback specified in the PEP). However, there's one big caveat to this, which #92 fixes: Currently it does not install the required versions of the To fix that, #92 splits step 1 into two: 1a. Attempt to get the metadata through the project's build system if installed in the local environment
We could potentially use |
As for your particular issue, your configuration all looks correct, and with the very limited information provided, all I can guess is that assuming you're using the latest version of Pyroma (4.1), it may be the issue fixed in #92 . Namely that the version of your build backend (Setuptools) currently installed in your runtime environment is too outdated (older than 61.0.0, in which full pyproject.toml support was added) to work properly with a fully Therefore, I suggest the following troubleshooting steps:
If none of that works, then you'll need to provide more information for us to give you useful help:
Thanks! |
Hi,
But it should be an option because I'm using Pyroma from PyPi. Debian 11 with Python 3.9.2. Pip list
|
So I installed the Pyroma from the PR.
This is the output.
|
Thanks, but this just installs Pyroma from the default ( python3 -m pip install --upgrade git+https://github.com/CAM-Gerlach/pyroma.git@improve-pep-517-approach
You can read through the actual PEPs for the full details (I'm in the process of porting the specs to the canonical packaging.python.org site), but PEP 518 specifies the |
Ah, the Microsoft GitHub front-end is a bit inconsistent at this point. Now I installed the correct branch. Maybe you can clone my repo and run pyroam on it and see if you can reproduce this on your site? |
FWIW, @CAM-Gerlach the cool kids call it pyproject.toml-based builds instead of referring to the specific PEPs, especially when talking to end users. ;) |
Yeah, that's what I plan to do shortly; I've just been busy these past couple days, sorry.
Yeah, I saw that discussion and I'd updated PEP 639 to formally define and consistently use the term "Pyproject metadata" to refer to the source metadata format originally defined by PEP 621, that was previously called "PEP 621 metadata". I'm still getting fully in the habit of calling builds triggered through the hooks originally defined in PEP 517 "Pyproject builds" (IMO, "pyproject.toml-based builds" is waaaay too long and klunky especially with end users, and more a rough description than a specific term). I've been a bit more hesitant because the spec isn't yet migrated and I'd had the impression that end users were more likely to be familiar with PEP 517 than the new (and still not fully established) term, but in hindsight it indeed would have been clearer and less confusing, thanks. |
Hey, sorry for the delay—I got caught up working on some other things and this dropped off my radar. Anyway, after testing this locally, I was able to reproduce this issue with Setuptools >=67.1.0 (but not with Setuptools <=67.0.0), and in fact ran into the same issue when attempting to build your package normally, with So, as far as I can tell, the error here is ultimately that your In any case, while this appears to be a genuine error with the source metadata, we likely can handle this better, by providing a more informative error message, printing the build backend output that actually describes the error in more useful detail (like |
Thanks a lot for breaking this down. It works now with |
How does pyorma look for the data (description, version string, etc)?
I have a pyproject.toml, the package is installed via
pip --editable
. I also pointed pyorma to the source folder (the local git repo). The rating is 0.There is no PyPi release yet or planed in the future.
You can find the project in here (branch
develop
!)https://codeberg.org/buhtz/hyperorg/src/branch/develop
EDIT:
There is also a lot of traceback-exceptions-output. To much to post. But one "interesting" string is
Neither setup.py nor setup.cfg was found
. This two files are not needed anymore today.Do you use
importlib.metadata
package to check the data?The text was updated successfully, but these errors were encountered: