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
RFE: don't pin dependencies exactly #13
Comments
Oh, sorry for this. |
I'll look into it - unfortunately as it is work related, I'll have to obtain legal sign-off to submit a PR, which will slow things down. |
Okay, I will do it myself |
This issue and #14 are fixed in 1.10 release (already published) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This extension pins every dependency exactly. That's a fine strategy for an end-user application, but for a library it's not really the right thing to do, as you inevitably end up with conflicting dependencies in a project that consumes the library. Please would you consider having more liberal dependencies (eg. markdown>3.0, rather than markdown==3.0.1) for example.
Thanks for a great extension, by the way!
The text was updated successfully, but these errors were encountered: