Skip to content
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

Reflect changes and content of files involved in packaging as defined by PEP 517/518 specification #4

Open
search5 opened this issue Feb 24, 2024 · 0 comments

Comments

@search5
Copy link

search5 commented Feb 24, 2024

Expected behaviour

With recent changes to the Python packaging specification to allow the use of different backends, installing packages using setup.py often results in warning messages.

Actual behaviour

Regardless of your Python version, you will need to update your packaging specification to follow the latest Python packaging specification, PEP 517/518.

What are the steps to reproduce this issue?

There is no separate error implementation procedure for packaging specification changes, as they are not considered errors and can be categorized as feature enhancements.

Any other comments?

I'm working on changing the SQLAlchemy 1 version code to SQLAlchemy 2 version code in several subprojects of the Python-social-auth project, and I'd like to reflect this in the corresponding commits.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant