First, let me offer congratulations and heartfelt thanks for your hard
work!
Victor Stinner writes:
> For network protocols, I don't know. It looks like the new email
> modules will offer two API levels: low level (native type) using
> bytes, high level using str (unicode). I don't know if the
Le jeudi 21 octobre 2010 21:14:55, Toshio Kuratomi a écrit :
> > That's exactly what I was looking for! Thanks. I think you've learned a
> > huge amount of good information that's difficult to find, so writing it
> > up in a more permanent and easy to find location will really help future
> > Pyt
On Thu, Oct 21, 2010 at 12:00:40PM -0400, Barry Warsaw wrote:
> On Oct 20, 2010, at 02:11 AM, Victor Stinner wrote:
>
> >I plan to fix Python documentation: specify the encoding used to decode all
> >byte string arguments of the C API. I already wrote a draft patch: issue
> >#9738. This lack of
On Oct 20, 2010, at 02:11 AM, Victor Stinner wrote:
>I plan to fix Python documentation: specify the encoding used to decode all
>byte string arguments of the C API. I already wrote a draft patch: issue
>#9738. This lack of documentation was a big problem for me, because I had to
>follow the fu
Le mardi 19 octobre 2010 16:12:56, Barry Warsaw a écrit :
> Going forward, is there adequate documentation, guidelines, and safeguards
> for future coders so that they Do The Right Thing with new code? Perhaps
> a short How To in the standard documentation would be helpful, with links
> to it from
Am 19.10.2010 16:12, schrieb Barry Warsaw:
> On Oct 19, 2010, at 03:53 AM, Victor Stinner wrote:
>
>>Seven months after my first commit related to this issue, the full test suite
>>of Python 3.2 pass with ASCII, ISO-8859-1 and UTF-8 locale encodings in a non-
>>ascii source directory. It means th
On Oct 19, 2010, at 03:53 AM, Victor Stinner wrote:
>Seven months after my first commit related to this issue, the full test suite
>of Python 3.2 pass with ASCII, ISO-8859-1 and UTF-8 locale encodings in a non-
>ascii source directory. It means that Python 3.2 now process correctly
>filenames in
On Tue, Oct 19, 2010 at 11:53 AM, Victor Stinner
wrote:
> Hi,
>
> Seven months after my first commit related to this issue, the full test suite
> of Python 3.2 pass with ASCII, ISO-8859-1 and UTF-8 locale encodings in a non-
> ascii source directory. It means that Python 3.2 now process correctly
Victor Stinner wrote:
> Hi,
>
> Seven months after my first commit related to this issue, the full test suite
> of Python 3.2 pass with ASCII, ISO-8859-1 and UTF-8 locale encodings in a non-
> ascii source directory. It means that Python 3.2 now process correctly
> filenames in all modules, buil
On 19 October 2010 05:52, Éric Araujo wrote:
> Congratulations Victor! This is not a small feat. The PSU should send
> you cookies to thank you, but they won’t since they don’t exist and
What? Cookies don't exist???
Paul.
___
Python-Dev mailing list
Congratulations Victor! This is not a small feat. The PSU should send
you cookies to thank you, but they won’t since they don’t exist and
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
On 10/18/2010 08:53 PM, Victor Stinner wrote:
Hi,
Seven months after my first commit related to this issue, the full test suite
of Python 3.2 pass with ASCII, ISO-8859-1 and UTF-8 locale encodings in a non-
ascii source directory. It means that Python 3.2 now process correctly
filenames in all
Hi,
Seven months after my first commit related to this issue, the full test suite
of Python 3.2 pass with ASCII, ISO-8859-1 and UTF-8 locale encodings in a non-
ascii source directory. It means that Python 3.2 now process correctly
filenames in all modules, build scripts and other utilities, wit
13 matches
Mail list logo
