python - Using git to manage virtualenv state: will this cause problems? -

i have git , virtualenv set in way suits needs and, far, hasn't caused problems. i'm aware setup non-standard , i'm wondering if more familiar virtualenv's internals can point out if, , where, it's go wrong.

my setup

my virtualenv inside git repository, git set ignore bin , include directories , in lib except site-packages directory.

more precisely, .gitignore file looks this:

*.pyc  # ignore virtualenv stuff except actual packages # /bin /include /lib/python*/* !/lib/python*/site-packages  # ignore easyinstall , setuptools /lib/python*/site-packages/easy-install.pth /lib/python*/site-packages/setuptools.pth /lib/python*/site-packages/setuptools-* /lib/python*/site-packages/pip-* 

with arrangement -- , else working on checkout of project -- can use virtualenv , pip normal following advantages:

1. if updates or installs package , pushes changes, else pulls changes automatically gets update: don't need notice requirements.txt file has changed or post-receive hook magic.

2. there no network dependencies: code make application work lives in git repository.

i'm aware works pure-python packages, that's i'm concerned @ moment.

does know of other problems approach should aware of?

if have -e items in requirements.txt - in other words if have editable dependencies described in format using git version control system run issues when src directory committed. if add /src .gitignore can avoid problem, installation adds pointer in site-packages location, need it!