On Aug 24, 12:17 pm, Gaëtan de Menten <[email protected]> wrote: > Of course. However, I will not apply any patch to trunk which breaks > compatibility with 2.x just yet. So, we'll have to either use an hybrid > approach like SQLAlchemy (with py3k code in specially crafted comments) > or a different branch, I'm not sure which. If you have a strong > preference either way, feel free to do so.
Actually, after posting I decided to just go ahead and try 2to3 on it. It almost works out of the box. There's one small issue which I believe I've corrected, and it works well under py3k with my test app.. I'm putting together a patch to use 2to3 conversion in setup.py to produce a py3k version out of the box (no breakage to 2.x involved), and will submit it in a little bit.. One other question: Are there any unit tests, etc, for Elixir? I noticed in the setup.py it's configured to use nose, but I'm not finding anything in the distribution that looks like Nose tests (or any other kind of tests).. I was hoping for something I could run through quickly to confirm that this thing does appear to be doing everything it's supposed to correctly after the conversion.. -- 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.
