[issue13744] raw byte strings are described in a confusing way

2013-10-13 Thread Georg Brandl
Georg Brandl added the comment: 3.3 is now released with both "br" and "rb" allowed, and in 2.7 the current text looks good enough for me. -- nosy: +georg.brandl resolution: -> out of date status: open -> closed ___ Python tracker

[issue13744] raw byte strings are described in a confusing way

2012-03-29 Thread Éric Araujo
Éric Araujo added the comment: Actually it’s fine, we already have the text in your message :) -- ___ Python tracker ___ ___ Python-b

[issue13744] raw byte strings are described in a confusing way

2012-03-29 Thread Éric Araujo
Éric Araujo added the comment: Thanks for the contribution. Could you post your suggested wording as a plain text file? -- nosy: +eric.araujo ___ Python tracker ___ __

[issue13744] raw byte strings are described in a confusing way

2012-03-29 Thread Martin v . Löwis
Changes by Martin v. Löwis : Removed file: http://bugs.python.org/file25064/stringByteLiteralBR.docx ___ Python tracker ___ ___ Python-bugs-li

[issue13744] raw byte strings are described in a confusing way

2012-03-29 Thread Joseph Chadwick
Joseph Chadwick added the comment: I uploaded before making the final save, so the first document is incomplete. (that's embarrassing) -- Added file: http://bugs.python.org/file25065/stringByteLiteralBR.docx ___ Python tracker

[issue13744] raw byte strings are described in a confusing way

2012-03-29 Thread Joseph Chadwick
Joseph Chadwick added the comment: The attached replaces the text for the documentation in 2.4.1 between the lexical definitions table and the escape sequence table. The only change is the following addition to the paragraph on string and byte literals prefixed by 'r' or 'R': When a byte lit

[issue13744] raw byte strings are described in a confusing way

2012-01-13 Thread Terry J. Reedy
Changes by Terry J. Reedy : -- nosy: +terry.reedy versions: -Python 3.1 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsu

[issue13744] raw byte strings are described in a confusing way

2012-01-09 Thread Barry A. Warsaw
Barry A. Warsaw added the comment: On Jan 09, 2012, at 03:35 PM, Antoine Pitrou wrote: > >Antoine Pitrou added the comment: > >> The $64k question: is this a new feature or a bug? :) > >Most certainly a feature... In that case, since we can only add the new prefixes to 3.3, I still think we n

[issue13744] raw byte strings are described in a confusing way

2012-01-09 Thread Antoine Pitrou
Antoine Pitrou added the comment: > The $64k question: is this a new feature or a bug? :) Most certainly a feature... -- ___ Python tracker ___

[issue13744] raw byte strings are described in a confusing way

2012-01-09 Thread Barry A. Warsaw
Barry A. Warsaw added the comment: On Jan 09, 2012, at 03:15 PM, Antoine Pitrou wrote: > >Antoine Pitrou added the comment: > >> Either Python should accept both spellings > >+1. Been annoyed several times by this. The $64k question: is this a new feature or a bug? :) -- ___

[issue13744] raw byte strings are described in a confusing way

2012-01-09 Thread Antoine Pitrou
Antoine Pitrou added the comment: > Either Python should accept both spellings +1. Been annoyed several times by this. -- nosy: +gvanrossum, pitrou ___ Python tracker ___ _

[issue13744] raw byte strings are described in a confusing way

2012-01-09 Thread Barry A. Warsaw
New submission from Barry A. Warsaw : The lexical analysis documentation says this: http://docs.python.org/py3k/reference/lexical_analysis.html?highlight=raw%20bytes "Bytes literals are always prefixed with 'b' or 'B';..." "Both string and bytes literals may optionally be prefixed with a lette