I'm an idiot! I had completely forgotten I'd previously ran python setup.py on my server, to test my switch over to python 2.5 had gone alright and all dependencies were met for my new project. A quick find of pyc files from root (/) showed bytecode generated for my project in it's own egg, created by the setup script, which the WSGI loader is obviously using (or maybe pylons' loader is using). A quick re-run of setup.py showed this to be true.
Definitely been a learning experience, cheers for the help. ;) -- Wes http://1stvamp.org/ http://gfbowl.com/ http://leeds2600.org.uk/ 2009/8/5 Wesley Mason <[email protected]>:
I hadn't actually thought of this simple step, so here goes: I ran: `find ./ -type f -name "*.pyc" -print0 | xargs -0 rm` to delete any .pyc files, and double checking they're going: `find ./ -type f -name "*.pyc"` returns nothing So just to make sure (even though it's in daemon mode I'm not leaving anything to chance) I do a full apache2 stop and start, and.....it's still using the old source. In fact if I run this again: `find ./ -type f -name "*.pyc"` I still get nothing. Any ideas? -- Wes http://1stvamp.org/ http://gfbowl.com/ http://leeds2600.org.uk/ 2009/8/5 Graham Dumpleton <[email protected]>:Try removing all the .pyc files in your source tree. If they are newer than source file, then Python will use them instead. If you aren't aware of what they are for, the .pyc files are a cache of byte code generated from compiling the source code. Thus they could contain an older copy of executable code. Graham 2009/8/5 Wes <[email protected]>:Hello, I'm having a slight problem with a small pylons based WSGI app I'm trying to get working on my server. It was working fine, with mod_wsgi (on Apache2, Debian Lenny) under embedded mode, and I didn't mind restarting as I would only load it onto my live server when I needed to do live testing. However, since lunchtime today when trying my latest revision checkout, it was caching the version from the previous day, even after a quick `/etc/init.d/apache2 restart` (which is definitely doing a full reload of apache, but to be sure have also tried a `force- reload`). I've since tried running it in daemon mode, following the exact steps from the mod_wsgi installation notes, and with Apache2's LogLevel set to "info" I can definitely see it is spawning separate processes for each request handle, but still working with old source. I can tell it's old source because entire controller action, along with mako templates, and even some static content, are missing. I have touched my wsgi app, tried changing it's location in fact, looked into file permissions, and user/group permissions, and I'm beginning to run low on options. I'm hoping someone can give me some suggestions as to what might be causing this. Cheers, Wes. >--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "modwsgi" 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/modwsgi?hl=en -~----------~----~----~----~------~----~------~--~---
signature.asc
Description: OpenPGP digital signature
