Subject: bug#12409: 24.2.50; OS X Python completion leaks junk to inferior-python-mode buffer

From: Fabián Ezequiel Gallina <[email-masked]>
Date: Mon, 08 Oct 2012 18:57:28 -0300

On 10/08/2012 04:49 PM, Jan Djärv wrote:
> Hello.
>
> Python does not write them, using dtruss i see:
>
> write_nocancel(0x1, "'aaaa;aaaaaa'\n\0", 0xE)		
>
> No \r in sight.
>
> 	Jan D.
>
> 8 okt 2012 kl. 21:07 skrev Stefan Monnier <[email-masked]>:
>
>>> (format "\r?\n\\(?:%s\\|%s\\|%s\\)$" works.  It is a bad idea to use literal
>>> ^M in files, so take Andreas advice and use \r.
>> BTW, could someone investigate into the cause of these ^M?
>> IOW, we need to look at the actual bytes that Python sends to Emacs,
>> then figure out why Emacs's EOL-conversion doesn't handle them (are
>> the bytes wrong, or is the process's coding-system set incorrectly?).
>>
>>
>>         Stefan

I just pushed that small fix in 110473. I think for future discussion 
the extra \r on OSX might have earned his own ticket. If everyone agrees 
we can close this one.