Support code highlighting#1577
Conversation
|
Have you checked if this will work with the deployment of the PEPs on python.org? |
|
How would one test that? |
|
The process to build the PEPs from python.org is described here https://pythondotorg.readthedocs.io/pep_generation.html |
|
|
I'm having difficulty building the site |
|
Could one of you please try? |
|
We don't 'have any experience with the web site, so it would be best to ask on the pythondotorg repo instead of here. |
|
I was also unsuccessful, I tried both the Vagrant and manual methods from https://pythondotorg.readthedocs.io/install.html |
|
Please report issue wrt pythondotorg guide in the GitHub.com/Python/pythondotorg repo |
|
@brettcannon Seems to work python/pythondotorg#1633 (comment) |
|
I rebased, should be good to merge now |
.github/workflows/build.yml
Outdated
| run: | | ||
| python -m pip install -U pip | ||
| python -m pip install -U docutils | ||
| python -m pip install -U docutils pygments |
There was a problem hiding this comment.
Perhaps we should create requirements.txt and pin the versions ofdocutils and pygments.
There was a problem hiding this comment.
Perils of reading commit info from emails and not checking the latest! Feel free to bump the docutils/sphix reqs, they are current as of April 2020, so 0.17.z / 4.y.z may be more appropriate.
A
| Pygments ~= 2.9.0 | ||
| Sphinx ~= 4.0.2 | ||
| docutils ~= 0.17.1 | ||
|
|
There was a problem hiding this comment.
Only question I'd have is if better to pin to compatible releases or all future? (~= vs >=) - historically been unpinned so I think that means the latest release has always been used.
(but I am not best placed to make this call, as no idea if e.g. previously there have been breaking changes to PEP rendering due to dependency changes, or the risk appetite for this in the future vs new features that may or may not be used)
A
|
all good to merge? |
|
is there any other concern here? |
|
@ofek matter of time to look at the PR (which I have), deciding if we want it, and then watching python.org/dev/peps to make sure nothing breaks. |
|
Any update on this? |
|
None from me, but I'm not the only PEP editor. I suspect we are all just busy with other stuff at the moment. |
|
Since it's been so long I'm going to re-trigger CI just to make sure. If it's still good I'm for merging this though. |
See: #1571 (comment)