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
On 10/06/2019 22:20, Avi Chein wrote:
> I'm trying to install Python 3.6 on my MacOS Mojave but it isn't installing
> properly.
When asking for help, on any forum, it's never a good idea to say that
something "doesn't work" or "isn't installing properly". That gives us
nothing to work on. What e
Hi,
I'm trying to install Python 3.6 on my MacOS Mojave but it isn't installing
properly. Can someone help me out? I'm a college student and have never
used Python before. Would be much appreciated!
Thans,
Avi
___
Tutor maillist - Tutor@python.org
To
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 when I removed that "#! usr/bin/python
But then how come it was working earlier for me without that import statement.
Python doesn't interpret it as a statement exclusively, before it worked fine
as a function.
Best Wishes,
Sai Allu
From: Mats Wichmann
Sent: Monday, June 10, 2019 11:12 AM
To: Sai All
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
