Mercurial > kallithea
annotate requirements.txt @ 5806:f33cc4af706b
tests: finally block also needs to be executed if api_call itself fails
The cleanup code (finally block) should be executed as soon as something what
changes the db fails.
I don't remember which one but one of these tests failed and caused all the
others to fail as well because the database wasn't cleaned up after the first
failure. That made finding the root cause more difficult then it should have
been.
author | domruf <dominikruf@gmail.com> |
---|---|
date | Tue, 12 Apr 2016 22:45:46 +0200 |
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 . |