> I have worked on the 1.1 release and I have all tests working in TG > itself and in the QS template (the default one with SQLAlchemy, with > and without identity)!
This is great news, thanks a lot for your work Florent! > In the process I removed all deprecation warnings from SQLAlchemy > 0.5.5 about the session_mapper. > > At the moment I have just replaced the session mapper with the > sqlalchemy.orm.mapper. BUT this means that user code that relied on > the session_mapper behaviour (instanciating the object with arguments, > auto saving, query method on the class) will break. > > We could try to mimic the session_mapper behavior (it is documented in > the SQLAlchemy documentation) but I would rather avoid this cruft and > explain how to migrate from the old SQLAlchemy way to the new one... > > What do others out there think? I only use sqlobject so I'm not really effected either way. My only hope is that sqlobject will continue to work with 1.1 just as it did in past releases. Cheers, Daniel -- Psss, psss, put it down! - http://www.cafepress.com/putitdown --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
