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
devguide doesn’t list all build dependencies #57681
Comments
The Quick Start section in the devguide does not tell people what they need to install in order to compile Python. A short mention or a link to a section with all info should be added. I can contribute info for Debian and derivative systems: “aptitude build-dep pythonX.Y” |
Well, it's a quick start. The link to "build Python" actually tells you about dependencies. |
Okay. I just hope that people following the quick start and having build issues will follow the link. I followed it and the section only mentions zlib, I think it could be exhaustive. |
I agree with Antoine, there's no need to mention them in the quickstart. Moreover these dependencies are optional, so there's no need to install them unless they are specifically needed (on a related note I would also add an "optional" in the warning that says "Python build finished, but the necessary bits to build these modules were not found" -- I've seen enough people complaining that the build "failed" because this dependencies were missing). |
|
I have a few arguments in favor of my position:
But it's still missing an "optional" before modules imho. The second message that says to "look in setup.py in detect_modules()" doesn't seem too useful too (but maybe I should take a look ;). There are a couple of threads on Core-Mentorship by people that got confused by these messages (and some include discussions about finding the dependencies).
You can also do it incrementally, adding e.g. "For Debian and derivative systems you can use |
|
So, the devguide has been updated since this issue was opened. The Quick Start section now has a link to build documentation, which includes information about build dependencies. Is this sufficient to call this bug closed? |
I agree with Jeff's recommendation that this issue is resolved by content already in the devguide's Build Dependencies[1]. Jeff, Thanks for helping close an old issue. [1] https://docs.python.org/devguide/setup.html#build-dependencies |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: