OK, i added this in 2298. I dont notice any speed enhancement in overall performance of the unit tests even though it builds on "set" and not "sets.Set"...this is probably because we dont use OrderedSet too much. Also i had to make some changes so its compatible with 2.3 (no generator expressions, subclasses "Set" which is "set" or "sets.Set").
On Feb 4, 3:42 am, [EMAIL PROTECTED] wrote: > > > - using "value.lower() == value" instead of value.islower() > > > ha > > > >>> x = "27" > > >>> x.islower() > > > False > > > >>> x.lower() == x > > > True > > > breaks a lot of tests too > > okay, forget that. Here an example OrderedSet over set; that seems to > give a bigger speedup than anything else, and without touching > anything. > IMO any bigger speedup would require logical changes, e.g. not doing > certain things at all, caching etc. > > oset.py.bz2 > 1KDownload --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
