Mercurial > kallithea
annotate requirements.txt @ 7229:e5a7f8f41370
issues: backout special whitespace handling
This is essentially a backout of commit 32e1e0745d3c.
That commit checked for whitespace at the beginning of the matched issue
reference, and explicitly retained it in the resulting link text.
The way this was handled is not only suboptimal, e.g. a set of 4 spaces
would still be reduced to 1, but is also not actually necessary: if
whitespace before the issue reference is not required, then it does not need
to be specified in the issue pattern, and if it _is_ required, then a
positive lookbehind assertion can be used instead.
author | Thomas De Schampheleire <thomas.de_schampheleire@nokia.com> |
---|---|
date | Fri, 16 Feb 2018 22:30:51 +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 . |