Git submodule or pip requirements?

Question

git

There is a git repository with a django site, there is another repo with a frequently-changed application. Changing the application leads to a change in the site code, all this is spinning in virtualenv. What is the best way to arrange dependencies: register the repository in requirements.txt and update via pip install --upgrade -r req.txt, or via git submodules and give the update to the farm git submodule update? Is there any fundamental difference between the two approaches?

Answer 1

I'm from the php world, but still. Previously, they used a submodule - everything would be fine, but there are situations when the history changes in a dependent repository and git cannot find the required commit. Now we use the package manager - there seems to be no big problems.

Answer 2

Obviously, the pip solution is a "Python-world" solution. While the git submodule is an adhoc solution ("hack") based on the features of the specific VCS that is currently in use.