Mercurial > kallithea
annotate requirements.txt @ 8039:4e565c5d7b7d
lib: establish py3 compatible strategy for string handling: introducing safe_bytes and deprecating safe_str
The meaning of safe_str will change when moving to py3. All use of safe_str is
thus tech debt that we have to chop off, mostly by moving to either
safe_unicode or safe_bytes ... or dropping because we know what we are doing
and rely on the improved type safety in py3.
author | Mads Kiilerich <mads@kiilerich.com> |
---|---|
date | Sun, 15 Dec 2019 20:00:38 +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 . |