On Fri, Oct 19, 2012 at 10:20 AM, Barry Warsaw wrote:
> On Oct 18, 2012, at 09:23 PM, Daniel Holth wrote:
>
>>The email module provides an ordered multidict interface to the data.
>>The first tag wins (if you improperly define Name: twice for example),
>>but the order of everything is preserved. W
On Oct 18, 2012, at 09:23 PM, Daniel Holth wrote:
>The email module provides an ordered multidict interface to the data.
>The first tag wins (if you improperly define Name: twice for example),
>but the order of everything is preserved. We just don't need it,
>except that it might be surprising to
Added some notes about the (lack of) ordering.
The email module provides an ordered multidict interface to the data.
The first tag wins (if you improperly define Name: twice for example),
but the order of everything is preserved. We just don't need it,
except that it might be surprising to see you
Will add that the order is not significant. It is essentially a multidict.
On Thu, Oct 18, 2012 at 2:45 PM, wrote:
> I'd like to request that PEP 426 is extended to talk about the order of
> fields.
> In particular, for the Extension field, is it necessary that all "additional
> tags"
> follow i
I'd like to request that PEP 426 is extended to talk about the order
of fields.
In particular, for the Extension field, is it necessary that all
"additional tags"
follow immediately the respective Extension field?
I also request that RFC 2119 terminology is followed strictly. In particular,
t
