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
fix_callable should be dropped from lib2to3 / changed #55649
Comments
Since the callable return in 3.2, should the fix_callable be dropped from lib2to3 or should it be adjusted to make distinction between 3.1 and 3.2 situation? I'm not sure if latter is possible. |
I suspect that this will not be the last time that a fix is version dependent. I think that the 2to3 distributed with 3.x should fix to 3.x. Otherwise, the fix would have to do an 'if version...' dance. (Perhaps the version distributed with 2.7 should do *that*.) But I would defer to those maintaining it. |
Someone should probably ask python-dev. callable, of course, doesn't work in 3.1. |
The decision should be left to the user. |
Benjamin added a note in d9571fb37269. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: