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

Deprecate web3.iban module #2537

Closed
pacrob opened this issue Jun 24, 2022 · 8 comments
Closed

Deprecate web3.iban module #2537

pacrob opened this issue Jun 24, 2022 · 8 comments

Comments

@pacrob
Copy link
Contributor

pacrob commented Jun 24, 2022

What was wrong?

Ethereum IBAN is a dead standard and can be removed.

How can it be fixed?

Add deprecation notices to the module so it can be removed in a future version of web3.py.

@dbfreem
Copy link
Contributor

dbfreem commented Jul 8, 2022

could this be deprecated in the v5 branch and removed in v6?

@fselmo
Copy link
Collaborator

fselmo commented Jul 8, 2022

could this be deprecated in the v5 branch and removed in v6?

That would be ideal 👌

@dbfreem
Copy link
Contributor

dbfreem commented Jul 8, 2022

I couldn't find any documentation saying that IBAN is deprecated. Was thinking about picking this issue up but wanted to make sure I got the correct wording in the deprecation warning. Can you point me to anything that says what replaced IBAN or is it just a complete deprecation without a replacement.

@fselmo
Copy link
Collaborator

fselmo commented Jul 8, 2022

I couldn't find any documentation saying that IBAN is deprecated. Was thinking about picking this issue up but wanted to make sure I got the correct wording in the deprecation warning. Can you point me to anything that says what replaced IBAN or is it just a complete deprecation without a replacement.

I haven't looked much into this. Deferring to @pacrob here... 👀

@pacrob
Copy link
Contributor Author

pacrob commented Jul 8, 2022

I think it is a feature that was created but never caught on. It is per @pipermerriam that it is a "a dead standard that is largely if not entirely unused". I spent a while combing through github and couldn't find any recent code using it or similar features in web3.js, ethers, etc.

It will be complete deprecation without replacement, but I think that it would be better to add deprecation notices in v6 and completely remove later. That will give any folks who might still be using it time to change and/or make noise about it.

@fselmo
Copy link
Collaborator

fselmo commented Jul 8, 2022

That will give any folks who might still be using it time to change and/or make noise about it.

If we decide to deprecate it, I lean towards adding deprecation in v5 and removing in v6 since we're getting breaking changes in now. I think the buffer between v5 and v6 should be enough. We are porting all major changes that aren't breaking over to v5... I think that gives users enough time to hang out in v5 until all warnings are addressed.

@pacrob
Copy link
Contributor Author

pacrob commented Jul 8, 2022

I defer to your leanings, deprecate in 5 & eliminate in 6 it is!

@fselmo
Copy link
Collaborator

fselmo commented Jul 15, 2022

closed by #2563 (v5) and #2565 (v6)... thanks once again @dbfreem 👌

@fselmo fselmo closed this as completed Jul 15, 2022
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

No branches or pull requests

3 participants