On Mon, Mar 24, 2008 at 3:51 PM, Mike Meyer <[EMAIL PROTECTED]> wrote: > Complicated? Really? On extra option, and an optional print when you > emit a line? And if you don't read the 2to3 code when debugging, or > don't consider yourself smart, I'd say that's your problem. Seriously, > the pdb 'l' command will shows you the source file when you're > debugging with it. Having a comment there that the code you're looking > at was generated by 2to3 should help avoid confusion if you decide > that's what needs to change.
(I said I was finished, and I am, but I'll answer this anyway, as I evidently misunderstood what you said, and I don't want to leave my misunderstandings as a last word, as that would misrepresent the debate.) You are right, it's not complicated, I misunderstood you as suggesting that the debugger showed the orginal 2.6 code and not the the 3.0 code. Which would be complicated, but also much more useful, and it would also make your parallell to compiled code and debugging relevant. Indeed such a solution would remove this problem when debugging. But this would more or less mean that 2to3 needs to compile the 2.6 code directly to pyc-files, as I understand it. -- Lennart Regebro: Zope and Plone consulting. http://www.colliberty.com/ +33 661 58 14 64 _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
