Alright, so this is surprising (to me). In my other post [1] I mentioned random import errors that I was having trouble reproducing on a consistent basis. Chris suggested rolling back to an earlier revision of Satchmo to see if this was a regression. I did not get to that yet, but it looks like I don't need to. After I made the above mentioned change to the shop.models file, *all* import errors disappeared.
What is especially interesting is that one of the sites has its own virtualenv, while the other 5 share another (the contents are identical and built from the same pip requirements file). I was getting import errors across both virtualenvs but I only modified the shop.models in the virtualenv used by the single site. Now all import errors from all sites have gone away. At this point I'm going to review my modwsgi configs, but it seems as though there is some strange interaction going on with the two virtualenvs/modwsgi and something particular to Satchmo and its dependencies (did not have any import errors with the 3 non-Satchmo sites). Hopefully I can gain some additional insight into what's going on, so I can either eliminate my temporary patch or come up with a patch that could be justified as belonging in Satchmo. Cheers, John-Scott [1] https://groups.google.com/d/topic/satchmo-users/p-K21Ks4BbA/discussion -- You received this message because you are subscribed to the Google Groups "Satchmo users" 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/satchmo-users?hl=en.
