I noticed `typing.get_type_hints()` returns Optional[Any] as a type hints if the default value of the argument is None:

```
$ python
Python 3.9.0 (default, Oct 24 2020, 15:41:29)
[Clang 11.0.3 (clang-1103.0.32.59)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> from typing import Any, get_type_hints
>>> def hello(name: Any = None):
...     pass
...
>>> get_type_hints(hello)
{'name': typing.Optional[typing.Any]}
```

I know typing.get_type_hints() wraps the user's type annotation with Optional when the default value of the argument is None. But it is needless to wrap Any with Optional because Any already contains None. It would be better not to wrap it with Optional when the user's annotation is Any.

There is actually a difference between Any and Optional[Any]. Try the following using e.g. mypy:

def f(a: Optional[Any]):
    a+1

def g(a: Any):
    a+1

You'll get an error in f but not in g.

So this behavior is not a bug.

Wow, I don't know that behavior. Thank you for your wisdom!