-
Notifications
You must be signed in to change notification settings - Fork 83
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
build: Set only lower bounds on core dependencies #1382
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1382 +/- ##
=======================================
Coverage 97.53% 97.53%
=======================================
Files 63 63
Lines 3808 3808
Branches 538 538
=======================================
Hits 3714 3714
Misses 55 55
Partials 39 39
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report at Codecov.
|
This is still a Draft PR as I want to go through and test if these lower bounds that we have can be safely pushed down any lower. |
4bce69e
to
8e54d20
Compare
This reverts commit 7e75730.
* Update softwareRequirements in codemeta.json to use required lower bounds on all core dependencies - Applies lower bounds from PR #1382 * Add CPython implimentation to programmingLanguage codemeta.json metadata
Description
Following @henryiii's and @hynek's advice (for the core dependencies now, we'll get to discussing the ones for the
setup.py
extras later) only place lower bounds on the core library dependencies, which have all reached maturity in their API.This was more recently motivated by the fact that Henry pointed out that we'll be excluding use of
Click
v8.0.0
(when it is released, currently onlyv8.0.0a1
on PyPI), but there's no reason to want to bound Click to onlyv7.X
orv8.X
.Thanks also to a very good comment from @tacaswell this also reverts the effects of PR #1378:
Checklist Before Requesting Reviewer
Before Merging
For the PR Assignees: