I gave locmem a quick whirl, and it blew up too. At least it returned
an error on the external page:
Mod_python error: "PythonHandler django.core.handlers.modpython"
Traceback (most recent call last):
File "/usr/local/lib/python2.5/site-packages/mod_python/apache.py",
line 299, in HandlerDispatch
result = object(req)
File "/home/grmadmin/webapps/django/django/core/handlers/
modpython.py", line 177, in handler
return ModPythonHandler()(req)
File "/home/grmadmin/webapps/django/django/core/handlers/
modpython.py", line 150, in __call__
response = self.get_response(request)
File "/home/grmadmin/webapps/django/django/core/handlers/base.py",
line 59, in get_response
response = middleware_method(request)
File "/home/grmadmin/webapps/django/django/middleware/cache.py",
line 60, in process_request
response = cache.get(cache_key, None)
File "/home/grmadmin/webapps/django/django/core/cache/backends/
locmem.py", line 23, in get
return copy.deepcopy(self._cache[key])
File "/usr/local/lib/python2.5/copy.py", line 189, in deepcopy
y = _reconstruct(x, rv, 1, memo)
File "/usr/local/lib/python2.5/copy.py", line 337, in _reconstruct
state = deepcopy(state, memo)
File "/usr/local/lib/python2.5/copy.py", line 162, in deepcopy
y = copier(x, memo)
File "/usr/local/lib/python2.5/copy.py", line 254, in _deepcopy_dict
y[deepcopy(key, memo)] = deepcopy(value, memo)
File "/usr/local/lib/python2.5/copy.py", line 189, in deepcopy
y = _reconstruct(x, rv, 1, memo)
File "/usr/local/lib/python2.5/copy.py", line 322, in _reconstruct
y = callable(*args)
File "/usr/local/lib/python2.5/copy_reg.py", line 92, in __newobj__
return cls.__new__(cls, *args)
TypeError: object.__new__(listiterator) is not safe, use
listiterator.__new__()
On Feb 12, 3:09 pm, Jeff <[EMAIL PROTECTED]> wrote:
> Does it happen with all cache backends?
>
> On Feb 12, 3:14 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> wrote:
>
> > Upon further investigation, it appears the feeds framework is not the
> > involved. Even getting a plain page I hit the same problem. As soon as
> > I make the call from the external site the django site freaks out when
> > caching is turned on through memcache.
>
> > On Feb 12, 12:08 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> > wrote:
>
> > > So I'm attempting to implementent caching with memcached today --
> > > yeah, yeah, I know, long overdue -- and am hitting a snag. The problem
> > > isn't with memcached, which webfaction so pleasantly has installed for
> > > me, or with setting up the caching in django, which seems to have gone
> > > pretty easily. I'm running into a problem with feeds and caching.
>
> > > When I have caching running, after a few minutes it stops working
> > > properly, the pages take forever to load or proxy error out, and the
> > > whole thing goes belly up. After testing various things, I believe the
> > > issue is related to a legacy php-based site which is pulling the
> > > django site's forum feed and displaying the latest topics.
>
> > > Could there be some issue with pulling that feed and memcached? Does
> > > any of this make any sense? Any ideas?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
