On approximately 4/10/2009 9:56 AM, came the following characters from
the keyboard of Barry Warsaw:
On Apr 10, 2009, at 1:19 AM, gl...@divmod.com wrote:
On 02:38 am, ba...@python.org wrote:
So, what I'm really asking is this. Let's say you agree that there
are use cases for accessing a
On approximately 4/16/2009 6:02 AM, came the following characters from
the keyboard of Steven D'Aprano:
On Thu, 16 Apr 2009 10:39:52 am Tony Nelson wrote:
I don't want there to be any str(msg['tag']) or bytes(msg['tag'])
at all, so there would be no loss of consistency.
That's ...
On approximately 10/6/2009 7:18 AM, came the following characters from
the keyboard of Stephen J. Turnbull:
In the following I use Python 3 terminology: strings are Python
Unicode objects, and bytes are Python bytes objects.
Glenn Linderman writes:
Email messages are bytes. Usually
On approximately 10/6/2009 5:30 PM, came the following characters from
the keyboard of Stephen J. Turnbull:
Glenn Linderman writes:
Yes, I interpreted, possibly misinterpreted, Barry's comment about
storing things as bytes, as that he was figuring to store them in wire
format.
What
On approximately 10/7/2009 3:33 AM, came the following characters from
the keyboard of Stephen J. Turnbull:
Glenn Linderman writes:
If you mean that the email module will keep track of what form the
object is currently represented by, that will eventually result in
UnicodeError: octet
On approximately 10/8/2009 12:16 AM, came the following characters from
the keyboard of R. David Murray:
I'd like to try to summarize what I understand Barry to be saying
Good summary! Deleted all but one point that I'd like to have clarified...
The API also provides ways to build up a
On approximately 10/8/2009 6:00 AM, came the following characters from
the keyboard of Barry Warsaw:
On Oct 8, 2009, at 3:29 AM, Glenn Linderman wrote:
And I agree that APIs to retrieve any MIME part as undecoded bytes is
appropriate; and to retrieve it as decoded strings is appropriate
On approximately 10/8/2009 3:39 PM, came the following characters from
the keyboard of Barry Warsaw:
On Oct 8, 2009, at 5:59 PM, Glenn Linderman wrote:
So to prepend into a text header, you shouldn't need to decode the
undecodable...
Except that you also have to collapse Re:'s and move them
On approximately 10/8/2009 4:20 PM, came the following characters from
the keyboard of Mark Sapiro:
Glenn Linderman wrote:
However, there are definitely mailing lists that don't do that. Google
Groups is one example that doesn't collapse, and always prepends the
headers in front of Re
On approximately 10/8/2009 8:47 PM, came the following characters from
the keyboard of Tokio Kikuchi:
Actually, as long as the prepended text is ASCII, all that work can be
done on the encoded value. When it is not ASCII, it may still be
separated and recognizable. Still that logic is more
On approximately 10/9/2009 5:25 AM, came the following characters from
the keyboard of Barry Warsaw:
On Oct 8, 2009, at 7:02 PM, Glenn Linderman wrote:
Well, that is a feature of some mailing list programs. Those that
want to do that, will have to decode and re-encode.
However
On approximately 10/9/2009 5:05 AM, came the following characters from
the keyboard of Barry Warsaw:
On Oct 8, 2009, at 6:39 PM, Glenn Linderman wrote:
1) wire format. Either what came in, in the parser case, or what
would be generated.
2) internal headers from the MIME part
3) decoded BLOB
On approximately 10/9/2009 6:25 PM, came the following characters from
the keyboard of R. David Murray:
On Fri, 9 Oct 2009 at 17:54, Glenn Linderman wrote:
On approximately 10/9/2009 4:20 PM, came the following characters
from the keyboard of R. David Murray:
On Fri, 9 Oct 2009 at 13:26
On approximately 10/10/2009 2:20 PM, came the following characters from
the keyboard of R. David Murray:
On Fri, 9 Oct 2009 at 11:59, Glenn Linderman wrote:
On approximately 10/9/2009 5:05 AM, came the following characters
from the keyboard of Barry Warsaw:
On Oct 8, 2009, at 6:39 PM, Glenn
On approximately 10/10/2009 9:01 PM, came the following characters from
the keyboard of Stephen J. Turnbull:
Glenn Linderman writes:
(I switched conformant to compliant,
Conformant is in common use. You might be more comfortable with
conforming.
Richard Stallman points out that you comply
On approximately 10/10/2009 5:47 PM, came the following characters from
the keyboard of Stephen J. Turnbull:
Glenn Linderman writes:
On approximately 10/10/2009 8:40 AM, came the following characters from
the keyboard of Stephen J. Turnbull:
So why are we discussing this? We don't
On approximately 10/10/2009 10:12 PM, came the following characters from
the keyboard of R. David Murray:
But perhaps it should be added to the Glossary itself :)
That would, to me, make it more acceptable for use. Like I said, I knew
what was meant, but tried several printed and internet
On approximately 1/25/2010 6:51 PM, came the following characters from
the keyboard of R. David Murray:
On Mon, 25 Jan 2010 16:55:15 -0800, Glenn Lindermanv+pyt...@g.nevcal.com
wrote:
Are there any other *Header APIs that would be required not to produce
exceptions? I don't yet perceive
On approximately 1/25/2010 8:10 PM, came the following characters from
the keyboard of Glenn Linderman:
That's true. The Bytes and String versions of binary MIME parts,
which are likely to be the large ones, will probably have a common
representation for the payload, and could potentially point
On 3/24/2011 2:41 PM, Barry Warsaw wrote:
On Mar 24, 2011, at 05:10 PM, Steffen Daode Nurpmeso wrote:
It would be great if the message (file) size would also be
provided as a public method, so that code-flow decisions can be
made dependend upon the plain size of a message.
(The size is known
On 4/11/2011 2:48 PM, R. David Murray wrote:
For the curious, I just posted a writeup of the process that
produced the header folding algorithm rewrite on my blog:
http://www.bitdance.com/blog/2011/04/11_01_Email6_Rewriting_Header_Folding/
Updated my virus definitions, and it went away.
On 4/11/2011 2:48 PM, R. David Murray wrote:
For the curious, I just posted a writeup of the process that
produced the header folding algorithm rewrite on my blog:
http://www.bitdance.com/blog/2011/04/11_01_Email6_Rewriting_Header_Folding/
Interesting!
[2]
On 4/11/2011 6:09 PM, R. David Murray wrote:
What would work would be to provide an alternate API where the Header
class feeds in an already-split list instead of a string. That makes
sense from several perspectives.
That's the essence of what I meant. An already-split list wouldn't
On 5/16/2011 1:24 PM, R. David Murray wrote:
On Sat, 14 May 2011 15:19:42 -0700, Glenn Lindermanv+pyt...@g.nevcal.com
wrote:
Looks great, conceptually. My only quibble is with the names
.source_value and .decoded: the names are clear, but lengthy (in
combination with stuff before the .).
On 5/16/2011 1:40 PM, R. David Murray wrote:
I've gone through the RFCs and done some additional googling,
and haven't been able to confirm the answer to this question: what
exactly is the syntax when a group is included in an address-list? (See
http://tools.ietf.org/html/rfc5322#section-3.4).
On 7/26/2011 5:38 AM, R. David Murray wrote:
What's the word for what is done when a text message is made to have
a line length of less than 78 by using quoted printable (or base64)
encoding? Is that also folding? If there's no existing term in common
use, folding would make sense to me. So I
26 matches
Mail list logo
