Some possibly dumb questions: 1. are you failing to start it with the same .ini 2. can you start the failed project using the working virtualenv, and vice versa? 3. have you tried with a new virtualenv, and comparing? 4. have you tried deleting all the .pyc files? sometimes an old one will somehow get stuck and never regenerate, which can cause odd issues like this. 5. any chance you updated python between creating the virtualenvs? if you update the interpreter, you usually need to reinstall every package.
-- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-discuss+unsubscr...@googlegroups.com. To post to this group, send email to pylons-discuss@googlegroups.com. Visit this group at http://groups.google.com/group/pylons-discuss. For more options, visit https://groups.google.com/d/optout.
