On Tue, 7 Sep 2010 06:02:39 am ALAN GAULD wrote:
> I wonder if we could create a module that would make v2.7 simulate v3
> to a close degree? hmm... And is it sensible to try, should we not
> perhaps just accept the difference?
from __future__ import print_function, unicode_literals
from future_bu
>Other than changing the input() to raw_input() for Python 2 compatibility,
>
>
> And of course you can do that using
>
> input = raw_input
>
>
> > the following statement could be added to the beginning of the program
> > to allow your Python 2 program to use the Python 3 style print function.
>
>
> > I think there is a trick in V2.7 to make it act more like v3 but someone
> > else will need to tell you what it is... :-)
>Other than changing the input() to raw_input() for Python 2 compatibility,
And of course you can do that using
input = raw_input
> the following statement could be a
>
>
> Python 2.7 (r27:82525, Jul 4 2010, 09:01:59) [MSC v.1500 32 bit (Intel)]
>> on win32 Type
>> "copyright", "credits" or "license()" for more information.
>>
>>> RESTART
>
What is your name? Keith
>>
>
> I think there
"Keith Lucas" wrote
What is wrong with the following, apparently almost straight out of
Python Programming
by Michael Dawson?
You are using Python v2, the tutorial seems to be written for v3.
There are big diffeernces in syntax between them, v3 is NOT
backwards compatible with v2.
# Get
