New submission from anatoly techtonik techto...@gmail.com:
issue6964 is closed, so this is a reminder that discussion over the actual
issue is not finished yet.
--
components: 2to3 (2.x to 3.x conversion tool)
messages: 166111
nosy: techtonik
priority: normal
severity: normal
status:
Martin v. Löwis mar...@v.loewis.de added the comment:
What is the issue that you are reporting here?
If you think there is an issue with Python, please state explicitly what the
issue is. I think issue 6964 was invalid to begin with: it complained that the
new module is no longer, but
anatoly techtonik techto...@gmail.com added the comment:
You're mistaken. issue6964 is not about deleting `new` module in Python 3, it
is about the 2to3 tool skipping this fact without warning.
--
___
Python tracker rep...@bugs.python.org
Florent Xicluna florent.xicl...@gmail.com added the comment:
It was answered in the previous message by Georg, on the related issue:
http://bugs.python.org/issue6964#msg93032
Bottom line: move over to the types module *before* running 2to3.
(the thread is very short, and clearly states that
anatoly techtonik techto...@gmail.com added the comment:
From the user point of view that's the same as saying for optparse:
Bottom line: move over to the argparse module *before* running 2to3.
--
resolution: invalid -
___
Python tracker
anatoly techtonik techto...@gmail.com added the comment:
Bottom line: The fact that 2to3 isn't capable to fix import new automatically
doesn't mean it should not warn that this code should be fixed manually.
--
___
Python tracker
Martin v. Löwis mar...@v.loewis.de added the comment:
It does mean exactly that. 2to3 is not designed or intended to ever issue
warnings. So if your request is that it should issue a warning, I'm closing it
as won't fix.
--
resolution: - wont fix
status: open - closed
Florent Xicluna florent.xicl...@gmail.com added the comment:
The documentation for porting is already clear about using -3 switch.
http://docs.python.org/dev/howto/pyporting.html#eliminate-3-warnings
The argparse module is different because it is not in the stdlib in 2.6, and
you can stay with
anatoly techtonik techto...@gmail.com added the comment:
My request is that after running 2to3 my code still doesn't work in Python 3.
--
resolution: wont fix -
status: closed - open
___
Python tracker rep...@bugs.python.org
anatoly techtonik techto...@gmail.com added the comment:
Florent: It is the same. new module just doesn't need replacement, because
its functionality is in the language, therefore it is no different saying.
--
___
Python tracker
Martin v. Löwis mar...@v.loewis.de added the comment:
Please don't reopen issues.
--
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15420
___
Changes by Martin v. Löwis mar...@v.loewis.de:
--
resolution: - wont fix
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15420
___
___
Martin v. Löwis mar...@v.loewis.de added the comment:
IIUC, your request is not should issue a warning, but 2to3 should make sure
that the resulting code runs on Python 3.
It is beyond the scope of 2to3 to provide such guarantees. Users are required
to test the conversion result, as it cannot
anatoly techtonik techto...@gmail.com added the comment:
Please don't reopen issues.
Please don't ask for such silly stuff. You can understand the reason why this
issue was opened, so why do you keep closing it if the issue is not resolved?
The scope of this issue never changed, Martin. If
Changes by Florent Xicluna florent.xicl...@gmail.com:
--
nosy: -flox, loewis
resolution: - wont fix
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15420
___
15 matches
Mail list logo
