Fine with me.
as
On 22 Mar 2015, at 12:32 pm, Barry Warsaw <ba...@list.org> wrote:
I want to make some minor backward incompatible changes to the JSON
representation for pending mailing lists requests, e.g. subscription holds.
You'll see these for example in urls like:
>>> dump_json('http://localhost:9001/3.0/lists/a...@example.com/requests')
entry 0:
delivery_mode: regular
display_name: Anne Person
email: a...@example.com
http_etag: "..."
language: en
request_id: ...
type: subscription
when: 2005-08-01T07:49:23
The first change is that `type: subscription` requests will change their
`address` key to `email` for consistency with other parts of the API. Second,
there will be no `password` key.
Let me know if this is a problem, and I can copy `email` to `address` so that
both would appear, and add a dummy `password` key.
Cheers,
-Barry
_______________________________________________
Mailman-Developers mailing list
Mailman-Developers@python.org
https://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives:
http://www.mail-archive.com/mailman-developers%40python.org/
Unsubscribe:
https://mail.python.org/mailman/options/mailman-developers/andrew.stuart%40supercoders.com.au
Security Policy: http://wiki.list.org/x/QIA9
_______________________________________________
Mailman-Developers mailing list
Mailman-Developers@python.org
https://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives:
http://www.mail-archive.com/mailman-developers%40python.org/
Unsubscribe:
https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
