-
Notifications
You must be signed in to change notification settings - Fork 24
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
Pinned versions in requirements.txt are too restrictive #39
Comments
I don't think you should be using |
This is correct, but doesn't change the issue I am facing. I'm actually not using requirements.txt, I just install it via Pip from PyPi. After getting the dependency conflicts, I looked into requirements.txt, noticed the pinned versions, and submitted this issue, assuming this is what gets installed when I install from PyPi. That's not the case, you are right the setup.py dependencies are what actually gets installed, and this is what causes my issue. They are still too narrow, especially as strict requirements on very basic commonly used libraries are made, not only on exotic ones. |
In that case the issue shouldn't be mentioning requirements.txt, but setup.py. Either way @ehtec, I think you'll love version |
same as me.
|
New Feature Request
Checklist
Current Limitation
The requirements in the requirements.txt file are too restrictive, because they pin exact package versions. They make it impossible to install moralis in my environment together with other packages.
Feature / Enhancement Description
Please don't make such restrictive dependency requirements, I don't think they are necessary for proper operation. For example only specify a minimum version.
Alternatives / Workarounds
Currently I need to bypass the dependency checks and install dependencies manually to get it work.
The text was updated successfully, but these errors were encountered: