On Sep 6, 10:01 am, Timothy Madden wrote:
> Hello
>
> Sorry if this has been discussed before, my search did not find it.
> My questions is if I should use
> #!/usr/bin/env python
> as the shebang line in a portable and open python script and if it does
> help with portability and usage.
Note
Ned Deily wrote:
In article <4aa3bfdf$0$282$14726...@news.sunsite.dk>,
Timothy Madden wrote:
My questions is if I should use
#!/usr/bin/env python
as the shebang line in a portable and open python script and if it does
help with portability and usage.
This question came up recently on st
In article <4aa3bfdf$0$282$14726...@news.sunsite.dk>,
Timothy Madden wrote:
> My questions is if I should use
>#!/usr/bin/env python
> as the shebang line in a portable and open python script and if it does
> help with portability and usage.
This question came up recently on stackoverflow (
On Sun, Sep 6, 2009 at 10:01 AM, Timothy Madden wrote:
> Hello
>
> Sorry if this has been discussed before, my search did not find it.
> My questions is if I should use
> #!/usr/bin/env python
> as the shebang line in a portable and open python script and if it does help
> with portability and usa
Hello
Sorry if this has been discussed before, my search did not find it.
My questions is if I should use
#!/usr/bin/env python
as the shebang line in a portable and open python script and if it does
help with portability and usage.
First, can one not find /usr/bin/python in any standard sys
