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
Plugin dependencies #12
Comments
You mean plugins depending on other plugins? I think a metadata field in the .plugin file is enough |
How would that work? We could:
Or maybe, in requirements.txt:
|
Assuming the dependency names are just strings, we can always use "['foo','bar']" which can be created using json.dumps but it should not be necessary, I like your version 6 |
Yep, I think version 6 is more clean... |
So, let’s actually trim out all of that nonsense and leave in two.
[Requirements]
a = 0.1.0
b = 0.2.0
c = 0.5.0
|
any thoughts, ideas, or such? |
I'm ok with both |
Re-thinking, I am more inclined to the second one version... |
install_plugin
option install the pluginsThe text was updated successfully, but these errors were encountered: