refactor!: drop 3.8 support

[antazoey]

What I did

requires:

ApeWorX/eip712#44
ApeWorX/evm-trace#59
ApeWorX/ethpm-types#118
ApeWorX/eth-pydantic-types#7

ApeWorX/evmchains#7

fixes: #

note: changes from running pyupgrade --py39-plus

How I did it

How to verify it

Checklist

• All changes are completed
• New test cases have been added
• Documentation has been updated

[fubuloubu]

Okay with dropping 3.8 for Ape v0.8

For now, if the move to add official 3.12 support can be added to downstream ApeWorX packages firs, and then to Ape within 0.7.x series, they can be accomplished non-breaking

[fubuloubu]

I also think some of our processes were using 3.8 since as type checking, linting, and docs

They can maybe upgrade to 3.9 or 3.11 (not sure which is better)

[antazoey]

Processes are all using 3.10 as far as I can tell, I don't know what is best either.
Edit: on separate PR, we can change those to be '3.x' so it uses the latest.

[banteg]

i've been devving on 3.12 and haven't seen any issues.

i'm pro dropping 3.9 too, dropping just 3.8 doesn't offer much interesting features.

installing any python version is trivial nowadays with pyenv or rye, and it's not like ape is used in any embedded systems where you can't upgrade.

[antazoey]

i've been devving on 3.12 and haven't seen any issues.

the main issue on 3.12 right now (which is soon to be fixed) is that there are some Ethereum packages importing from pkg_resources which may not be installed. We are soon to having this fully fixed, there is a separate PR for it.

i'm pro dropping 3.9 too, dropping just 3.8 doesn't offer much interesting features.

We are trying to wait closer to EOL for 3.9. There is actually a nice 3.8drop affordance we gained - typing improvements. No longer are we cursed to importing List, Dict, we can finally use list[str] style syntax for typing

[NotPeopling2day]

@antazoey I tried to resolve the merge conflicts but please double check!