On Mon, 2011-08-29 at 14:49 -0700, Ben Sizer wrote: > Hah, that was it. No, it wasn't what I expected. I had expected this: > > /home/kylotan/webapps/testproj/myapp/python2.7/myapp/__init__.pyc > > But it was actually: > > /home/kylotan/webapps/testproj/lib/python2.7/myapp/__init__.pyc > > It looks like the install process has installed the project as a > package in the lib directory which takes precedence over the app > itself in the main directory. > > I have no idea whose fault that is, because Python packaging is still > entirely opaque to me after a decade of use, but perhaps it's > something Webfaction do wrong when they run the quickstart? (I expect > there's something else wrong in that they don't require that you > activate the virtualenv before running the app, but it doesn't seem to > make any difference to me either way.)
What happened is: - you (or webfaction's bootstrap script) ran "setup.py install", which placed a *copy* of the install in your virtualenv's site-packages directory - you hacked on the generated code and it had no effect until you told the virtualenv to use the development code by running "setup.py develop". "setup.py install" is good for installing an app as a production app; otherwise "setup.py develop" is the right thing for development. - C -- You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en.
