Sebastian Rittau
Sebastian Rittau
I'm still stumped what the problem here is. I have the same results as @erictraut when testing this PR locally. It really behaves as if the changes to the python-dateutil...
Here's what I'm going to do: Comment out the offending line in the test cases and merge this PR if the tests pass. Then I'm going to open another PR...
Still waiting for python/mypy#15687.
I have no time to look into the pytype error at the moment. @rchen152: Could have a look? Otherwise I'll try to narrow the problem down tomorrow.
The pytype fix was fairly straightforward: Remove the quotes around bound types from the TypeVar, which is cleaner anyway: https://github.com/python/typeshed/pull/10370/commits/45482b5cecfc71cae0766de9b5382bcf9b46e091
(Test failure is a GitHub hickup, I will restart the failed test.)
```python class A: ... class B: A: A reveal_type(B.A) ``` ```$ mypy --version mypy 1.7.1 (compiled: yes) $ mypy foo.py foo.py:6: note: Revealed type is "foo.A" Success: no issues found...
Unlike #7870, we could just introduce a type alias for `Any` and call it `UnsafeNone` or some other kind of name that includes `None`?
> Do we want their IDE to show re.Match[str] | UnsafeNone or re.Match[str] | MaybeNone or re.Match[str] | SometimesNone or something else? I believe that showing them something other than...
Just to clarify: I'm still in favor of using a type alias in some way, although documenting it in some other way would be better than the status quo.