I've run into a project that demands Python 2.3 (they've got a large codebase that's still running on Python 2.3) and I'll be implementing some features in that application that utilize Elixir (if possible).
I see that some patches are in the trunk of SQLAlchemy that support Python 2.3, but Elixir still has trouble in some cases. I'm going to file a bug to this effect and I have a patch that fixes the two issues I've encountered through my own code. There are still 11 tests that fail under Python 2.3 that fall into 4 categories (list sort parameter, @beforeinsert decorator, generator comprehension, and a Crypto lib issue). Of course, more issues may emerge after the tests are fixed. Questions Can my patch be integrated into the trunk? Is my technique sound? If I invest the time on addressing the compatibility issues with the rest of the errors, can they be integrated as well? I guess what it really comes down to is what is the interest in maintaining Python 2.3 compatibility? Regards, Jason --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SQLElixir" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlelixir?hl=en -~----------~----~----~----~------~----~------~--~---
