On Mon, Jul 22, 2013 at 12:21 PM, Some Developer
wrote:
> On 14/07/13 20:17, Florian Apolloner wrote:
>
>> Hi,
>>
>> I'd like to get rid of everything FCGI-specific in Django sooner or
>> later (rather sooner). Flup isn't maintained since a long time and there
>> is no ticket tracker to report stu
On 14/07/13 20:17, Florian Apolloner wrote:
Hi,
I'd like to get rid of everything FCGI-specific in Django sooner or
later (rather sooner). Flup isn't maintained since a long time and there
is no ticket tracker to report stuff. Graham pointed out that if someone
wants to use FCGI they can use
htt
My understanding was Django is a WSGI application, and as such its role is
to process requests handed to it. It isn't the server as such.
It's the role of a WSGI publisher to accept requests and pass them on to an
appropriate handler. So, uWSGI, gunicorn, flup and mod_wsgi as the
Publishers we m
On Sun, Jul 21, 2013 at 11:39 AM, Juan Luis Boya wrote:
> * An asynchronous server may be attending many client connections at a time
> for each worker thread. Concurrency is achieved within the thread using an
> application specific dispatcher. In an asynchronous server, there is only
> one block
Hello,
I have some awesome news today. At long last I managed to finally get
the refactor of ForeignKey to pass the entire test suite. It's only
one configuration (CPython 2.7 + SQLite), but it's a start. Due to the
nature of my changes, I expect that only database creation should be
prone to erro
Explicit is better than implicit and `all()` is more a `Manager` concept than a
`QuerySet` one.
IMO `QuerySet.all()` should only be used when API parity with `Manager` is
needed.
Internally `QuerySet` uses `_clone()` rather than `all()` and with #20625 on
its way, I think it's useful to have a
Can't we just use .all() in views instead of creating a new QuerySet method
which does exactly the same thing?
On Sun, Jul 21, 2013 at 12:34 PM, Loic Bistuer wrote:
> My attempt with a public `QuerySet.clone()` method and docs for
> `*ObjectMixin.queryset`:
>
> https://github.com/django/django/p
> Juan, technically Django isn't a server at all...
>
Django is a web application framework whose operation consists on waiting
for HTTP requests from the network (encapsulated with WSGI) and replying
each one of them with a HTTP response. Call it what you want.
> whether it's sync, async,
My attempt with a public `QuerySet.clone()` method and docs for
`*ObjectMixin.queryset`:
https://github.com/django/django/pull/1384
Made a PR to facilitate review and discussion, feel free to close if you think
it's the wrong approach.
--
Loic
--
You received this message because you are su
On 21/07/2013 05:08, Curtis Maloney wrote:
I wasn't aware there was a particular performance issue, but I'll
certainly keep it in mind.
Take a look at this:
http://www.peterbe.com/plog/fcgi-vs-gunicorn-vs-uwsgi
I've probably already said it but if you want some help with this
project I'd be
10 matches
Mail list logo
