2011/3/5 Juan Antonio Ibáñez <[email protected]> > You are right. BASELINE virtualenv was not created using --no-site- > packages. How did you knoe that? >
It was the only thing that made sense. When I ran the commands on my side in a known clean virtualenv, it worked just fine. So, the only option had to be something corrupting your virtualenv, and that left very few possibilities. Either a bad copy of the library got installed, or was being pulled from the OS. > Is always necessary to use a BASELINE virtualenv and a application > virtualenv? > Actually, you only need one virtualenv at all for the application. In the docs on the site, BASELINE is meant to refer to your application's virtualenv. -- Michael J. Pedersen My IM IDs: Jabber/[email protected], ICQ/103345809, AIM/pedermj022171 Yahoo/pedermj2002, MSN/[email protected] -- You received this message because you are subscribed to the Google Groups "TurboGears" 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?hl=en.
