Skip to content

[3.15] gh-150579: use lazy imports for concurrent.futures (GH-150585)#152975

Open
miss-islington wants to merge 1 commit into
python:3.15from
miss-islington:backport-423ae0f-3.15
Open

[3.15] gh-150579: use lazy imports for concurrent.futures (GH-150585)#152975
miss-islington wants to merge 1 commit into
python:3.15from
miss-islington:backport-423ae0f-3.15

Conversation

@miss-islington

@miss-islington miss-islington commented Jul 3, 2026

Copy link
Copy Markdown
Contributor

This module has a manual lazy import hack using __getattr__. Now that lazy imports exist and cannot be disabled, this could use lazy imports instead.

Key differences: this will now show up in sys.lazy_modules when accessed. Error messages should be a bit better without the wrapper __getattr__ involved. That's the only differences I can think of.
(cherry picked from commit 423ae0f)

Co-authored-by: Henry Schreiner henryfs@princeton.edu
Signed-off-by: Henry Schreiner henryfs@princeton.edu
Co-authored-by: Gregory P. Smith greg@krypto.org

…0585)

This module has a manual lazy import hack using `__getattr__`. Now that lazy imports exist and cannot be disabled, this could use lazy imports instead.

Key differences: this will now show up in sys.lazy_modules when accessed. Error messages should be a bit better without the wrapper `__getattr__` involved.  That's the only differences I can think of.
(cherry picked from commit 423ae0f)

Co-authored-by: Henry Schreiner <henryfs@princeton.edu>
Signed-off-by: Henry Schreiner <henryfs@princeton.edu>
Co-authored-by: Gregory P. Smith <greg@krypto.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants