-
-
Notifications
You must be signed in to change notification settings - Fork 14.7k
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
python312Packages.web3: 6.5.0 -> 7.2.0 #373563
base: master
Are you sure you want to change the base?
Conversation
@ofborg build python313Packages.web3 |
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/prs-ready-for-review/3032/5083 |
@ofborg build python313Packages.web3 |
6075b3d
to
7e18f96
Compare
@GaetanLepage Thanks. I also went ahead and fixed other places regarding the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To be applied to all files.
|
||
pythonImportsCheck = [ "trie" ]; | ||
|
||
meta = with lib; { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
meta = with lib; { | |
meta = { |
The with
pattern is discouraged now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in general, or just for the metadata?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In general, this pattern is not ideal (costly and can lead to mistakes).
But here, I am talking about the with lib;
specifically.
Keeping with lib.maintainers;
for instance is fine IMO.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
changed, anyhow.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
--------- Impacted packages on 'x86_64-linux' ---------
12 packages added:
python312Packages.ckzg (init at 2.0.1) python312Packages.eth-bloom (init at 3.1.0) python312Packages.eth-tester (init at 0.12.0-beta.2) python312Packages.py-evm (init at 0.10.1-beta.2) python312Packages.pyunormalize (init at 16.0.0) python312Packages.trie (init at 3.0.1) python313Packages.ckzg (init at 2.0.1) python313Packages.eth-bloom (init at 3.1.0) python313Packages.eth-tester (init at 0.12.0-beta.2) python313Packages.py-evm (init at 0.10.1-beta.2) python313Packages.pyunormalize (init at 16.0.0) python313Packages.trie (init at 3.0.1)
3277 packages updated:
Probably not :D
pkgs/top-level/python-packages.nix
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are too many rebuilds, this should go to staging
@GaetanLepage correct me if I am wrong here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indeed, good point. Why is that though ?
@hellwolf are you touching a deep package ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it all because the web3.py package itself.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I plan to do a nixpkgs-review pr` when things settle, and see how many changes follow.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, my interest has been to maintain slither-analyzer echidna, which transitively dependon on web3.py
.
if that's what you meant by "deep packages".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I plan to do a nixpkgs-review pr` when things settle, and see how many changes follow.
Well, nixpkgs-review
directly pulls the evaluation rebuilds from GitHub. So, if the GitHub action has labeled the PR with the 2501-5000 rebuilds
tag, it will be the same in nixpkgs-review
.
Why are so many packages depending on web3.py
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if the GitHub action has labeled the PR with the 2501-5000 rebuilds tag, it will be the same in nixpkgs-review.
Ah, I didn't know!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are so many packages depending on web3.py ?
No idea!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But probably some other packages, not web3.py itself.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Splitting PR possible, just more work.
I get 404 for one of the sources: https://codeload.github.com/mlodewijck/pyunormalize/tar.gz/refs/tags/4b45c576567fb0293acb93a308c97cbaba3caa5f
|
right. that should be a ref, not tag. I will fix |
I made one more round clean up according to the suggestion. @GaetanLepage And please give it another try @siraben |
Thanks. A few more are still not applied. |
what are they?
Okay, I will create a new TODO list. |
@GaetanLepage I have tidied the code up. I also have fixed commit messages. |
2dd6bea
to
f686ac5
Compare
changelog = "https://github.com/ethereum/eth-typing/blob/v${version}/docs/release_notes.rst"; | ||
description = "Common type annotations for Ethereum Python packages"; | ||
homepage = "https://github.com/ethereum/eth-typing"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
changelog = "https://github.com/ethereum/eth-typing/blob/v${version}/docs/release_notes.rst"; | |
description = "Common type annotations for Ethereum Python packages"; | |
homepage = "https://github.com/ethereum/eth-typing"; | |
description = "Common type annotations for Ethereum Python packages"; | |
homepage = "https://github.com/ethereum/eth-typing"; | |
changelog = "https://github.com/ethereum/eth-typing/blob/v${version}/docs/release_notes.rst"; |
Previously at: #342749
Things done
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)Add a 👍 reaction to pull requests you find important.