Run a python script and the #!/usr/bin/python line

[pascor]

I'm coming from the MSW development world and a few things in linux/ubuntu for "getting things done" have got me stumped.

If I have my python app in "/usr/local/pyscripts" named "myapp.py", how can I set up things so that I can run it from anywhere on the command line by simply giving the command "myapp arg1 arg2 arg3" ? (I can write bash scripts and set aliases if necessary.)

What (good) is the shebang line for in Python scripts ? What part of the OS uses it ?

TIA :-)

[numberwhun]

If you would like to know the reasoning behind why dot is a bad thing to have in the PATH variable, then read this.

As per the article, if you do decide to add it to your path, only add it at the end and not the beginning of the PATH variable. You could simply put this in your .bashrc and open another window:

PATH = $PATH:.
 

But know that myself and probably most other unix people here are just fine with putting the ./ before our scripts. We don't find it to be an issue because:

#1. We know the security risks behind it and
#2. Most importantly, this isn't a Windows system. Windows is insecure (IMHO) because of its lax nature of how it does things. You aren't going to make this Windows and are just going to have to deal with the nuances of it. They are there for a reason.

Regards,

Jeff

[pascor]

Security (and the lack there of) and the OS getting programs in PATH mixed up generally have nothing to do with each other.

This forum isn't the place to flame Windows security issues. There are plenty of other places to do that.

[numberwhun]

Believe me, I wasn't flaming Windows, I was pointing out what, in my opinion, is a fact. You made the comparison to Windows in post #5 above, I just added an observation to it.

Further to that, we definitely need to get the point across that searching the current directory first is extremely insecure and should not be done. Personally I would stick to using the ./ in front o things, and always do, versus adding the current directory to my path. Don't learn that lesson the hard way, it can wreak havoc.

[Mariostg]

Really pascor how much time did you spent researching about your problem? Did you even bother looking at the links that were provided to you? I sincerely believe all replies provided to your queries are fair. There are several exemples on the internet about the nasty things that could happen if you set your current directory in the path. As @Numberwhun
said, if you want it in your path, put it last. It is a wise advise.

[pascor]

The security issues amount to just 2 potential problems:

1 - If a user is stupid enough to name a program the same as an already existing program or script name. This implies the user is only slightly smarter than a head of cabbage and doesn't first use the [ which ] utility to avoid name duplications.

2 - If the system is hacked. This implies that the OS is inherently unsafe, anyway, and much more anti-malware protection is needed.

Since I'm not a professional developer, I think the risks are minimal.

[numberwhun]

They would not have the security warnings against something if it wasn't a concern. You would think that people wouldn't do it, but it happens. Heck, people alias things all the time and get themselves in trouble without even knowing it. Users are the inherent threat that all sys admins guard against, its just the way things go. Doesn't matter the OS, the user is the reason for rules most of the time.

I am not going to go any further with this. You have been given the articles to read on the security risks and the system you are working on is yours. If you take the risk then you have nobody to blame but yourself if something goes wrong. We can only give you advice.

Regards,

Jeff