typing.get_origin behaves differently between standard collections and typing collections

Bug report

typing.get_origin behaves differently between standard collections, and typing collections
more specifically

get_origin(dict) is None, while get_origin(Dict) is <class 'dict'>
the same holds for other collections as well

This is true from python3.9 where support for standard collections was added

to my understanding dict should be able to be a drop-in replacement for Dict, which is not true in case relying on get_origin

I suggest updating get_origin to return the relevant class for builtin collections as opposed to None which returns today

note, this might mean a breaking change, as pointed out here, but id does make Dict and dict behave more similarly

Commencez par reproduire typing.get_origin pour dict, Dict et les autres paires de collections décrites dans le rapport. Lisez l’implémentation existante de get_origin et ses tests, puis examinez la discussion sur le risque de rupture de compatibilité. Le travail est considéré comme terminé lorsque le comportement attendu a été convenu et que les cas de collections pertinents sont couverts de manière cohérente.