Mercurial > kallithea
annotate requirements.txt @ 7992:5a092b5f0d98
routing: fix files_annotate_home annotate value to be compatible with Routes >= 2
The routing entry for files_annotate_home had annotate=True. That primarily
served to let the controller files.index differentiate files_annotate_home from
files_home and files_home_nopath . Anything true can work.
test_files.py is creating files_annotate_home URLs in an odd way: Instead of
explicitly specifying it is a files_annotate_home URL, it passes expected
controller parameters and expects routing to find a URL that would provide
these parameters. It thus also has to specify the otherwise "invisible"
annotate value. For Routes < 2, True works just fine. For Routes >= 2, it seems
to expect values that actually can be encoded in URLs.
Thus, instead of True, use '1'.
author | Mads Kiilerich <mads@kiilerich.com> |
---|---|
date | Mon, 11 Nov 2019 01:56:23 +0100 |
parents | 941548131765 |
children |
rev | line source |
---|---|
5741
941548131765
setup: introduce requirements.txt for use as "pip install -r requirements.txt" as alternative to "setup.py develop"
Mads Kiilerich <madski@unity3d.com>
parents:
diff
changeset
|
1 # requirements.txt file for use as "pip install -r requirements.txt" as a |
941548131765
setup: introduce requirements.txt for use as "pip install -r requirements.txt" as alternative to "setup.py develop"
Mads Kiilerich <madski@unity3d.com>
parents:
diff
changeset
|
2 # readthedocs compatible alternative to "pip install -e ." which is a working |
941548131765
setup: introduce requirements.txt for use as "pip install -r requirements.txt" as alternative to "setup.py develop"
Mads Kiilerich <madski@unity3d.com>
parents:
diff
changeset
|
3 # alternative to "setup.py develop" which doesn't work with Mercurial 3.7 |
941548131765
setup: introduce requirements.txt for use as "pip install -r requirements.txt" as alternative to "setup.py develop"
Mads Kiilerich <madski@unity3d.com>
parents:
diff
changeset
|
4 . |