Jonas Obrist

huh that's a new one. what environment is this running in (local/ec2/ecs/...)? if this is running on AWS, have you checked your security group that there's nothing in there blocking...

not really, you can at least document your current implementation. I know this is a lot of work, but for people to actually use it (which is required to find...

this project doesn't use distutils from what I can see. what exactly are you suggesting should change?

ah, i was only looking in packaging related code.

how is this relevant? we run black on our own code, not untrusted input. it's not part of the actual package and only used in development. also, if I were...

> * checking in `poetry.lock` for faster package resolution I do not like this for libraries. CI should run against the latest versions

I wonder if we should just port this to GHA like I did for aiodynamo. There I also made it so [poetry only locks in one step](https://github.com/HENNGE/aiodynamo/blob/3cbf4d859be01283e0ef6c92bc275870fb4d08f0/.github/workflows/workflow.yml#L6-L21) that is re-used...

@darylweir thank you for this report. I agree it would make sense for `table_exists` to also allow `.updating`. But there's probably also a use case (eg our test suite) for...

`.gitignore` because my local `.gitignore` starts with `.*` so it excluded itself and I didn't notice... `poetry.lock` not included on purpose (see dimaqqs comment), in my opinion libraries should not...

> Reproducible dev/test environment is always a nice thing to have. That sounds nice, but is it that useful for a library? Because what you get from `pip install aiodynamo`...