Skip to content
This repository has been archived by the owner on Nov 30, 2023. It is now read-only.

Switch to absolute imports for Python3 compatability #460

Merged
merged 4 commits into from
Feb 10, 2019

Conversation

jarondl
Copy link
Contributor

@jarondl jarondl commented Jan 28, 2019

Part of #412

Started by:
futurize -nw -f libfuturize.fixes.fix_absolute_import .
And followed up by fixing a few local problems.

Note that it includes commits that are part of #457, so we should merged #457 first

Another backwards compatible change as part of google#412

by running:

    futurize -nw -f libfuturize.fixes.fix_print_with_import  .
Part of google#412

Started by:
futurize -nw -f libfuturize.fixes.fix_absolute_import  .
And followed up by fixing a few local problems.
jarondl added a commit to jarondl/transitfeed that referenced this pull request Jan 28, 2019
Part of google#412

Started with `futurize -nw --stage1 .`, but had to do a few manual
changes.

Note that it includes commits from google#460
transitfeed has many import cycles, which is a bad thing. Converting
to absolute import exposed some of them. This changes adds the minimal
changes required to make imports work, for example by moving some
types from `problems.py` to `errors.py`.
@stotala stotala merged commit e5e4751 into google:master Feb 10, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants