[issue42839] SourceFileLoader does not (fully) accept path-like objects

Petr Viktorin added the comment: I just filed the slightly more general bpo-45127. -- nosy: +petr.viktorin ___ Python tracker ___

[issue42839] SourceFileLoader does not (fully) accept path-like objects

Change by Filipe Laíns : -- nosy: +FFY00 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue42839] SourceFileLoader does not (fully) accept path-like objects

Guido van Rossum added the comment: If Brett's theory is right, compile() has a bug though -- it shouldn't plug a non-string into the code object. Or possibly the code object constructor should reject such objects (or extract the string). -- ___

[issue42839] SourceFileLoader does not (fully) accept path-like objects

Brett Cannon added the comment: importlib is probably not os.PathLike-clean due to its bootstrapping restrictions of not getting to use anything implemented in Python from 'os' (i.e. if it isn't being managed in posixmodule.c then it probably won't work). If you follow the traceback it's

[issue42839] SourceFileLoader does not (fully) accept path-like objects

Guido van Rossum added the comment: Maybe Brett can help? -- nosy: +brett.cannon, gvanrossum ___ Python tracker ___ ___

[issue42839] SourceFileLoader does not (fully) accept path-like objects

New submission from favonia : If one uses the loader created by importlib.machinery.SourceFileLoader(module_name, path) in a meta path finder, where path is not a str, then the following error would happen at the moment the module is being imported. Note that, the error would not occur if