Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bugfix for detecting pynames in aliased import statements #230

Merged
merged 1 commit into from Jan 4, 2018

Conversation

soupytwist
Copy link
Contributor

This case wasn't being handled correctly; e.g, the pyname for "foo" in
import foo as bar evaluates to an AssignedName instead of an
ImportedModule. This is similar to the module name in a "from" import,
adding a special case to handle it in the same way.

Fixes #229

This case wasn't being handled correctly; e.g, the pyname for "foo" in
`import foo as bar` evaluates to an `AssignedName` instead of an
`ImportedModule`. This is similar to the module name in a "from" import,
adding a special case to handle it in the same way.
@soupytwist
Copy link
Contributor Author

@mcepl, want to take a look? Good to have another pair of eyes on it.

@mcepl
Copy link
Contributor

mcepl commented Jan 4, 2018

Looks reasonable. I cannot vouch for the code, because I really forgot most of Rope API, but I don't see anything obviously stupid and there are tests, so it should be OK.

@soupytwist soupytwist merged commit 5f84456 into python-rope:master Jan 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants