Closed tiangolo closed 3 years ago
Merging #36 (9150aa2) into master (18f4021) will not change coverage. The diff coverage is
n/a
.
@@ Coverage Diff @@
## master #36 +/- ##
=======================================
Coverage 80.41% 80.41%
=======================================
Files 7 7
Lines 878 878
=======================================
Hits 706 706
Misses 172 172
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact)
,ø = not affected
,? = missing data
Powered by Codecov. Last update 18f4021...9150aa2. Read the comment docs.
:tada: This PR is included in version 0.3.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:
And I don't know if it would make sense to make it require smart-open[gcp] directly, but that would couple Pathy to Google Cloud Storage. Or maybe it could make sense to add optional dependencies for Pathy similar to smart-open, so pathy[gcp] would include smart-open[gcp].
Pathy already has a "gcs" package extra that includes the GCS library dep, but it could be interesting to add "smart_open[gcs]" to our "gcs" dependencies. I wonder if having "smart_open" as a required dep and then "smart_open[gcs]" as an extra would conflict?
⬆️ Upgrade
smart-open
pin, to fixbotocore
requiringurllib3
< 1.26When standard
pip
installs the latestpathy
, it installssmart-open
< 3.0.0, and it requiresbotocore
, which in turn requiresurllib3
< 1.26. But it seems something else also requiresurllib3
, and that one is resolved first, sopip
(the current version) installs the newerurllib3
and shows a warning about the conflicting dependency.But when using Pex, it doesn't show a warning, it fails right away.
The funny thing is,
pip
, with the new resolver (with--use-feature=2020-resolver
) can detect it, then it uninstalls the first resolvedurllib3
and installs the olderurllib3
1.25.x. But there's no way to force Pex to use that new resolver :pensive:The new version of
smart-open
3.0.0 doesn't requirebotocore
, instead it has new optional requirements:or
This PR only increases the pin range for
smart-open
.There would also be needed a Pathy version bump and release :grimacing: :sweat_smile:
And I don't know if it would make sense to make it require
smart-open[gcp]
directly, but that would couple Pathy to Google Cloud Storage. Or maybe it could make sense to add optional dependencies for Pathy similar tosmart-open
, sopathy[gcp]
would includesmart-open[gcp]
.