On approximately 11/5/2008 11:47 PM, came the following characters from
the keyboard of Stephen J. Turnbull:
Glenn Linderman writes:
> But the API could speak Unicode, and do the appropriate translations.
> Or in some cases, inappropriate translations.
You've written that kind of thing thre
Glenn Linderman writes:
> But the API could speak Unicode, and do the appropriate translations.
> Or in some cases, inappropriate translations.
You've written that kind of thing three or four times by now. As far
as I can see, you just don't care about any requirements beyond your
own.
> Pl
On approximately 11/5/2008 6:09 PM, came the following characters from
the keyboard of Stephen J. Turnbull:
Glenn Linderman writes:
> On approximately 11/5/2008 2:59 PM, came the following characters from
> the keyboard of Andrew McNamara:
> >> I would find
> >>
> >> message[b'Subject'] =
On approximately 11/5/2008 4:24 PM, came the following characters from
the keyboard of Andrew McNamara:
But I'm not at all clear on what you mean by a round-trip through the
email module. Let me see... if you are creating an email, you (1)
should encode it properly (2) a round-trip is mostly me
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
There appears to be a bug in the documentation for 3.0. See issue 4266.
http://bugs.python.org/issue4266
I'm sorry that I'm too tired to figure out what the basic problem is.
I've made the issue a release blocker (the only one left for 3.0rc2),
Glenn Linderman writes:
> On approximately 11/5/2008 2:59 PM, came the following characters from
> the keyboard of Andrew McNamara:
> >> I would find
> >>
> >> message[b'Subject'] = b'Hello'
> >>
> >> to be totally gross.
Indeed.
> >> Depending on the level of email interface, there sh
>But I'm not at all clear on what you mean by a round-trip through the
>email module. Let me see... if you are creating an email, you (1)
>should encode it properly (2) a round-trip is mostly meaningless, unless
>you send it to yourself. So you probably mean email that is received,
>and that
On approximately 11/5/2008 2:59 PM, came the following characters from
the keyboard of Andrew McNamara:
I would find
message[b'Subject'] = b'Hello'
to be totally gross.
While RFC Email is all ASCII, except if 8bit transfer is legal, there
are internal encoding provided that permit the
>I would find
>
> message[b'Subject'] = b'Hello'
>
>to be totally gross.
>
>While RFC Email is all ASCII, except if 8bit transfer is legal, there
>are internal encoding provided that permit the expression of Unicode in
>nearly any component of the email, except for header identifiers. But
On approximately 11/5/2008 12:38 PM, came the following characters from
the keyboard of Barry Warsaw:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Oct 30, 2008, at 6:17 PM, Andrew McNamara wrote:
That's a tricker case, but I think it should use bytes internally. One of
the early goals of e
Done -- I'm fine with this particular API change.
On Wed, Nov 5, 2008 at 12:02 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Guido,
>
> Can you please make a BDFL pronouncement on issue 4211, specifically the
> backward compatibility and API brea
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Oct 30, 2008, at 6:17 PM, Andrew McNamara wrote:
That's a tricker case, but I think it should use bytes internally.
One of
the early goals of email was that be able to cope with malformed
MIME -
this includes incorrectly encoded messages. So
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Guido,
Can you please make a BDFL pronouncement on issue 4211, specifically
the backward compatibility and API break for __path__ this late in the
game:
http://bugs.python.org/issue4211
If you can decide in the next 3 hours we can get the patc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 5, 2008, at 7:20 AM, Victor Stinner wrote:
That's why we are all waiting on barry for python 3.0rc2 :-)
T minus 8h10m and counting...
- -B
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSRGyvXEjvBPtnXfVAQKHywP/TRRnd
Le Monday 03 November 2008 12:12:57 [EMAIL PROTECTED], vous avez écrit :
> in run.py in Python_30\Lib\idlelib
> the line:sockthread.set_daemon(True)
> has to be changed to:sockthread.setDaemon(True)
It's already fixed in python trunk:
http://svn.python.org/view?rev=6
in run.py in Python_30\Lib\idlelib
the line:sockthread.set_daemon(True)
has to be changed to:sockthread.setDaemon(True)
the message was:
D:\Python_30\Lib\idlelib>python idle.py
Traceback (most recent call last):
File "", line 1, in
File "D:\Python_30\lib\idlelib\
2008/11/5 Arnaud Delobelle wrote:
> (or one could use given=dict(lst=lst, d=d))
>
> This would have two advantages:
>
> * eliminate the rist of keyword argument name collision
> * one could put all the 'given' objects in a dictionary and then
> 'pickle' expressions as needed using this method. Lat
17 matches
Mail list logo
