> > >http://code.google.com/p/modwsgi/wiki/IssuesWithPickleModule > > You are misunderstanding the mod_wsgi documentation. That only applies > to data types specified inside the actual WSGI script file. It doesn't > apply to data types specified elsewhere in standard Python modules. > > In particular the documentation says: > > """Note that these limitations only apply to the WSGI application > script file which is the target of the WSGIScriptAlias, AddHandler or > Action directives. Any standard Python modules or packages which make > up an application and which are being imported from directories > located in sys.path using the 'import' statement are not affected.""" >
Thank you Graham, your mail helped and it works as documented (although that same paragraph was that confused me initially) I have actually tried pickling and had unpickling errors on the non- Django side before looking for a cause finding the above documentation. My errors were due to similar copies of the class being defined in two different places with different parent module names instead of on a common sys.path. Now I have retried knowing it should work and indeed it does. Thanks for your work on mod_wsgi. Jani -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
