Re: Sets

2008-07-20 Thread Cole Tuininga
>> On Sat, Jul 19, 2008 at 11:50 PM, Julien Phalip <[EMAIL PROTECTED]> wrote: >> > >> Oops - sorry, I wasn't very clear in my original request. I'm looking >> for a set type in the Django model hierarchy. Does this make more >> sense? > > A set is just an unordered collection of objects. In othe

Re: Sets

2008-07-20 Thread Cole Tuininga
On Sat, Jul 19, 2008 at 11:50 PM, Julien Phalip <[EMAIL PROTECTED]> wrote: > > 'set' is a Python standard object [1], since version 2.4. In version > 2.3 you need to import the 'Set' package first. > So, if you care about backward compatibility in Python, the most > secure way to import it is: Oo

Re: Sets

2008-07-20 Thread Malcolm Tredinnick
On Sun, 2008-07-20 at 10:05 -0400, Cole Tuininga wrote: > On Sat, Jul 19, 2008 at 11:50 PM, Julien Phalip <[EMAIL PROTECTED]> wrote: > > > > 'set' is a Python standard object [1], since version 2.4. In version > > 2.3 you need to import the 'Set' package first. > > So, if you care about backward

Re: Sets

2008-07-20 Thread Karen Tracey
On Sun, Jul 20, 2008 at 10:05 AM, Cole Tuininga <[EMAIL PROTECTED]> wrote: > > On Sat, Jul 19, 2008 at 11:50 PM, Julien Phalip <[EMAIL PROTECTED]> wrote: > > > > 'set' is a Python standard object [1], since version 2.4. In version > > 2.3 you need to import the 'Set' package first. > > So, if you

Re: Sets

2008-07-19 Thread Julien Phalip
'set' is a Python standard object [1], since version 2.4. In version 2.3 you need to import the 'Set' package first. So, if you care about backward compatibility in Python, the most secure way to import it is: try: set except NameError: from sets import Set as set # Python 2.3 fallback [