There should be a little warning in the 1.0.2 docs or on
http://code.djangoproject.com/wiki/DjangoSpecifications/Core/Threading
that it is *not* thread safe.
I've hit http://code.djangoproject.com/ticket/10470 on production,
applied the patches manually. Please make sure you apply both
http://cod
plete test run, as
10036 shows, up to 10039, those Django versions won't even start.
Slightly off topic: when is 1.0.3 scheduled for? There have been quite
a few commits in the 1.0.x branch since 1.0.2, bugfixes only, if there
aren't any problems it would be nice to have a tested r
Or rather - how to keep the server from blowing up. I've searched the
web before, but nothing I've found solves the problem.
Some background info - I'm running worldoflogs.com, a site that gets
around 100 concurrent requests during rush hour and still growing
rather rapidly. Django powers the fro
On Jun 12, 4:43 am, Graham Dumpleton
wrote:
>
> On Jun 12, 11:51 am, Miles wrote:
> > If someone has an idea how to get memory usage at about the same with
> > lower cpu cost than a full GC every request, please tell.
>
> In Python, garbage collecting is not real garbage
We have a default virtual host configured to show a maintenance page,
so when we disable the django virtual host, everything gets direct
there.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To
3. If it is not a bug but Django's own wrapper doesn't deal with this
> problem, how do I deal with it? Should I simply create a new database
> connection for every single web request?
>
> James
Connections aren't thread safe - you have to ensure every thread gets
its own connec
I've been running the python memcached connector for a while, without
much trouble. But just today during a stress test of one of the feeds
(read: many many requests expected), I've ran into an out of sockets
situation.
After every single request, the cache backend forces a disconnect from
all me
after
every request? For us, keeping it alive works, but for others, it
might break. You can't really file that as a bug, right? Reopened the
original ticket, if it gets rejected, at least people can find the
solution on google :P
Miles
--~--~-~--~~~---~--~~
You r
127.0.0.1 www.example.com to /etc/hosts will help
but i just get localhost page that tells me cherokee is running:/ Any
one can help?
Best regards
Miles
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email
g multiple sites out
of one Django installation? I see the sites table and site_id setting,
but haven't seen much about how best to use them.
thanks in advance,
Miles
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google G
As part of my web-app, I would like to allow users to upload files. Towards
this end
I have a model field:
zipfile = meta.FileField(upload_to =".")
This has a custom manipulator with the field line:
formfields.FileUploadField(field_name="zipfile"),
and a template entry of:
Hi,
I am new to Django. The tutorial all went fine, but I'm having no success in
getting
Apache to yield anything useful. I have probably done something truly stupid
-- and
hopefully obvious -- and would appreciate someone pointing out my error(s).
System: Debian/Linux (Etch/testing: Apache-
Thanks, Ian, for trying. Following your recommendation to
SetEnv DJANGO_SETTINGS_MODULE myproject.settings
then on the first try the error message becomes:
Mod_python error: "PythonHandler django.core.handlers.modpython"
Traceback (most recent call last):
File "/
Newbie problem ...
While django-admin.py startproject myproject worked, other django-admin
actions (e.g. init -- for setting up user authentication) don't. I tried
setting DJANGO_SETTINGS_MODULE using both '/' and dotted directory notation,
and using long and short paths to the settings file, an
ribute as a label to the "qty" field. In
essence, Item left joined to Site through Allocation.
Is this easily achievable?
Thanks,
Miles
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group
15 matches
Mail list logo