Closed fselmo closed 5 months ago
Return ipc path even if it doesn't yet exist. See #2911
Remove the ethPM
module, deprecated in #2953
Better UX for provider-specific middlewares. See: https://github.com/ethereum/web3.py/issues/2770
edit: issue created (#2990)
Remove the miner API, deprecated in #2856.
Here, then upstream libs:
AttributeDict
updates #3105
web3 v7 should set hexbytes>=1.0.0
.
Bottom pins for our other libs should move up to at least the release that dropped py37 support
Where possible, have all errors thrown inherit from Web3Exception
, or ENSException
. See #1864.
I updated the task list to include all the commented items in this issue. We can try to add items to the task list in the future so we can keep track of what's done and what isn't.
Return ipc path even if it doesn't yet exist. See #2911
@kclowes was this completed with the merging of #2911 ?
Return ipc path even if it doesn't yet exist. See #2911
@kclowes was this completed with the merging of #2911 ?
Not done. Just needs the if exists
part removed and return the path.
All issues that were being tracked here are now completed and released as of 7.0.0-beta.5
. There may be other changes added into v7
as we update the library to use newer major versions of dependencies but those can be tracked separately before stable gets released.
Can I see a link explaining the motivation for a major v7 changing lots of things?
Can I see a link explaining the motivation for a major v7 changing lots of things?
Hey @MathiasExorde. Each issue here should have its own link, though the migration documentation provides a good summary of it all together. Most of the changes were quite small, though technically breaking. Those have to be aggregated and need to wait until the next major version cycle to be addressed. Some of the bigger changes, like the middleware moving to a class-based architecture, helped close out long-standing tickets such as the ability to batch requests which had been an open issue since 2018. Hope that helps.
Main thread for tracking breaking changes slated for the next major version release of web3.py -
v7
. This will be an evolving issue much like #1416 was forv6
.Candidates: