Thank you for the reply and your help, Jonathan. I've answered your questions inline.
Oh! Deleting the .pyc files did it. Thank you very much! I remember learning about the potential for that problem at a Python Bootcamp, but hadn't encountered it before. I appreciate everyone's help. On Tuesday, June 30, 2015 at 3:36:29 PM UTC-5, Jonathan Vanasco wrote: > > Some possibly dumb questions: > > 1. are you failing to start it with the same .ini > The two projects have different .ini files specific to each project, though they are very similar in their Pyramid setup. > 2. can you start the failed project using the working virtualenv, and vice > versa? > Thank you--I hadn't thought to try that. The failed project is failed in both virtualenvs, but the working project works in both virtualenvs. > 3. have you tried with a new virtualenv, and comparing? > Not yet, but I'll put that on the to-do list. Given what I found with your suggestion of running each project in the other's virtualenv, I'm thinking the issue is somewhere in the failed project. > 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pylons-discuss. For more options, visit https://groups.google.com/d/optout.
