Wouldn't it make sense to add a keyword argument to both itervalues
and iteritems, which lets you get lists instead? That would seem
easier than writing new methods. Example:
>>> dictionary.iteritems(as_list=True)
...
--~--~-~--~~~---~--~~
You received this messa
On Wed, Aug 20, 2008 at 10:01 AM, James Turk <[EMAIL PROTECTED]> wrote:
>
> Quite understandable that this isn't a priority by any means, ticket
> including patch is up here for posterity:
> http://code.djangoproject.com/ticket/8447
The patch was a bit off; it used iteritems in iterlists in test
Quite understandable that this isn't a priority by any means, ticket
including patch is up here for posterity:
http://code.djangoproject.com/ticket/8447
On Aug 20, 9:20 am, "Jeremy Dunck" <[EMAIL PROTECTED]> wrote:
> On Wed, Aug 20, 2008 at 8:08 AM, Malcolm Tredinnick<[EMAIL PROTECTED]> wrote:
>
On Wed, Aug 20, 2008 at 8:08 AM, Malcolm Tredinnick
<[EMAIL PROTECTED]> wrote:
...
>> Also because of this should 8399, trivial as it is, go up on
>> BackwardsIncompatibleChanges?
>
> Yes, it should. Hopefully Gary (Wilson) will see this and make the
> change, since it was his commit. It was no do
On Tue, 2008-08-19 at 22:09 -0700, James Turk wrote:
[...]
> It seems that changing my code to use lists will give almost the same
> result, but would it be possible to get an "iterlists" method to
> replace the iteritems which was changed?
This is probably worth leaving until after 1.0 for now.
I've been trying to stay up to date when testing locally and just
noticed 8399 seems to be the source of a break in my code where
MultiValueDict's iteritems was used. I see that this relates to
http://code.djangoproject.com/ticket/7331 and I understand a decision
had to be made.
iteritems used t
