Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Link additional Pipfiles from root one #122

Open
filips123 opened this issue Dec 13, 2019 · 0 comments
Open

Link additional Pipfiles from root one #122

filips123 opened this issue Dec 13, 2019 · 0 comments

Comments

@filips123
Copy link

It should be possible to link additional Pipfiles from the root one, and install dependencies from all files at once.


Even if one of Pipfile benefits is that you can have one file instead of multiple requirements.txt files, there are still some cases where you would want multiple separate files.

For example, you may want to have some completely separated functionality in separate folder, which would require its own dependencies. Then root Pipfile would specify something like "load additional/Pipfile if exists" which will them automatically install that additional dependencies. This would be useful for some kind of program plugin functionallyty, as plugins could just be a folders with Pipfile, and their dependencies would be automatically installed when the plugin folders will be present.


So, there should be a few types of loading this. Here, I will just provide examples, but without any real syntax that would be used.

First two should be just classic "load path/to/Pipfile" and "load path/to/Pipfile if it exists". So, first one should fail if file does not exst and second one should not.

Next should be some more advenced loading like "load plugins//Pipfile" and "load path/to/Pipfile". So, wildcart should be handled correctly to install dependencies in all pathes that match.

And the third is quite similar to second one, so they could probably be implemented/used together. This would be support classic regexes when loading patches. So you could have "load plugins/[^disabled-]*/Pipfile" which would load all "plugins" which aren't disabled (so without disabled- prefix).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant