On Fri, May 1, 2015 at 9:01 PM, Ben Sizer <kylo...@gmail.com> wrote: > Another good question, and this gives us the answer. The module lists are > quite different, as I'd expect because the load happens in the context of the > full application whereas the dump happens as a standalone script. But > literally every module that is in the 'before dump' list is in the 'before > load' list - except OMDBMap. Like the error says! What /is/ in the 'before > load' list however is "my_wsgi_app.OMDBMap". The module has been imported, > but the pickle algorithm is unable to reconcile the module in the WSGI app's > namespace with the module referenced in the pickle file. > > So... I don't know how to fix this, but I do now know why it fails, and I > have a satisfactory answer for why it is acting differently on the Linux > server (and that is just because that is the only one running under WSGI). > Two out of three isn't bad! >
Cool! That's part way. So, can you simply stuff OMDBMap into sys.modules prior to loading? It might be a bit of a hack, but it should work for testing, at least. Conversely, you could change the dump script to import via the name my_wsgi_app to make it consistent. ChrisA -- https://mail.python.org/mailman/listinfo/python-list
