You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
move builtin interfaces like ERC20 to ethereum.ercs instead of vyper.interfaces
Motivation
ERC20 et al are clearly ethereum-specific (ERC in fact standing for "Ethereum Request for Comment"), not something related to vyper- the language.
Specification
per title
Backwards Compatibility
breaks backwards compatibility. we could have a deprecation period for the 0.4.x series where import ERC20 from vyper.interfaces is deprecated but still works; meanwhile the new and recommended way is import ERC20 from ethereum.ercs.
Simple Summary
move builtin interfaces like ERC20 to
ethereum.ercs
instead ofvyper.interfaces
Motivation
ERC20 et al are clearly ethereum-specific (ERC in fact standing for "Ethereum Request for Comment"), not something related to vyper- the language.
Specification
per title
Backwards Compatibility
breaks backwards compatibility. we could have a deprecation period for the 0.4.x series where
import ERC20 from vyper.interfaces
is deprecated but still works; meanwhile the new and recommended way isimport ERC20 from ethereum.ercs
.References
loosely related to #2431 and #2814
Copyright
Copyright and related rights waived via CC0
The text was updated successfully, but these errors were encountered: