blender-cloud/requirements-dev.txt

-r ../pillar-python-sdk/requirements-dev.txt
-r ../pillar/requirements-dev.txt
-r ../attract/requirements-dev.txt
-r ../flamenco/requirements-dev.txt
-r ../pillar-svnman/requirements-dev.txt

-e ../pillar-python-sdk
-e ../pillar
-e ../attract
-e ../flamenco
-e ../pillar-svnman
-e .
Added requirements-dev.txt It just links to the requirements-dev.txt files of the subprojects. 2017-03-07 14:21:07 +01:00			`-r ../pillar-python-sdk/requirements-dev.txt`
			`-r ../pillar/requirements-dev.txt`
			`-r ../attract/requirements-dev.txt`
			`-r ../flamenco/requirements-dev.txt`
Added SVNMan extension 2017-11-03 13:42:41 +01:00			`-r ../pillar-svnman/requirements-dev.txt`
Don't install subpackages as editable in requirements.txt Doing this would require editable (and thus writable) checkouts, which we don't have on our production machines. 2017-03-08 17:17:53 +01:00
			`-e ../pillar-python-sdk`
			`-e ../pillar`
			`-e ../attract`
			`-e ../flamenco`
Added SVNMan extension 2017-11-03 13:42:41 +01:00			`-e ../pillar-svnman`
Add `-e .` to requirements-dev.txt 2018-08-29 12:24:45 +02:00			`-e .`