On Sep 2, 2:47 pm, Chris Angelico <ros...@gmail.com> wrote: > On Mon, Sep 3, 2012 at 7:18 AM, gwhite <gwh...@ti.com> wrote: > > Thanks again, Terry. There is a lot to the language, I am finding > > out. I am a HW engineer, not really a programmer. Python seems a lot > > more sophisticated than MATLAB. > > > I'm kinda thinking `write` is likely to be a little more "stable" than > > `print` (if that is the right characterization) when my eventual > > switch from 2.7 to 3.x happens. You think? > > If you're planning to switch, make use of __future__. It's > specifically to make that job easier. Once you have a future > declaration at the top, print() will be stable across 2.7 and 3.x.
I guess you're saying 3.x will just ignore: from __future__ import print_function I'll risk being silly, and thus ask: but what if when I get to 3.x there is no __future__, as it is now "present?" Do I need to strip out the line? What would happen when I finally started running 3.3, and a new __future__ was made that broke the old syntax? Do I need to strip out the line? I'm probably over thinking it. I don't know what I am doing. lol! -- http://mail.python.org/mailman/listinfo/python-list
