[issue6964] import new fails

anatoly techtonik 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 _

[issue6964] import new fails

Georg Brandl added the comment: Bottom line: move over to the types module *before* running 2to3. -- nosy: +georg.brandl ___ Python tracker ___ __

[issue6964] import new fails

Brett Cannon 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 would have cover

[issue6964] import new fails

Changes by Georg Brandl : -- assignee: -> benjamin.peterson nosy: +benjamin.peterson ___ Python tracker ___ ___ Python-bugs-list maili

[issue6964] import new fails

Rene Dudfield 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. cheers, -- ___

[issue6964] import new fails

Quentin Gallet-Gilles 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 warnings at interpreter

[issue6964] import new fails

New submission from Rene Dudfield : python3.1 >>> import new Traceback (most recent call last): File "", line 1, in ImportError: No module named new 2to3-3.1 doesn't mention how to change it. -- components: 2to3 (2.x to 3.0 conversion tool) messages: 92974 nosy: illume severity: nor