[issue6323] Py3.1 pdb doesn't deal well with syntax errors

2009-06-22 Thread nlopes
nlopes added the comment: That fixes it. It seems to be introduced when committing a fix for issue #1038. -bash-3.2$ svn diff -r 58126:58127 Lib/pdb.py Index: Lib/pdb.py === --- Lib/pdb.py (revision 58126) +++ Lib/pdb.py

[issue6323] Py3.1 pdb doesn't deal well with syntax errors

2009-06-22 Thread nlopes
nlopes added the comment: I can reproduce it in my OpenBSD 4.5 box (only one I tried). This simple code: print(3 seems to break the pdb flow in python 3.1 the way Andreas described it. When I tried in 2.7, this is what I get: -bash-3.2$ ./python -m pdb test.py SyntaxError: ('invalid s

[issue6266] cElementTree.iterparse & ElementTree.iterparse return differently encoded strings

2009-06-21 Thread nlopes
Changes by nlopes : Removed file: http://bugs.python.org/file14324/_elementtree.diff ___ Python tracker <http://bugs.python.org/issue6266> ___ ___ Python-bugs-list mailin

[issue6266] cElementTree.iterparse & ElementTree.iterparse return differently encoded strings

2009-06-21 Thread nlopes
nlopes added the comment: Don't mind what I just said. I overlooked the N. I couldn't figure out what was going wrong with your solution. That works. Mine is a ... aham. :) -- ___ Python tracker <http://bugs.python.

[issue6266] cElementTree.iterparse & ElementTree.iterparse return differently encoded strings

2009-06-21 Thread nlopes
nlopes added the comment: I got pure gibberish output, but I know why. It was a compilation gone wrong. To get the output as ElementTree, I think instead of parcel = Py_BuildValue("sN", (prefix) ? prefix : "", makestring(uri)); it should be parcel = Py_BuildValue(&qu

[issue6266] cElementTree.iterparse & ElementTree.iterparse return differently encoded strings

2009-06-20 Thread nlopes
nlopes added the comment: You're right about the conversion to Latin1. I actually played a bit with makestring before going in another direction (although not very good) because makestring alone wasn't giving what is intended. I'll try to check tomorrow a good approach for th

[issue6266] cElementTree.iterparse & ElementTree.iterparse return differently encoded strings

2009-06-20 Thread nlopes
nlopes added the comment: This is a pretty dumb patch, but it does it's job. Basically it decodes the utf-8 encoded prefix and uri. Then, encodes it into Latin1. Probably there are better ways of doing this and those ideas are welcome. Patch attached. -- keywords: +patch nosy: +n