-
Notifications
You must be signed in to change notification settings - Fork 159
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
Unclear what the build system is #581
Comments
https://peps.python.org/pep-0517/
Is this causing any problems (both "build" and "pip" seem to do the right thing) ? I can make it explicit if needed |
It defaulted to setuptools.build_meta.__legacy__. Set explicitely to avoid any confusion. See quodlibet#581
See #582. I'd still like to know if this is causing any problems and requires a new release. |
No, no real problems right now. Just a bit confusion, and if you don't specify the setuptools backend explicitly, then you're relying on (somewhat obsolete) legacy setuptools backend. No need to make a new release over this. |
OK, thanks. I've merged #582 |
(as for the poetry/setuptools mix.. it allows me to use poetry for dev, while still providing a setup.py with some minimal metadata duplication) |
What is the actual build system used by mutagen?
pyproject.toml
has some poetry metadata but thebuild-system
section includes setuptools requirements. However, even then it doesn't declare anybuild-backend
, neither setuptools' nor poetry's.The text was updated successfully, but these errors were encountered: