On Aug 10, 2012, at 12:20 AM, Steven D'Aprano wrote:
>
[byte]
> That is not Python's doing. That is the shell, and so it depends
> entirely on your choice of operating system and shell. It works on Unix,
> Linux and probably Mac OS, but not on Windows.
>
Yes, it definitely does work on Mac O
On 10/08/12 15:35, Modulok wrote:
...
My Question:
Is it true that doing that is as same as doing #!/usr/bin/env python
on Unix? Because I think that the matter of shebang is limited to Bash
and Windows don't have a bash, it has a Command Prompt. And I don't
think such thing happens in Windows.
On 08/10/2012 12:01 AM, Santosh Kumar wrote:
> Hello There,
>
> We all know that line starting with "#" in Python is a comment.
>
> We also know that when the first line of any file (with any extension)
> has "#!/usr/bin/env bash" and if you make it executable and do
> ./filename.ext in the termina
...
> My Question:
> Is it true that doing that is as same as doing #!/usr/bin/env python
> on Unix? Because I think that the matter of shebang is limited to Bash
> and Windows don't have a bash, it has a Command Prompt. And I don't
> think such thing happens in Windows.
It has nothing directly do
On 10/08/12 14:01, Santosh Kumar wrote:
Hello There,
We all know that line starting with "#" in Python is a comment.
We also know that when the first line of any file (with any extension)
has "#!/usr/bin/env bash" and if you make it executable and do
./filename.ext in the terminal then it will
Hello There,
We all know that line starting with "#" in Python is a comment.
We also know that when the first line of any file (with any extension)
has "#!/usr/bin/env bash" and if you make it executable and do
./filename.ext in the terminal then it will be considered as bash file
(in this case e
