It even supports SVN/SSH checkouts and .egg distributed packages.
[1] http://www.pip-installer.org/en/latest/requirement-format.ht...
I studied the requirement file documentation and I couldn't find a solution. It seems that to take advantage of this feature in pip I have to write a setup.py, and as I've mentioned that really doesn't make sense for my type of project. Or am I misunderstanding something?
pip freeze > requirements.txt
pip install -f requirements.txt
You are by no means required to make your source code a module or anything like that. If you use the above with a virtualenv you can isolate different models for different projects and have them frozen at different versions. You are also able to modify requirements.txt to include version specific information. packagename==3.4.0 now locks packagename to 3.4.0 when pip goes to install it.
I'm assuming your git directory looks like this:
$DIR
\
| - requirements.txt
| - fileone.py
| - filetwo.py
| - folder
\
| - __init__.py
| - filethree.py
pip install -r requirements.txt