Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork32k
GH-92584: Redirect to Setuptools' guidance on extension modules#108030
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:main
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
It's got important information in there that probably doesn'tofficially exist anywhere else, and for POSIX devs trying to make stuff work on Windows I'm sure it's invaluable (though it would be nice to have similar guides for Windows devs trying to make stuff work on *nix, but I'm not going to hold my breath). Expecting people to extract the same information from That said, it's in desperate need of cleanup and modernisation anyway, so I won't miss it. A cross-platform primer on building extension modules by hand (i.e. without |
Should we open a new issue for this? A |
zooba commentedAug 16, 2023 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
It won't hurt, but I'm not sure it'll help convince anyone to actually do it. But I don't know of any better place to put the note - maybe as a comment in the docs as well (referencing the soon-to-be-created new issue)? |
Opened#108064 |
Uh oh!
There was an error while loading.Please reload this page.
I'm unsure if we should just drop
extending/windows
entirely, as it internally reccomends just to usesetuptools
:A
📚 Documentation preview 📚:https://cpython-previews--108030.org.readthedocs.build/