[issue37162] new importlib dependencies csv, email and zipfile

Brett Cannon added the comment: @serhiy: mind opening a new issue for your zipfile.Path worry? -- ___ Python tracker ___ ___

[issue37162] new importlib dependencies csv, email and zipfile

Serhiy Storchaka added the comment: @staticmethod def _switch_path(path): from contextlib import suppress import zipfile from pathlib import Path with suppress(Exception): return zipfile.Path(path) return Path(path) Oh, I did not know

[issue37162] new importlib dependencies csv, email and zipfile

Change by Brett Cannon : -- stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue37162] new importlib dependencies csv, email and zipfile

Matthias Klose added the comment: yes, that's for the minimal package. zipfile is found in Lib/importlib/_bootstrap_external.py Again, it's just a question here, having found an unmotivated distutils import before in one of the standard modules. -- resolution: -> not a bug

[issue37162] new importlib dependencies csv, email and zipfile

Brett Cannon added the comment: The imports are on purpose but they are not required for import to run, just like importlib.resources isn't necessary. -- ___ Python tracker

[issue37162] new importlib dependencies csv, email and zipfile

Serhiy Storchaka added the comment: I have not found zipfile here. email is used for parsing METADATA and PKG-INFO. It replaces the rfc822 module. cvs is used for parsing RECORD and SOURCES.txt. Actually using it for for parsing SOURCES.txt is improper as it might contain double quotes or

[issue37162] new importlib dependencies csv, email and zipfile

Anthony Sottile added the comment: at least for debian, the motivation is to provide a `pythonX.X-minimal` and a `pythonX.X` package -- the former ~mostly just contains the interpreter and the latter includes the stdlib (I'm interested as well, hit this packaging 3.8 for deadsnakes)

[issue37162] new importlib dependencies csv, email and zipfile

Jason R. Coombs added the comment: I imagine that importlib.metadata isn’t imported at bootstrap time, only after the import infrastructure is ready. I think an early failure to import one of those dependencies is desirable. What is the reasoning behind deferring the imports and why does it

[issue37162] new importlib dependencies csv, email and zipfile

Change by Karthikeyan Singaravelan : -- nosy: +barry, jaraco ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue37162] new importlib dependencies csv, email and zipfile

New submission from Matthias Klose : compared to 3.8 alpha4, beta1's importlib has three new dependencies csv, email and zipfile. Is this intended, or should the toplevel imports in importlib.metadata be moved into the functions where these are once used? -- components: Library