[issue20335] bytes constructor accepts more than one argument even if the first one is not a string

2014-01-21 Thread Renaud Blanch
Changes by Renaud Blanch : -- title: bytes constructor accepts more than one argument even of the first one is not a string -> bytes constructor accepts more than one argument even if the first one is not a string ___ Python tracker &l

[issue20335] bytes constructor accepts more than one argument even of the first one is not a string

2014-01-21 Thread Renaud Blanch
Changes by Renaud Blanch : -- keywords: +patch Added file: http://bugs.python.org/file33600/bytesobject.patch ___ Python tracker <http://bugs.python.org/issue20

[issue20335] bytes constructor accepts more than one argument even of the first one is not a string

2014-01-21 Thread Renaud Blanch
New submission from Renaud Blanch: % python3 Python 3.3.2 (v3.3.2:d047928ae3f6, May 13 2013, 13:52:24) [GCC 4.2.1 (Apple Inc. build 5666) (dot 3)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> help(bytes)

[issue11682] PEP 380 reference implementation for 3.3

2011-07-11 Thread Renaud Blanch
Renaud Blanch added the comment: I can not comment on http://bugs.python.org/review/11682/, so a quick comment here: Doc/whatsnew/3.3.rst patch gives me credit together with Greg Ewing for the implementation, but I've only upgraded his patches to 3.3. So, the following line: +(Implement

[issue12471] wrong TypeError message on '%i' formatting

2011-07-04 Thread Renaud Blanch
Renaud Blanch added the comment: that was quick! just a question: is it worth backporting the fix to 2.7? if this helps, here is a backport for the patch commited to 3.2 <http://hg.python.org/cpython/rev/97707459bb5a> -- Added file: http://bugs.python.org/fil

[issue12471] wrong TypeError message on '%i' formatting

2011-07-01 Thread Renaud Blanch
New submission from Renaud Blanch : The TypeError message is erroneous when attempting to format a non number object with a '%i' string (notice the '%d' in the error message): >>> '%i' % 's' Traceback (most recent call last):

[issue11682] PEP 380 reference implementation for 3.3

2011-06-30 Thread Renaud Blanch
Renaud Blanch added the comment: I've just updated the pep380-test patch to make it slightly simpler (still in golden output form though) https://bitbucket.org/rndblnch/cpython-pep380/src/317eadf5e3e8/pep380-tests -- ___ Python tracker

[issue11682] PEP 380 reference implementation for 3.3

2011-05-01 Thread Renaud Blanch
Renaud Blanch added the comment: As nick said, the repo only host a patch queue. the patch itself is visible here: https://bitbucket.org/rndblnch/cpython-pep380/qseries?apply=t&qs_apply=pep380 Or it can be download here in raw text: https://bitbucket.org/rndblnch/cpython-pep380/raw/tip/pe

[issue11682] PEP 380 reference implementation for 3.3

2011-03-30 Thread Renaud Blanch
Changes by Renaud Blanch : -- nosy: +rndblnch ___ Python tracker <http://bugs.python.org/issue11682> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue1672568] silent error in email.message.Message.get_payload

2009-05-13 Thread Renaud Blanch
Renaud Blanch added the comment: looks very good to me. thanks daniel for your work renaud -- ___ Python tracker <http://bugs.python.org/issue1672568> ___ ___

[issue1672568] silent error in email.message.Message.get_payload

2009-04-06 Thread Renaud Blanch
Renaud Blanch added the comment: good idea, why not something like sketched in the attached patch? it does not break any existing code, while providing a way for new users to have a chance to get the decoding errors. of course, the doc should be updated accordingly, and tests should be added

[issue1672568] silent error in email.message.Message.get_payload

2009-04-03 Thread Renaud Blanch
Renaud Blanch added the comment: Daniel: i can't remember the exact scenario (i filled this bug 2 years ago !) after having a look back at email.message.Message.get_payload, i remember the problem: the decoding errors are silented by the method and you have no way to know if the decodin