You are correct, and I just found this last night. We'll be getting newer versions of the .egg out very shortly that will correct the problem finally.
On Tue, May 24, 2011 at 11:56 AM, MattRock <[email protected]> wrote: > This has happened in the last few days and I have confirmed. On a > brand new machine with nothing more than a TG2 project installed, > sqlalchemy 0.7.0 is now installing to the virtualenv which produces a > non-functioning stock version of Turbogears2. With SQLalchemy 0.7.0, > the initial connection to the site produces an "ImportError: cannot > import name ClassManager" error. > This can be fixed by back-versioning SQLalchemy to 0.6.7 [easy_install > sqlalchemy==0.6.7] but I thought it was an issue worthy of front and > center issues. > > Any web searching on this issue provides no help. > > FWIW, > MattRock > > -- > 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. > > -- Michael J. Pedersen My IM IDs: Jabber/[email protected], AIM/pedermj022171 Yahoo/pedermj2002, MSN/[email protected] My LinkedIn Profile: http://www.linkedin.com/in/michaeljpedersen Twitter: pedersentg -- 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.
