[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [pygame] Color, unpacking to r,g,b and r,g,b,a - ValueError: too many values to unpack

To: pygame-users@xxxxxxxx
Subject: Re: [pygame] Color, unpacking to r,g,b and r,g,b,a - ValueError: too many values to unpack
From: Greg Ewing <greg.ewing@xxxxxxxxxxxxxxxx>
Date: Thu, 18 Jun 2009 14:08:09 +1200
Delivered-to: archiver@xxxxxxxx
Delivered-to: pygame-users-outgoing@xxxxxxxx
Delivered-to: pygame-users@xxxxxxxx
Delivery-date: Wed, 17 Jun 2009 22:07:14 -0400
In-reply-to: <64ddb72c0906162341h15449e56nb14f24e1a8cbb711@xxxxxxxxxxxxxx>
References: <64ddb72c0906162202r432887e5l760c6bb2cca8660f@xxxxxxxxxxxxxx> <4A388D38.5040304@xxxxxxxxx> <64ddb72c0906162341h15449e56nb14f24e1a8cbb711@xxxxxxxxxxxxxx>
Reply-to: pygame-users@xxxxxxxx
Sender: owner-pygame-users@xxxxxxxx
User-agent: Mozilla Thunderbird 1.0.5 (Macintosh/20050711)

René Dudfield wrote:

If it could unpack to 3, or 4 depending on the number of elements on
the left, I think I'd prefer that though.


That's not possible, because as far as the object is
concerned, it's just being iterated over. It has no
way of knowing that it's being unpacked, or how many
items are expected.

I think I'd go for the subtype.

--
Greg

References:
- [pygame] Color, unpacking to r,g,b and r,g,b,a - ValueError: too many values to unpack
  - From: René Dudfield
- Re: [pygame] Color, unpacking to r,g,b and r,g,b,a - ValueError: too many values to unpack
  - From: Lenard Lindstrom
- Re: [pygame] Color, unpacking to r,g,b and r,g,b,a - ValueError: too many values to unpack
  - From: René Dudfield

Prev by Author: Re: Functions that steal references (Re: [pygame] [patch] minor memory leaks...)
Next by Author: Re: [pygame] Bitmask Collision Response
Previous by thread: Re: [pygame] Color, unpacking to r,g,b and r,g,b,a - ValueError: too many values to unpack
Next by thread: [pygame] update() weirdness
Index(es):
- Author
- Thread