fa232daa10
Hopefully that works. This was confusing. Grepping for 3.6 to see how other places pin it there were a bunch of normal pins in .txt files and then some comment-but-actually-instruction comments in the -raw files. There is a readme in the requirements folder but it just says what instructions are allowed. Not why you would want to add them, seems to very high cognitive load setup. Trying to run the recompile_requirements.py script it did some stuff then quit because it couldn't find python3.7. Yeah I don't have that installed. It doesn't try to use pyenv or anything, just runs venv expecting you have everything installed? Turns out you take the name of the requirements file you added the instructions to (eq requirements-test.txt-raw -> test) and run it with that as argument. The requirements file you modify should be the highest level one that mentions the requirement you want to pin. Anyway I edited the qutebrowser.text-raw one because that seems like the main one and it mentions MarkupSafe (because of jinja2?) and ran `scripts/dev/recompile_requirements qutebrowser` in my existing venv. Lets see what the CI thinks. Also got lots of `pkg_resources==0.0.0` in a bunch of requirements files which seems problematic. |
||
|---|---|---|
| .. | ||
| apparmor | ||
| nsis | ||
| requirements | ||
| userscripts | ||
| Makefile | ||
| cheatsheet.svg | ||
| org.qutebrowser.qutebrowser.appdata.xml | ||
| org.qutebrowser.qutebrowser.desktop | ||
| qutebrowser.rcc | ||
| qutebrowser.spec | ||
