anatoly techtonik techto...@gmail.com added the comment:
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.
--
nosy: +techtonik
Georg Brandl ge...@python.org added the comment:
Bottom line: move over to the types module *before* running 2to3.
--
nosy: +georg.brandl
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6964
New submission from Rene Dudfield ill...@users.sourceforge.net:
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.
--
components: 2to3 (2.x to 3.0 conversion tool)
Quentin Gallet-Gilles qgal...@gmail.com added the comment:
The 'new' module has been removed in python 3.0. The documentation
advices you to use the 'types' modules instead
(http://docs.python.org/library/new.html).
I'm also pretty sure you get a message for this module if you enable the
Rene Dudfield ill...@users.sourceforge.net added the comment:
Hi,
yes it does report a warning with 2.6, thanks.
python2.6 -3 -c import new
-c:1: DeprecationWarning: The 'new' module has been removed in Python
3.0; use the 'types' module instead.
I guess it should be a TODO item with 2to3.
Changes by Georg Brandl ge...@python.org:
--
assignee: - benjamin.peterson
nosy: +benjamin.peterson
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6964
___
Brett Cannon br...@python.org added the comment:
Benjamin can re-open if he wants, but having 2to3 emit warnings about
deprecated modules is not what it is meant to do. 2to3 is supposed to only
be run once you are running against 2.6 w/ no DeprecationWarning or
Py3KWarning being raised, which
