Mercurial > kallithea
annotate requirements.txt @ 7713:cba155768085
middleware: drop fix_PATH
Back out ccbdff90e5a0. That seemed like an odd hack. In order to work properly,
it should not only be applied for protocol access middleware, but also for web
UI and for commands. So evidently, it is not really necessary.
The problem it describes is fixed much better in 5e501b6ee639 by setting the
right python executable in the hook scripts, further improved in 1bafb2d07709
and 6df08d78f8e7 to *actually* use the right python executable.
author | Mads Kiilerich <mads@kiilerich.com> |
---|---|
date | Mon, 07 Jan 2019 00:00:18 +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 . |