El De-dog-lo

> ape-vyper does not appear to leverage this. Any others I might be missing? It might in the future as vyper is adding module libraries

> Doesn't look like it was influenced by input metadata at all, so settings changes or path changes shouldn't influence it at all like with Solidity. Correct, Vyper's CBOR only...

Not sure how actively developed this is, but this might work too (since ghapi is dead): https://github.com/sigmavirus24/github3.py

> github3.py has a large source dist size: 36 MB No way we are using this lol

This is the service I was thinking of: https://www.4byte.directory/

> Want me to take a look ? could test adding it here: https://github.com/ApeWorX/ape/blob/main/src/ape/types/signatures.py#L21

btw, this is great for loading already set environment variables, but for those looking to manage environment variables it is recommended to use something specific to your development environment like...

No, I think it could also be resolved by having an image w/ gcc in it, or otherwise having a binary wheel for whatever that architecture is

could just be extending `ReceiptAPI.__str__` so you can just do `print(receipt)` (but keep `__repr__`)

> hmm, it seems like there are many bugs in `ape compile` It does need some attention at the moment, however this specific issue should be easy to fix if...