Emma Smith
Emma Smith
We do run docker compose down twice: https://github.com/getsentry/self-hosted/blob/bacecf4fedde3635d27433d00c833890af086fc7/install/turn-things-off.sh#L8-L12 so my guess is one of the containers is in the removal state when we run the down command again. I cannot...
I have experienced this issue before (on v.2.6.0)
In getsentry/sentry#39281 @alexandernst found that we did not catch his compose was too old... which is odd because we do check for this. Perhaps our check is not working 100%...
mypyc + setuptools + PEP 517: types are checked and code is compiled to C at each stage of the build
FWIW, I've found that https://github.com/pypa/build is like 10x+ faster when using PEP 517 to build wheels vs `pip wheel`.
I suggest we close this in favor of discussing this on typing-sig and having it standardized in a PEP, I'd love to see something like `{'foo': int}` be shorter syntax...
I actually would prefer this to be on by default. The superseding PEP 634 says: > For cases such as sealed classes and enums, where the patterns are all known...
The semantics of `MYPYPATH` are entirely up to the type checker using it. In addition, we do not want to add anything in site packages to the `MYPYPATH`, as that...
@woolinsilver-kainos agreed the error message could be improved. Would you like to submit a PR to improve it?
@sjosegarcia where are you running mypy from? if it is in site packages then you will get this error
Coming back to this: a) this issue is no longer nearly as important now that #5701 is resolved b) maybe we can lift the restriction on MYPYPATH entirely, since the...