On Sat, 01 Sep 2012 13:55:11 +0900, "Stephen J. Turnbull"
wrote:
> "Martin v. Löwis" writes:
>
> > Unfortunately, this conflicts with the desire to use UTF-8 in attribute
> > values - RFC 822 (and also 2822) don't support this, but require the
> > use oF MIME instead (Q or B encoding).
>
>
"Martin v. Löwis" writes:
> Unfortunately, this conflicts with the desire to use UTF-8 in attribute
> values - RFC 822 (and also 2822) don't support this, but require the
> use oF MIME instead (Q or B encoding).
This can be achieved simply by extending the set of characters
permitted, as MIME
On Fri, Aug 31, 2012 at 12:53 PM, R. David Murray wrote:
> On Fri, 31 Aug 2012 12:18:05 -0400, Daniel Holth wrote:
>> Some edits to include / and remove rfc822 again. What is the right
>> email.policy.Policy()?
>
> When I discussed using email to parse metadata with Tarek a long time
> ago, I tho
On Fri, 31 Aug 2012 12:18:05 -0400, Daniel Holth wrote:
> Some edits to include / and remove rfc822 again. What is the right
> email.policy.Policy()?
When I discussed using email to parse metadata with Tarek a long time
ago, I thought he was going to move to using a delimiter-substitution
algorit
Some edits to include / and remove rfc822 again. What is the right
email.policy.Policy()?
https://bitbucket.org/dholth/python-peps/changeset/8ec6dd453ccbde6d34c63d2d2a18393bc70cf115
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org
Am 31.08.12 15:57, schrieb Nick Coghlan:
However, also +1 on using "/" as the extension separator to avoid
ambiguity in field names, as well as restoring the explicit
requirement that metadata entries use valid RFC 822 metasyntax.
Unfortunately, this conflicts with the desire to use UTF-8 in at
On Fri, Aug 31, 2012 at 10:41 PM, R. David Murray wrote:
> It also allows for typo detection, which automatically interpreting
> prefix strings as extensions names would not.
+1 on retaining the explicit extension field, mainly for the
cross-validation benefits (including easily checking which ex
On Fri, 31 Aug 2012 07:01:17 -0400, Daniel Holth wrote:
> On Aug 31, 2012, at 6:54 AM, Donald Stufft wrote:
> > Unless i'm mistaken (which I may be!) I believe that a / can be used as
> > the separator between the namespace and the "real" key.
> >
> > Home-page: http://www.python.org
> > Extensi
Am 31.08.12 12:54, schrieb Donald Stufft:
On Friday, August 31, 2012 at 6:48 AM, "Martin v. Löwis" wrote:
3. There should be a specification of how collisions between extension
fields and standard fields are resolved. E.g. if I have
Extension: Home
Home-page:http://www.python.org
is Home-page
On Aug 31, 2012, at 6:54 AM, Donald Stufft wrote:
> On Friday, August 31, 2012 at 6:48 AM, "Martin v. Löwis" wrote:
>> 3. There should be a specification of how collisions between extension
>> fields and standard fields are resolved. E.g. if I have
>>
>> Extension: Home
>> Home-page: http://ww
On Friday, August 31, 2012 at 6:48 AM, "Martin v. Löwis" wrote:
> 3. There should be a specification of how collisions between extension
> fields and standard fields are resolved. E.g. if I have
>
> Extension: Home
> Home-page: http://www.python.org
>
> is Home-page the extension field or the P
11 matches
Mail list logo
