From: Cameron Simpson
Sent: Monday, June 10, 2019 5:34 PM
To: Sai Allu
Cc: Mats Wichmann; tutor@python.org; Deepak Dixit
Subject: Re: [Tutor] Python printing parentheses and quotes
On 10Jun2019 19:04, Sai Allu wrote:
>Actually I'm pretty sure what happened was that the "#! usr/bin/python&
On 10Jun2019 19:04, Sai Allu wrote:
Actually I'm pretty sure what happened was that the "#! usr/bin/python" was in
a module that was being imported. So the Python interpreter cached it or somehow crashed
randomly, which meant that the print was working as a keyword instead of a function.
But
Sent: Monday, June 10, 2019 11:12 AM
To: Sai Allu; tutor@python.org
Subject: Re: [Tutor] Python printing parentheses and quotes
On 6/10/19 10:50 AM, Sai Allu wrote:
> Hello!
>
> I was just wondering if anybody encountered an issue where the Python
> interpreter was changing how it
: Sai Allu; tutor@python.org
Subject: Re: [Tutor] Python printing parentheses and quotes
On 6/10/19 10:50 AM, Sai Allu wrote:
> Hello!
>
> I was just wondering if anybody encountered an issue where the Python
> interpreter was changing how it interprets print statements. So I'm usin
On 10/06/2019 17:50, Sai Allu wrote:
> Basically what happened was that I had a few lines in the script like this
> ip = "10.41.17.237"
> print(" Welcome to Squid Monitoring for ", ip)
> print("")
>
> and the output was like this
>
> (" Welcome to Squid Monitoring for 10.41.17.
On 6/10/19 10:50 AM, Sai Allu wrote:
> Hello!
>
> I was just wondering if anybody encountered an issue where the Python
> interpreter was changing how it interprets print statements. So I'm using
> default Python on Mac OSX (2.7.10 I'm pretty sure) and running with the
> "python script.py" comm
Hello!
I was just wondering if anybody encountered an issue where the Python
interpreter was changing how it interprets print statements. So I'm using
default Python on Mac OSX (2.7.10 I'm pretty sure) and running with the "python
script.py" command.
Basically what happened was that I had a fe
