The docstring of func process_message in vm/interpreter.py is wrong

[Alleysira]

Metadata

• Hardfork: From Frontier to Cancun

What was wrong?

Hello, developers! This is just a Inappropriate expression in docstring.

Take the func process_message() in vm/interpreter.py in Cancun as an example:

execution-specs/src/ethereum/cancun/vm/interpreter.py

Lines 204 to 240 in fcd1275

	def process_message(message: Message, env: Environment) -> Evm:
	"""
	Executes a call to create a smart contract.
	Parameters
	----------
	message :
	Transaction specific items.
	env :
	External items required for EVM execution.
	Returns
	-------
	evm: :py:class:`~ethereum.cancun.vm.Evm`
	Items containing execution specific objects
	"""
	if message.depth > STACK_DEPTH_LIMIT:
	raise StackDepthLimitError("Stack depth limit reached")
	# take snapshot of state before processing the message
	begin_transaction(env.state, env.transient_storage)
	touch_account(env.state, message.current_target)
	if message.should_transfer_value and message.value != 0:
	move_ether(
	env.state, message.caller, message.current_target, message.value
	)
	evm = execute_code(message, env)
	if evm.error:
	# revert state to the last saved checkpoint
	# since the message call resulted in an error
	rollback_transaction(env.state, env.transient_storage)
	else:
	commit_transaction(env.state, env.transient_storage)
	return evm

I think here process_message() is just a smart contract call that executes the code of message, instead of what is described in the func's docstring:

Executes a call to create a smart contract.

I checked all vm/interpreter.py from Frontier to Cancun, it seems that all forks have this issue. Perhaps a slight adjustment to the description could help clarify this.

Thanks for you attention!