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
import new fails #51213
Comments
python3.1 >>> import new
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
ImportError: No module named new 2to3-3.1 doesn't mention how to change it. |
The 'new' module has been removed in python 3.0. The documentation I'm also pretty sure you get a message for this module if you enable the |
Hi, yes it does report a warning with 2.6, thanks. python2.6 -3 -c "import new" I guess it should be a TODO item with 2to3. cheers, |
Benjamin can re-open if he wants, but having 2to3 emit warnings about If the docs don't make this clear then they need to be changed to do so |
Bottom line: move over to the types module *before* running 2to3. |
Damn it. I've run 2to3 during setup.py phase and went smoothly, but when I run examples the package fails. It should at least warn about this "import new". It should not be that hard to catch. |
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: