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

Switch to the non-legacy setuptools backend #1914

Closed
wants to merge 1 commit into from

Conversation

mgorny
Copy link
Contributor

@mgorny mgorny commented Oct 14, 2022

Use the non-legacy setuptools.build_meta backend. Prepend the setup directory to sys.path prior to importing modules relative to it.

Fixes #1910

Use the non-legacy `setuptools.build_meta` backend.  Prepend the setup
directory to `sys.path` prior to importing modules relative to it.

Fixes gevent#1910
@mgorny
Copy link
Contributor Author

mgorny commented Oct 14, 2022

I'm not 100% sure that this is the best approach but it seems to work here.

@jamadden
Copy link
Member

Thank you.

@jamadden jamadden closed this in 2bfebea Oct 14, 2022
@mgorny
Copy link
Contributor Author

mgorny commented Oct 15, 2022

Thanks!

@mgorny mgorny deleted the setuptools-backend branch October 15, 2022 06:30
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

Successfully merging this pull request may close these issues.

pyproject.toml uses non-public __legacy__ setuptools backend
2 participants