| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
…eyword use of parameters (python/cpython#107984) It is now possible to deprecate passing keyword arguments for keyword-or-positional parameters with Argument Clinic, using the new '/ [from X.Y]' syntax. (To be read as "positional-only from Python version X.Y") Co-authored-by: Erlend E. Aasland <erlend@python.org> Co-authored-by: Alex Waygood <Alex.Waygood@Gmail.com>
… that uses the limited C API (python/cpython#108584) Co-authored-by: Alex Waygood <Alex.Waygood@Gmail.com> Co-authored-by: Erlend E. Aasland <erlend.aasland@protonmail.com>
|
We'll need to wait a few hours until the Python documentation is rebuilt (hence why the workflow failed when re-run). A |
Sorry, something went wrong.
|
I'd like to move the English HTML docs build from the docs server and use Read the Docs, so we get ~instant deploys instead of waiting ~24 hours. The non-HTML and translations can remain on the docs server (at least to begin with). But that will need more planning (adding the language/version switchers, perhaps co-ordination with RtD) so something for future discussion :) |
Sorry, something went wrong.
Well, of course E[wait time] is only 12 hours..! I have hesitations about moving to RtD, but again best part of a dedicated discussion. I think we could (and should) look into rebuilding /3/ (perhaps also the pre-release versions, but certainly only the English HTML) more frequently than 24 hours, potentially every 4 or 6. I'm led to believe the expensive bits of the build are not the HTML bits. I'll open a docsbuild-scripts issue. A |
Sorry, something went wrong.
|
Opened python/docsbuild-scripts#163 |
Sorry, something went wrong.
|
Thanks for opening that! Today's daily build has built today. I've restarted the GHA job and it's passed. I don't see an option to rebuild RTD, but feel free to close/re-open if you like. |
Sorry, something went wrong.
|
@erlend-aasland would you mind rebase-merging this please? I wouldn't want to progress the CPython PR without having the developer's guide being properly up-to-date. A |
Sorry, something went wrong.
Thanks for taking care of this! |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
cc: @erlend-aasland; there were two commits that I've only just noticed weren't included in the earlier branch. Please may you rebase-merge this PR to include them?
A
📚 Documentation preview 📚: https://cpython-devguide--1167.org.readthedocs.build/