CC: @ddfisher @JukkaL @markshannon
PEP 484 currently says:
An optional type is also automatically assumed when the default value is
None, for example::def handle_employee(e: Employee = None): ...This is equivalent to::
def handle_employee(e: Optional[Employee] = None) -> None: ...
This was intended as saving some typing in a common case, but I've received strong feedback from some quarters that this is not consistent and a bad idea. There are other places where None is allowed but none of them automatically add Optional (to the contrary).
So far it hasn't mattered much for mypy users because mypy doesn't have Optional support, but that's soon going to change (the --strict-optional flag is becoming more reliable) so if we're going to change this, now would be a good time. Thoughts? If we don't change this soon it will probably be too late.
Michael0x2a, bluicezhen, pkch, artwyman, TheGhostHuCodes and 6 morecjw296 and Hocnonsense
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4