[issue6964] import new fails

2012-07-22 Thread anatoly techtonik 

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

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6964
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue6964] import new fails

2009-09-23 Thread Georg Brandl 

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
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue6964] import new fails

2009-09-22 Thread Rene Dudfield 

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)
messages: 92974
nosy: illume
severity: normal
status: open
title: import new fails
type: behavior
versions: Python 3.1

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6964
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue6964] import new fails

2009-09-22 Thread Quentin Gallet-Gilles 

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
warnings at interpreter startup in python 2.6.

--
nosy: +quentin.gallet-gilles

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6964
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue6964] import new fails

2009-09-22 Thread Rene Dudfield 

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.

cheers,

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6964
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue6964] import new fails

2009-09-22 Thread Georg Brandl 

Changes by Georg Brandl ge...@python.org:


--
assignee:  - benjamin.peterson
nosy: +benjamin.peterson

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6964
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue6964] import new fails

2009-09-22 Thread Brett Cannon 

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 would have covered this issue.

If the docs don't make this clear then they need to be changed to do so 
(and that should be a new issue anyway).

--
nosy: +brett.cannon
resolution:  - wont fix
status: open - closed

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6964
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com