Closed pacrob closed 7 months ago
I suppose so, though v0.2.0
supported py37 as a max, which none of our libs officially support.
If the goal is to keep pins as low as possible without breaking, that then calls https://github.com/ethereum/web3.py/issues/3239 into question too.
I can see either way - leaving it as 0.2.0
or bumping to 0.2.3
. It doesn't look like we're enforcing <3.7 in 0.2.0
, we're just not testing against it.
What was wrong?
The previous capping of
hexbytes
dep was unneeded as it wasn't actually breaking for this lib.How was it fixed?
Opened to
hexbytes>=0.2.3
- the first version that tested against>=py38
Todo:
[x] Clean up commit history
[x] Add or update documentation related to these changes
[x] Add entry to the release notes
Cute Animal Picture