Jeroen Ruigrok van der Werven kirjoitti: > -On [20071123 16:53], Christian Boos ([EMAIL PROTECTED]) wrote: >> 1. setup.py: there's no dependency on SQLAlchemy set, so running e.g. >> "test" results in a backtrace, until SQLAlchemy is (easy_)installed. > > Yeah, it's on my list of stuff todo. Just been discussing too many > SA-specifics with Manuzhai. It will be there this weekend at least. I am > currently aiming for 0.4.x as minimum.
Is there any reason to aim for older releases of SA? >> 2. I've got: "ERROR: Testing env.get_known_users" on Windows >> >> Seems due to a Permission denied: 'c:...trac-tempenv\\db\\trac.db' >> issue. That probably happens because there's a live SQLite connection at >> that time. > > Very likely. Windows seems to default to exclusive locks faster than Unix. And very keen to keep locks. :) >> 3. starting tracd: Could not parse rfc1738 URL from string >> 'sqlite:db/trac.db' >> >> Well, we probably want to keep compatibility here with existing [trac] >> db strings. The move to SQLAlchemy should be transparent to the user. > > Yeah, but will we document the new preferred connection string anyway or do we > want to keep our 'own'? Support old one for backwards compatibility. Promote new method as preferred. After release or two, drop backward support. It gives time for migration. As known it's not nice to break things but since Trac is not "1.0" doing that is that bad. Same is done for CS for templates. Support exists and will be dropped in the future. Oh and BTW, if you need help with SA stuff, I can try to contribute something. -- Jani Tiainen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" 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/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
