You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I notice that nearly every requirement is locked down/pinned. This is extremely restrictive on projects that depend on this package. It is common for developers to pin the oldest compatible version of something, then to allow up to the next breaking release. So, perhaps for example:
# requirements.txt
...
requests>=2.5.1,<3.0 # declare that you require at least 2.5.1, but allow up to the next breaking release.
...
The text was updated successfully, but these errors were encountered:
Hi, been nearly 3 weeks. Any chance someone with package authority could at least respond to this? The current state is really rather overbearing. Requests, in particular is a very popular 3rd party package and therefore in use by many things, Forcing a hard requirement to such an old version of requests means that Mendeley cannot be installed alongside more modern packages without creating dependency conflicts that we, as consumers of this SDK, cannot overcome.
While this issue with requests is, by itself a very real issue, it also serves as an example. Nearly all of the dependencies on 3rd party packages should be relaxed as stated above.
Hi, I notice that nearly every requirement is locked down/pinned. This is extremely restrictive on projects that depend on this package. It is common for developers to pin the oldest compatible version of something, then to allow up to the next breaking release. So, perhaps for example:
The text was updated successfully, but these errors were encountered: