Open DistributedDoge opened 4 months ago
Some type annotations in fork_types.py for each fork use bytes type, and some use Bytes alias imported from ..base_types.
fork_types.py
bytes
Bytes
..base_types
class Transaction: ... data: Bytes class Account: ... code: bytes class Log: ... data: bytes
Issue #752 suggests that spec would be more consistent if Bytes alias was applied everywhere to match surrounding code.
This change should not result in any functional difference as Bytes is alias for bytes.
For every Log.data and Account.code in src/ethereum/$fork_name/fork_types.py replaced type annotation like so: bytes => Bytes.
Log.data
Account.code
src/ethereum/$fork_name/fork_types.py
What was wrong?
Some type annotations in
fork_types.py
for each fork usebytes
type, and some useBytes
alias imported from..base_types
.fork_types.py
Issue #752 suggests that spec would be more consistent if
Bytes
alias was applied everywhere to match surrounding code.This change should not result in any functional difference as
Bytes
is alias forbytes
.How was it fixed?
For every
Log.data
andAccount.code
insrc/ethereum/$fork_name/fork_types.py
replaced type annotation like so:bytes
=>Bytes
.Cute Animal Picture