I am new to Ubuntu... I am trying to run my first simple python program "Hello World" ... After running following commands in terminal
1. chmod +x filename.py
2. ./filename.py
terminal is showing following error "bash: ./filename.py: Permission denied"
what can I do for solve about problem?
Do you have the appropriate incantation at the top of your python file? e.g.,
#!/usr/bin/python (or alternatively #!/usr/bin/env python)
Just to clarify, chmod +x only makes a file executable, it doesn't run it.
And I'm assuming your script looks like nothing more complex than this:
#!/usr/bin/env python
print 'hello world'
#!/usr/bin/env python. And OP does say that exactly that way of running it is what gives the error.
ls -l filename.py command so we can see the file permissions?Some possibilities:
What does it say if you type umask? chmod +x will only make a file executable for you if your umask doesn't block the user executable bit. A typical umask such as 0022 will not block the user execute bit, but a umask like 0122 can. (See the Description section of chmod(1) for more info.)
To execute a script such as a Python script, you also need read permission. Try chmod u+rx filename.py and execute the script again.
It's also remotely possible that whatever interpreter you've specified in the file with the "hashbang" line at the beginning of your file (e.g. #!/usr/bin/env python) isn't executable, although that in my experience yields a different error message.
chmod -x will remove execute permission from user, group, and other, but again only if the umask doesn't include those execute bits—see the chmod manual page at linux.die.net/man/1/chmod for more info. chmod u+rx will set the user read and execute bits regardless of umask.I deal with the same problem on my new system.
It is the third time I tried to solve this, and your post is the first one appearing on google results. My post is late, but think that it will help another users with the same problem.
In my case, it was about partition table setup.
Check in your /etc/mtab file how python script is being stored. Check if there is a clause: noexec
noexec is a flag that forbid executing under the partition. By default, it is set with exec. But, sometimes, this kind of things happen.
Now, it is working fine here.
ls -l filename.pyand post what it says .. I'm curious about the file permission (thoughchmod +x filename.pywould be the right way to make the file executable).#!/usr/bin/env pythonin the first line of your script?#!/usr/bin/env pythonvs#!/usr/bin/pythonI was severely admonished by some person on SO for using the former (which all of my own scripts still do) because presumably you could not be sure which Python would execute in case you had more than one installed, so the idea was to always specify the full path for the one you wanted). Maybe I should make this a question and post it on SO./usr/bin/envis fine. It is simply a way to say "use what you find on myPATH" which is perfectly fine if yourPATHis constructed sanely. I would say it is preferred if you're going to distribute your scripts, because then they will be able to use the end-user'sPATH. But if you have a need to explicitly use one specific Python binary, then yes, by all means, specify that.