Author mdartiailh
Recipients docs@python, mdartiailh
Date 2017-06-07.15:02:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1496847775.57.0.842403144977.issue30588@psf.upfronthosting.co.za>
In-reply-to
Content
codecs.escape_decode does not appear in the codecs documentation. This function is to my knowledge the only convenient way to process the escaped characters in a literal string (actually found here https://stackoverflow.com/questions/4020539/process-escape-sequences-in-a-string-in-python). It is most useful when implementing a parser for a language extending python semantic while retaining python processing of string (cf https://github.com/MatthieuDartiailh/enaml).

Is there a reason for that function not being documented ?
History
Date User Action Args
2017-06-07 15:02:55mdartiailhsetrecipients: + mdartiailh, docs@python
2017-06-07 15:02:55mdartiailhsetmessageid: <1496847775.57.0.842403144977.issue30588@psf.upfronthosting.co.za>
2017-06-07 15:02:55mdartiailhlinkissue30588 messages
2017-06-07 15:02:55mdartiailhcreate