DRY up future.builtins imports #3467

Closed
opened 2020-10-12 11:38:18 +00:00 by chadwhitacre · 3 comments

As part of the Python 3 port we are importing many future.builtins across the codebase. Right now we directly import from future.builtins, which subtle differences across modules. Can we tighten that up?

As part of the Python 3 port we are importing many future.builtins across the codebase. Right now we directly import from future.builtins, which subtle differences across modules. Can we tighten that up?
chadwhitacre added the
code
normal
task
n/a
labels 2020-10-12 11:38:18 +00:00
chadwhitacre added this to the Support Python 3 milestone 2020-10-12 11:38:18 +00:00
chadwhitacre self-assigned this 2020-10-12 11:38:24 +00:00
Author
(https://github.com/tahoe-lafs/tahoe-lafs/pull/854)

Does it matter all that much? It's temporary scaffolding that will all be ripped out as soon as Python 2 support is dropped.

Does it matter all that much? It's temporary scaffolding that will all be ripped out as soon as Python 2 support is dropped.
Merged in <https://github.com/tahoe-lafs/tahoe-lafs/commit/962662b315b72d81e75a7253a177b9bdfae3790e>
exarkun added the
fixed
label 2020-10-31 23:26:58 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#3467
No description provided.