Skip to content
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

Remove deprecated personal namespace #3350

Merged
merged 8 commits into from Apr 17, 2024

Conversation

fselmo
Copy link
Collaborator

@fselmo fselmo commented Apr 16, 2024

What was wrong?

Related to Issue #2854
Closes #2844

How was it fixed?

  • Remove the personal namespace from the codebase and all tests and mentions of it.
  • Get rid of any tests and test fixtures related to locking and unlocking accounts.
  • Use the account set up via the keyfile in the geth fixture as the "known" account and expose its address and private key for test fixtures to be able to pass to relevant tests.
  • Since I re-ran the test fixture, I also updated it to use the latest geth that can be used - 1.13.14 (No Cancun rules still since we are still waiting for devmode support from Geth).

Todo:

  • Clean up commit history
  • Add or update documentation related to these changes
  • Add entry to the release notes

Cute Animal Picture

1000022290

@fselmo fselmo force-pushed the remove-deprecated-personal-namespace branch from 794c359 to b0598af Compare April 16, 2024 21:29
@fselmo fselmo force-pushed the remove-deprecated-personal-namespace branch from b0598af to 61ae400 Compare April 16, 2024 21:35
- Remove the idea of an ``unlockable_account``. Since we are no longer
  using an API to "unlock", there's no need to test it. Instead, use
  the keyfile account as the ``from`` in ``eth_sendTransaction`` and
  anywhere that an account that is "known" by the node needs to be used.

- Set up the keyfile account as the known account for testing.
@fselmo fselmo force-pushed the remove-deprecated-personal-namespace branch from 61ae400 to 5aeb7f2 Compare April 16, 2024 21:47
@fselmo fselmo marked this pull request as ready for review April 16, 2024 21:49
fselmo added a commit to fselmo/web3.py that referenced this pull request Apr 16, 2024
@fselmo fselmo changed the title Remove deprecated personal namespace Remove deprecated personal namespace Apr 16, 2024
@fselmo fselmo force-pushed the remove-deprecated-personal-namespace branch from 2dad79b to 8a47aeb Compare April 16, 2024 22:15
fselmo added a commit to fselmo/web3.py that referenced this pull request Apr 16, 2024
bonus: re-generate fixture for making sure we have all changes in related to ethereum#3350
Copy link
Contributor

@pacrob pacrob left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm!

@fselmo fselmo force-pushed the remove-deprecated-personal-namespace branch from 07d08d9 to fa23f25 Compare April 17, 2024 17:56
- Clean up some unnecessary changes related to removing personal namespace
- bonus: re-generate fixture for making sure we have all changes in related to ethereum#3350
@fselmo fselmo force-pushed the remove-deprecated-personal-namespace branch from fa23f25 to 71407ca Compare April 17, 2024 21:20
@fselmo fselmo merged commit 3b200a5 into ethereum:main Apr 17, 2024
54 of 57 checks passed
fselmo added a commit that referenced this pull request Apr 17, 2024
- Clean up some unnecessary changes related to removing personal namespace
- bonus: re-generate fixture for making sure we have all changes in related to #3350
@fselmo fselmo deleted the remove-deprecated-personal-namespace branch April 17, 2024 21:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Remove personal namespace support and tests
2 participants