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

PEP517 #67

Open
Alessandro-Barbieri opened this issue May 17, 2022 · 4 comments
Open

PEP517 #67

Alessandro-Barbieri opened this issue May 17, 2022 · 4 comments

Comments

@Alessandro-Barbieri
Copy link

Could you move the buildsystem to PEP517?

@cdent
Copy link
Owner

cdent commented May 17, 2022

The current build system works, so without compelling reasons to change I'd be reluctant to do so. What are the compelling reasons?

I'm not doubting that there are benefits and reasons, so mostly this is a question of "why?"

I'd happily welcome and review a pull request that made the change, if you're interested.

@Alessandro-Barbieri
Copy link
Author

Because I'm packaging for gentoo overlay ::guru and now non PEP517 build are considered legacy
see https://projects.gentoo.org/python/guide/distutils.html#the-pep-517-and-legacy-modes

@cdent
Copy link
Owner

cdent commented May 26, 2022

Like I said "I'd happily welcome and review a pull request that made the change". If it needs to wait on me it may be a while.

@cdent
Copy link
Owner

cdent commented Mar 16, 2024

Note that python -m build will build wsgi-intercept just fine. Is that sufficient to be PEP517 compliant according to gentoo?

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

No branches or pull requests

2 participants