Path: csiph.com!usenet.pasdenom.info!aioe.org!newsfeed1.swip.net!newsfeed2.funet.fi!newsfeeds.funet.fi!news.cc.tut.fi!not-for-mail From: Anssi Saari Newsgroups: comp.lang.python Subject: Re: Shebang line on Windows? Date: Tue, 26 Feb 2013 16:30:44 +0200 Lines: 12 Message-ID: References: <512B63BC.6090600@davea.name> NNTP-Posting-Host: 2001:708:310:3430:dc0d:6429:26a3:43ac Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: news.cc.tut.fi 1361889044 14777 2001:708:310:3430:dc0d:6429:26a3:43ac (26 Feb 2013 14:30:44 GMT) X-Complaints-To: abuse@tut.fi NNTP-Posting-Date: Tue, 26 Feb 2013 14:30:44 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux) Cancel-Lock: sha1:jBEMJP/ST3gPUEHtiqEcZpQKahM= Xref: csiph.com comp.lang.python:39953 Michael Torrie writes: > Actually, the shell isn't involved in parsing the shebang line at all. > That's actually done in the kernel by the program loader. So it's the > kernel that has a problem with it; wonder if Linus would accept a patch > to ignore the tailing CR? Worth a try in my opinion. There's some historical information about the shebang at http://www.in-ulm.de/~mascheck/various/shebang/ There's a table which says Linux since 2.4.0 removes trailing whitespace from the shebang line. I guess Linux doesn't count CR as whitespace in this context.