This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author xiang.zhang
Recipients LawfulEvil, serhiy.storchaka, xiang.zhang
Date 2017-04-27.16:57:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1493312246.4.0.402724971722.issue30103@psf.upfronthosting.co.za>
In-reply-to
Content
There seems no standard. I also read the wikipedia but for perl and uuencode on my Linux, they now all use backticks to represent zero instead of spaces.

[~]$ perl -e 'print pack("u","Ca\x00t")'
$0V$`=```
[~]$ cat /tmp/test
Ca[~]$ uuencode /tmp/test -
begin 664 -
"0V$`
`
end

while Python now:

>>> import uu
>>> uu.encode('/tmp/test', '-')
begin 664 test
"0V$ 
 
end

Except the link Kyle gives, the manpage of FreeBSD describes the new algorithm: http://www.unix.com/man-page/freebsd/5/uuencode/

I don't propose to change current behaviour to break backwards compatibility. But I think it's reasonable to provide a way to allow users to use backticks.
History
Date User Action Args
2017-04-27 16:57:26xiang.zhangsetrecipients: + xiang.zhang, serhiy.storchaka, LawfulEvil
2017-04-27 16:57:26xiang.zhangsetmessageid: <1493312246.4.0.402724971722.issue30103@psf.upfronthosting.co.za>
2017-04-27 16:57:26xiang.zhanglinkissue30103 messages
2017-04-27 16:57:26xiang.zhangcreate