antazoey

> Found `.cache` referenced in ape-solidity and ape-cairo. ape-vyper does not appear to leverage this. Any others I might be missing? * Don't worry about ape-cairo, is no longer really...

> Long term thinking, maybe we could maybe create a temporary package structure that we build from on the fly every time we compile. I think we kinda do this...

We could add those configs separately to the `ape-solidity` config so the user could sometimes do this: ```yaml compile: cache_folder: my/custom/cache solidity: import-paths: - my/custom/cache ```

> Not sure how actively developed this is, but this might work too (since ghapi is dead): https://github.com/sigmavirus24/github3.py Pros: * Good license * More trusted code Nuetral: * Probably won't...

Hello! I am guessing the fixture is indeed session-isolation (both via pytest and chain-isolation) but the tests themselves are still "function" scoped so they get the function isolation (including chain-restore)...

We have also talked about a `SecretStorageAPI` type thing

Is this a problem with the framework?

Amazon has base images for Python Linux: https://github.com/aws/aws-lambda-base-images/blob/python3.9/Dockerfile.python3.9

changed to a feature request, specifically for the docker image to work with aws but note you can make your own image and use ape as a base

we already have plans to rename in 0.8