Opened at 2020-10-12T11:38:18Z
Closed at 2020-10-31T23:26:58Z
#3467 closed task (fixed)
DRY up future.builtins imports
Reported by: | chadwhitacre | Owned by: | chadwhitacre |
---|---|---|---|
Priority: | normal | Milestone: | Support Python 3 |
Component: | code | Version: | n/a |
Keywords: | Cc: | ||
Launchpad Bug: |
Description
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?
Change History (4)
comment:1 Changed at 2020-10-12T11:38:24Z by chadwhitacre
- Owner set to chadwhitacre
- Status changed from new to assigned
comment:2 Changed at 2020-10-12T11:46:36Z by chadwhitacre
comment:3 Changed at 2020-10-12T12:01:56Z by exarkun
Does it matter all that much? It's temporary scaffolding that will all be ripped out as soon as Python 2 support is dropped.
comment:4 Changed at 2020-10-31T23:26:58Z by exarkun
- Resolution set to fixed
- Status changed from assigned to closed
Note: See
TracTickets for help on using
tickets.
https://github.com/tahoe-lafs/tahoe-lafs/pull/854