That's a good idea.

I do have a correction. In addition to deleting the .pyc files, I was 
playing with my import statements. The problem returned after uncommenting 
one of the wtforms imports I'd missed.

This whole mess was caused by a typo--I apologize for taking up your time. 
Turns out that wtforms and wftorms are very similar-looking words. I'm not 
surprised my app couldn't find module wftorms. 

On Wednesday, July 1, 2015 at 9:59:48 AM UTC-5, Jonathan Vanasco wrote:
>
>
>
> On Wednesday, July 1, 2015 at 9:32:41 AM UTC-4, Brian Looker wrote:
>>
>> 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 put a dumb little file called 'cleanup.py' in every project.  it's just 
> some crude shell commands to delete all the .pyc .pyo files and everything 
> under 'data' so I can quickly start fresh.
>
> it has solved so many odd situations like you describe!
>

-- 
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.

Reply via email to