The first thought we had was to modify the version of Project B that had been installed in the virtualenv for Project A. So ideally we need to get Project B to load in that specific branch. And lets be honest, what are the odds they will be “positively” affected? In my experience, its zero. Simply promoting the branch to master is not ideal if there is a problem with the branch potentially all projects that depend on Project A could be affected. But, we want test a different branch of Project A. (pip and setup.py, etc.) Project B pip installs Project A, and in the requirements.txt it is listed like a normal git repository dependency. These projects are both python based, so they are using the normal tools. Recently I had an interesting situation: We had some new code, lets call it project A, that had not been merged into master, but it needed to used by another project (project B) to see if a certain bug had been fixed. 18 April 2016 Working with branches and a requirements.txt
0 kommentar(er)
