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 martin.panter
Recipients LawfulEvil, martin.panter, serhiy.storchaka, xiang.zhang
Date 2017-04-28.00:50:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1493340614.64.0.330493492007.issue30103@psf.upfronthosting.co.za>
In-reply-to
Content
FWIW I am using NXP LPC microcontrollers at the moment, whose bootloader uses the grave/backtick instead of spaces. (NXP application note AN11229.)  Although in practice it does seem to accept Python's spaces instead of graves.

I wouldn't put too much weight to Wikipedia, especially where it says graves are not used for encoded data (vs length and padding). Earlier versions of Wikipedia did mention graves in regular data.

I understand the reason for avoiding spaces is to due to spaces being stripped (e.g. by email, copy and paste, etc). You have to avoid spaces in data, not just padding, because a data space may still appear at the end of a line.
History
Date User Action Args
2017-04-28 00:50:14martin.pantersetrecipients: + martin.panter, serhiy.storchaka, xiang.zhang, LawfulEvil
2017-04-28 00:50:14martin.pantersetmessageid: <1493340614.64.0.330493492007.issue30103@psf.upfronthosting.co.za>
2017-04-28 00:50:14martin.panterlinkissue30103 messages
2017-04-28 00:50:13martin.pantercreate