| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
We've been down this road before and it was either not accepted or shortly reverted, though I don't remember why. There is some history to dig up and review here, though past rejection doesn't necessarily mean we must still stick to the status quo. |
Sorry, something went wrong.
|
Right, so we need to be able to build using pre-downloaded tools not in the venv, so fix 1 and 2 are not needed. We could add a check for other missing tools in this guard: Lines 55 to 59 in b863b9c In this case, python_docs_theme was missing, and isn't easy to check for. So I guess "if in doubt, make clean venv applies :) (I think I've seen a similar problem for another tool that could be checked easily, but I can't remember what it was so I'll address it if it comes up again.) What's left? I think the bonus .PHONY change is still useful. Shall I refactor this PR or make a new, cleaner one? |
Sorry, something went wrong.
I went for a new, clean PR, please see #99396. And let's close this one, thanks for the background! |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Problem
I started getting this error:
That's because I have no venv so it can't find the theme.
The problem is we have this, which looks for Sphinx in the venv or $PATH:
And in my case it's finding it in my $PATH, so this guard passes:
cpython/Doc/Makefile
Line 55 in b863b9c
But I don't get this warning:
cpython/Doc/Makefile
Lines 65 to 66 in b863b9c
Fix
Two things (aka let's do it like the devguide)
https://github.com/python/devguide/blob/05f6d0c8d09bd757440e0346190dbd62e06c7251/Makefile#L9-L10
https://github.com/python/devguide/blob/05f6d0c8d09bd757440e0346190dbd62e06c7251/Makefile#L58-L64
Bonus
Whilst we're changing Docs/Makefile, PR #98189 recently fixed some missing .PHONY targets. 👍
I expect missing .PHONY targets will happen again, because it's normal to copy/paste a target, and forget (or not know) to update the long .PHONY line right at the top.
Let's do as @zware suggested and define them right next to each target: #98189 (comment)
We do this at Pillow and at work, it helps a lot. (I'll add it to the devguide and PEPs too.)