: bad interpreter: No such file or directory in python [closed]

Answer 1

Probably you have \r\n line endings, where \r is carriage return and \n is newline

That means that the first line might be like this

#!/usr/bin/env python\r\n

or

#!/usr/bin/python\r\n

so the shell is trying to run the command python\r

Answer 2

You're probably using the #!python hashbang convention that's inexplicably popular among Windows users. Linux expects a full path there. Use either #!/usr/bin/python or (preferably) #!/usr/bin/env python instead.