Hi, I'll test it on a large production site (the city envies platform, which is fairly complex as a single tg instance hosts many virtual hosts) and tell you if it works without any problem. But City Envies isn't SA (it's SO), and already working on tg1.1b3 :)
Cheers, Jon On 4 sep, 09:04, Florent Aide <[email protected]> wrote: > On Fri, Sep 4, 2009 at 12:14 AM, Christoph Zwerschke<[email protected]> wrote: > > [...] > > > After having a second look I noticed that after some polishing (already > > done in r6633) this is not a real problem. > > > The old Session.mapper is still available as turbogears.database.mapper > > as long as it's available in SA. So old projects will continue to work > > with SA < 0.6 (emitting a deprecation warning for SA >= 0.5.5). > > [...] > > > So this is "configurable" via the "import mapper from ..." in model.py. > > Right. We just need to document the way to use it. I'll work on the > website issue and then we're good for a release. If some people not > afraid of svn could test it I would be glad. > > Don't be surprised at the version number (at the moment it is 1.1b5) > this is because I changed the release number to make it different from > b3 but did not want to make it final yet. This does not mean we'll > release a beta... I think this time 1.1 is ready for the final. I > personally use it in production since a long time with no issue. > > Florent. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
