| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
I'm not sure if adding a new dedicated Variables section is the best home for all these variables. I chose to use .. cmdoption:: NAME syntax to avoid name conflicts with compiler flags defined with .. envvar:: NAME such as: https://docs.python.org/dev/using/configure.html#compiler-flags I used ./configure --help | grep '^\s\+[A-Z]\{2,\}' command to list all configure variables, see @erlend-aasland's comment: #109101 (comment) Initially, I just wrote this PR to document LIBATOMIC :-) |
Sorry, something went wrong.
|
I reorganized the doc. I'm not sure between envvar and cmdoption. The current doc uses envvar. cc @hugovk |
Sorry, something went wrong.
|
@erlend-aasland: it seems like the whole "3.3.4. Libraries Options" section is new in Python 3.11, all xxx_CFLAGS and xxx_LIBS, no? |
Sorry, something went wrong.
|
PROFILE_TASK was added in Python 3.8. |
Sorry, something went wrong.
Yes, it came with the setup.py migration we did. |
Sorry, something went wrong.
| Name for machine-dependent library files. | ||
|
|
||
|
|
||
| Libraries Options |
There was a problem hiding this comment.
How about Third-party dependencies or Options for third-party dependencies?
Sorry, something went wrong.
There was a problem hiding this comment.
Go for "Options for third-party dependencies".
Sorry, something went wrong.
|
@erlend-aasland: I updated my PR, would you mind to review it again? |
Sorry, something went wrong.
| .. cmdoption:: LIBATOMIC | ||
|
|
||
| Linker flags when ``cpython/pyatomic.h`` header file is used. | ||
|
|
||
| Default: ``LIBATOMIC='-latomic'`` if ``libatomic`` is needed, or | ||
| ``LIBATOMIC=''`` otherwise (also the default when Python is cross-compiled). | ||
|
|
||
| .. versionadded:: 3.13 | ||
|
|
There was a problem hiding this comment.
This is going away with #109344:
| .. cmdoption:: LIBATOMIC | |
| Linker flags when ``cpython/pyatomic.h`` header file is used. | |
| Default: ``LIBATOMIC='-latomic'`` if ``libatomic`` is needed, or | |
| ``LIBATOMIC=''`` otherwise (also the default when Python is cross-compiled). | |
| .. versionadded:: 3.13 |
Sorry, something went wrong.
There was a problem hiding this comment.
I understand that you want me to remove this variable in the doc, so I removed it.
Sorry, something went wrong.
|
Oh sorry for the noise, I tried a Git tool which messed up with my PR. I fixed my PR. |
Sorry, something went wrong.
|
PR rebased on the main branch. |
Sorry, something went wrong.
There was a problem hiding this comment.
I would keep the PR focused and handle capitalization issues in a separate PR.
New titles should follow the existing conventions, even if it doesn't match the preferred capitalization specified by the devguide. A follow-up PR can fix it.
Sorry, something went wrong.
Hum, ok, I reverted these changes. I didn't expect that changing a few titles would be so controversial :-) |
Sorry, something went wrong.
Co-authored-by: Ezio Melotti <ezio.melotti@gmail.com>
|
@erlend-aasland @hugovk @ezio-melotti: I rebased my PR on the main branch, squashed commits, I reverted title casing change (don't use Titlecase Anymore). Please review the updated PR. @ezio-melotti: I applied your sugsestions to use :samp:, thanks. |
Sorry, something went wrong.
|
Looks good, although I'll leave approval for someone who knows about these flags 👍 |
Sorry, something went wrong.
There was a problem hiding this comment.
Looks good Sphinx-wise. (But same caveat as Hugo wrt the flags)
A
Sorry, something went wrong.
Co-authored-by: Ezio Melotti <ezio.melotti@gmail.com>
|
Thanks for the reviews. If someone has more remarks, feel free to propose a PR :-) |
Sorry, something went wrong.
|
LGTM! Thanks for documenting these things. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
📚 Documentation preview 📚: https://cpython-previews--109224.org.readthedocs.build/