[issue2888] pprint produces different output in 2.6 and 3.0

Facundo Batista <[EMAIL PROTECTED]> added the comment: Commited in 64446, thank you all! -- resolution: -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> ___

[issue2888] pprint produces different output in 2.6 and 3.0

Changes by Facundo Batista <[EMAIL PROTECTED]>: -- assignee: fdrake -> facundobatista ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Pyt

[issue2888] pprint produces different output in 2.6 and 3.0

Manuel Kaufmann <[EMAIL PROTECTED]> added the comment: Documentation fix. Added file: http://bugs.python.org/file10464/pprint.rst.diff ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue2888] pprint produces different output in 2.6 and 3.0

Fred L. Drake, Jr. <[EMAIL PROTECTED]> added the comment: The attached test_pprint.diff adds a test for this problem. This test passes for the py3k and release25-maint branches and fails for the trunk. Applying Manuel Kaufmann's pprint.diff patch to the trunk causes it to pass as well. I'll lea

[issue2888] pprint produces different output in 2.6 and 3.0

Fred L. Drake, Jr. <[EMAIL PROTECTED]> added the comment: The patch doesn't include a new test to cover this case. That needs to be written and applied to both trunk and py3k. -- versions: +Python 2.6 -Python 3.0 ___ Python tracker <[EMAIL PROTECTED]

[issue2888] pprint produces different output in 2.6 and 3.0

Fred L. Drake, Jr. <[EMAIL PROTECTED]> added the comment: I will note that Python 2.5 matches Python 3.0 in this regard. ___ Python tracker <[EMAIL PROTECTED]> ___ _

[issue2888] pprint produces different output in 2.6 and 3.0

Fred L. Drake, Jr. <[EMAIL PROTECTED]> added the comment: The version seen in py3k is the intended formatting; I don't remember anything about a change, but given the time I've not had in following commit messages and discussions, I could easily have missed something. I'm strongly in favor of th

[issue2888] pprint produces different output in 2.6 and 3.0

Terry J. Reedy <[EMAIL PROTECTED]> added the comment: I think I *slightly* prefer the 'new' way. Was pprint.py changed between 2.6 and 3.0? Or is the change a side-effect of 3.0 changes? Or of 2to3 if that was used? (In glancing through it, I did not see anything that needed change) Fred, I am a

[issue2888] pprint produces different output in 2.6 and 3.0

Facundo Batista <[EMAIL PROTECTED]> added the comment: It's not a 2.6 bug, as it behaves exactly as the documentation states. In Py3 it *is* different the result than the documentation. However, it's not clear to me if this behaviour is changed deliberately or by mistake (personally, I prefer th

[issue2888] pprint produces different output in 2.6 and 3.0

Manuel Kaufmann <[EMAIL PROTECTED]> added the comment: If the correct way is the first option, we can use this patch to solve that error. I attached diff file. I use Lib/test/test_pprint.py to ensure that's works. -- keywords: +patch nosy: +humitos Added file: http://bugs.python.org/f

[issue2888] pprint produces different output in 2.6 and 3.0

New submission from Alexandre Vassalotti <[EMAIL PROTECTED]>: The indent argument produces different output in Python 2.6 and 3.0: Python 3.0a5+ (py3k:63349:63350M, May 16 2008, 00:37:17) [GCC 4.2.3 (Ubuntu 4.2.3-2ubuntu7)] on linux2 Type "help", "copyright", "credits" or "license" for more in