As it stands in ethereum-execution@2.18.0rc5.dev1, EEST's packages are exposed at the top-level as our source directories are organized underneath ./src/ethereum_spec_tests:
https://github.com/ethereum/execution-specs/tree/69bfc231862811d5010c884c9a893828dee425de/src/ethereum_spec_tests

I.e., you can do:

uvx --with ethereum_execution==2.18.0rc5.dev1 ipython

then interactively import them as

import cli

for all off:

cli
config
ethereum_clis
ethereum_test_base_types
ethereum_test_checklists
ethereum_test_exceptions
ethereum_test_execution
ethereum_test_fixtures
ethereum_test_forks
ethereum_test_rpc
ethereum_test_specs
ethereum_test_tools
ethereum_test_types
ethereum_test_vm
pytest_plugins

Imo, cli, config and pytest_plugins are too generic and should be changed in some way, shape or form.

But should we prefix everything with ethereum_test?

• Then we have ethereum_clis (which is a good name imo) and ethereum_test_cli (which is very close to ethereum_clis), see also chore(weld): Move src/cli -> src/ethereum_test_cli #2154.

Instead should we namespace everything as ethereum_test.execptions?

First step is have a concept we agree on and then to PR it.