Open() on path that exceeds 248 char limit results in "FileNotFoundError: [Errno 2] No such file or directory"

Bug report

Attempting to open or appending paths to sys.path with paths that length exceed the 248 character limit results in incorrect errors. In the case of opening paths that exceeded the limit, rather than an error pointing to the path length being exceeded we see a file not found. A similar error handling issue is prevalent with appending paths that exceed the limit to sys.path. In this case when trying to access the module you will receive a module not found error. I am now aware the path limit can be disabled on installation or later but these false flags led me astray while debugging.

Reproduction Steps:

• Create a text file whose path exceeds 248 characters
• Attempt to read/write from that file
  or
• Create a Python module whose path exceeds 248 characters
• Attempt to import that module from an external directory by appending the path to sys.path

Environment

• CPython versions tested on: 3.10.4
• Operating system and architecture: Windows x64

Commencez par reproduire le comportement signalé sur Windows x64 avec Python 3.10.4 : ouvrez un fichier dont le chemin dépasse 248 caractères, puis testez l’importation d’un module depuis un chemin trop long ajouté à sys.path. Suivez les échecs d’ouverture et d’importation pour identifier l’endroit où la condition de longueur est perdue. C’est terminé lorsque les deux cas signalent une erreur précise de longueur de chemin au lieu de FileNotFoundError ou ModuleNotFoundError.