Message 115355 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	benjamin.peterson
Recipients	BreamoreBoy, benjamin.peterson, djc, stutzbach
Date	2010-09-02.01:37:23
SpamBayes Score	4.0145104e-10
Marked as misclassified	No
Message-id	<AANLkTim5Pd868bfvoSFg+ec+PU3i879-fyWLg9TQV+qK@mail.gmail.com>
In-reply-to	<1283391335.45.0.235954812557.issue7141@psf.upfronthosting.co.za>

Content
2010/9/1 Daniel Stutzbach <report@bugs.python.org>: > > Daniel Stutzbach <daniel@stutzbachenterprises.com> added the comment: > > Excluding the future fixer would only get me half of the way there. I would still need to add "from __future__ import print_statement" to all of my scripts if I want them to continue to work under 2.6. I'm still apprehensive because it's not really the point of 2to3 to port apps to 2.6.

2010/9/1 Daniel Stutzbach <report@bugs.python.org>:
>
> Daniel Stutzbach <daniel@stutzbachenterprises.com> added the comment:
>
> Excluding the future fixer would only get me half of the way there.  I would still need to add "from __future__ import print_statement" to all of my scripts if I want them to continue to work under 2.6.

I'm still apprehensive because it's not really the point of 2to3 to
port apps to 2.6.

History
Date	User	Action	Args
2010-09-02 01:37:25	benjamin.peterson	set	recipients: + benjamin.peterson, stutzbach, djc, BreamoreBoy
2010-09-02 01:37:24	benjamin.peterson	link	issue7141 messages
2010-09-02 01:37:23	benjamin.peterson	create