annotate requirements.txt @ 6533:5d60c9a391cd

pullrequests: introduce "action objects" for PR creation Inspired by the command design pattern, this attempts the following: * move policy and business logic from controllers into the model, * move validation, authorization and execution logic closer together in the code, * establish a reusable pattern for modelling higher-level concepts (like "create a new PR iteration"), * make error handling more well-defined, and independent of the controller layer, and * provide clear separation between, one one hand, the validation and authorization of a request, and on the other, the actual execution.
author Søren Løvborg <sorenl@unity3d.com>
date Fri, 03 Mar 2017 15:34:31 +0100
parents 941548131765
children
Ignore whitespace changes - Everywhere: Within whitespace: At end of lines:
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 .