"/usr/bin/python^M: bad interpreter"

Question

Cannot figure out, where to change EOF in PyCharm. My scripts start with :

#!/usr/bin/python
# -*- coding: utf-8 -*-

It outputs something like this when I try to run it like an executable (chmode +x) :

-bash: ./main.py: /usr/bin/python^M: bad interpreter: No such file or directory

there seems to be `^M` characters in the script, use dos2unix — avasal, Apr 02 '12 at 10:50
It seems like the original file was created in MSDOS/Windows without UNIX/Linux end of line support. So when you tried to run this file on UNIX/Linux, you got an error. The easiest way is to recreate the file on UNIX/Linux. The scalable way is to configure the MSDOS/Windows shell to support saving with UNIX/Linux end of lines. It's help you to create and reuse files on both systems. — dzNET, Jun 29 '18 at 23:25

score 55 · Answer 1 · answered Apr 02 '12 at 10:51

55

The issue is not EOF but EOL. The shell sees a ^M as well as the end of line and thus tries to find /usr/bin/python^M .

The usual way of getting into this state is to edit the python file with a MSDOS/Windows editor and then run on Unix. The simplest fix is to run dos2unix on the file or edit the file in an editor that explicitly allows saving with Unix end of lines.

answered Apr 02 '12 at 10:51

mmmmmm

32,227
27
88
117

I think the python interpreter is not ran at all. The shebang interpreter fails on ^M. – jpic Apr 02 '12 at 10:53
Yes sorry the shell is see ingthis – mmmmmm Apr 02 '12 at 10:53
3

If you don't have dos2unix, simply execute `sudo apt-get install dos2unix`, in Ubuntu 14.04. – gsamaras Jan 30 '16 at 20:01

score 37 · Accepted Answer · answered Apr 02 '12 at 11:13

37

Set line separator to Unix:

Unix

answered Apr 02 '12 at 11:13

CrazyCoder

389,263
172
990
904

3

If the file has already been saved, this doesn't seem help. Probably only with new files? You'll need to use the `dos2unix` tool for those files. – ksaylor11 Aug 02 '16 at 20:59

score 32 · Answer 3 · edited May 23 '17 at 10:31

32

You may find the answers here: ./configure : /bin/sh^M : bad interpreter

As a Mac OS X user, I didn't find the command dos2unix. Alternatively, I use vi/vim: :set fileformat=unix and then save the file :wq

edited May 23 '17 at 10:31

Community

1
1

answered Sep 03 '13 at 21:18

Jiangwei Yu

609
7
7

score 25 · Answer 4 · answered Sep 01 '14 at 20:29

25

If you are using Vim, just enter the following command:

:set fileformat=unix

answered Sep 01 '14 at 20:29

Vitaly Isaev

5,392
6
45
64

score 16 · Answer 5 · answered Apr 02 '12 at 10:52

16

you may want to try dos2unix <filename>

answered Apr 02 '12 at 10:52

gefei

18,922
9
50
67

1

note. Had centos installed without it. to install just sudo yum install dos2unix. it's in the repos. – ThinkBonobo Feb 18 '15 at 22:23

score 10 · Answer 6 · answered Jan 26 '14 at 21:49

10

Install dos2unix: sudo apt-get install dos2unix

and let it do the magic: dos2unix FILENAME

answered Jan 26 '14 at 21:49

vatsa

124
1
9

score 6 · Answer 7 · answered Jul 08 '14 at 07:50

6

For MacOS you can install it via Homebrew like this:

brew install dos2unix

And next do

dos2unix FILENAME

answered Jul 08 '14 at 07:50

FastSolutions

1,809
1
25
49

score 3 · Answer 8 · answered Nov 15 '13 at 14:19

Similar to Jiangwei Yu's post. On UNIX/Linux, I used vi to edit the Python file. Using vi, you can see the ^M at the end of each line.

Find the following line /usr/bin/python^M

Hit end to get to the end of the line

Hit delete to remove the ^M

To save the file and quit, type in: :wq

This worked for me.

score 3 · Answer 9 · answered Sep 04 '15 at 14:42

3

you may try to do this:

sed --in-place 's/^M//g' main.py

[ to type in ^M, press ctrl+v,ctrl+m ]

answered Sep 04 '15 at 14:42

karthiksatyanarayana

109
2
11

score 2 · Answer 10 · answered Nov 05 '13 at 09:28

2

Just a Question of format beween win and unix:

try command: dos2unix fileName

After it run again, it should work

answered Nov 05 '13 at 09:28

vivi

334
2
13

How does this add to or improve on other answers? – mmmmmm Jul 06 '16 at 13:42

"/usr/bin/python^M: bad interpreter"

10 Answers10

Linked

Related