- marked as enhancement
-
assigned issue to
Missing import support for pip requirements
In a requirements.txt file, -r other_deps.txt
is a valid syntax for importing requirements from another file. I am using this feature for managing my project dependencies for different environments.
Those prod, stage and dev files are importing common dependencies from common.txt file.
On VersionEye, -r other_deps.txt
is not a valid syntax. The tool can't resolve -r
parameter.
Comments (5)
-
-
@ulgens Can you please post your common.txt file here? Or is it somewhere on Bitbucket/GitHub?
-
- changed status to resolved
@ulgens OK. I just fixed it. Lines which are starting with
-r
are ignored now. But you can flip the switch for multiple*.txt
files and if they are in the same repository and same branch they will be merged automatically into 1 logical project at VersionEye. -
@ulgens Here I described the new behaviour: https://blog.versioneye.com/2016/06/29/auto-merge-for-git-projects/.
-
reporter Oh, sorry for delay. Thanks for the blog post btw, it's excited to see a new feature as a result of a bug report :) I'll try the new behaviour.
- Log in to comment
Thanks for reporting this. But it's not a bug, it's a feature request ;) The pip parser currently can only handle 1 file. So it works like designed. Supporting file imports would be a new feature on VersionEye.