Dependency tree with requirements.txt

[mjtorn]

Hi!

I'm trying to accomplish a purely Github-based deployment scheme for multiple packages in private repos.

If setup.py / install_requires knew about Github, I might be able to use only that and preserve requirements.txt for bootstrapping an environment. This is not the case, however, and I prefer pip and requirements.txt anyway :)

So the situation is package foo has a requirements.txt which goes all the way to

-e git+ssh://[email protected]/.../foodb.git#egg=foodb

Now that package's requirements.txt is not considered.

Wouldn't it be nice if there was an option like

-e git+ssh://[email protected]/.../foodb.git#egg=foodb -r foodb/requirements.txt

to make it possible to install these deps?

[mjtorn]

The -r in my example would look for the relative-path requirements.txt after installation. It could be something else as well, but that or using an ssh url – -r git+ssh://.../requirements.txt – would be clean and not require writing a client for github raw urls and their tokens.

[dstufft]

I feel pretty strongly that this is an incredibly bad idea.

[mjtorn]

I'm not sure I agree with it being an incredibly bad idea. Surely there are things to consider when resolving dependencies, so it wouldn't be easy.

This hasn't been a real issue in ages, though, and I forgot all about it :D It's easy enough to work with a flat requirements.txt which is crafted in development and deployed with configuration management.