On Wed, Jun 23, 2010 at 11:06 PM, Robert Coup
wrote:
> On Thu, Jun 24, 2010 at 4:24 AM, Waldemar Kornewald
> wrote:
>> FileField gets a new method prepare_upload() which takes the following
>> arguments:
>> * request
>> * upload_url: the target URL of the upload view
>> * private: should this be
The problem of including javascript files/libraries was discussed
quite a few times on this mailing list. (the problems start to appear
when two or more reusable apps are used on the same page and both of
them reference same javascript libraries, thus conflicting with each
other )
The overall cons
On Thu, Jun 24, 2010 at 4:55 AM, Robert Coup
wrote:
> Hi again,
>
>> Jacob said: I'm +1e100 or so.
>> Russ said: +1.
>
> Now lives as http://code.djangoproject.com/ticket/13820
>
>>
>> The only catch I can think of that hasn't been raised is the hotshot
>> profiling handler; it's currently depende
On Jun 24, 6:55 am, Robert Coup wrote:
> Hi again,
>
> > Jacob said: I'm +1e100 or so.
> > Russ said: +1.
>
> Now lives ashttp://code.djangoproject.com/ticket/13820
>
>
>
> > The only catch I can think of that hasn't been raised is the hotshot
> > profiling handler; it's currently dependent on t
Thanks for the tips guys.
I implemented this in my app, and it's interesting, at least. After
quite a bit of refactoring, I was left with my solution. I see what
you're saying about coupling serialization strategies with model
definitions. This is an interesting post-refactoring feeling. Usually
a
On Thu, Jun 24, 2010 at 4:24 AM, Waldemar Kornewald
wrote:
> FileField gets a new method prepare_upload() which takes the following
> arguments:
> * request
> * upload_url: the target URL of the upload view
> * private: should this be only privately accessibly or also publicly?
> (default: False;
Hi again,
> Jacob said: I'm +1e100 or so.
> Russ said: +1.
Now lives as http://code.djangoproject.com/ticket/13820
>
> The only catch I can think of that hasn't been raised is the hotshot
> profiling handler; it's currently dependent on the modpython handler.
> I don't think there's a whole lot
Hi Anton,
On Wed, Jun 23, 2010 at 10:13 PM, Anton Bessonov wrote:
>>
>> * mod_wsgi is better in every way.
>
> And? Jinja2-Template Engine is every way better as Django Template Engine.
> Drop DJango Template Engine and support Jinja2?
Russell explained it, but mod_wsgi:
- is actively develope
On Wed, Jun 23, 2010 at 2:58 AM, Russell Keith-Magee
wrote:
> On Wed, Jun 23, 2010 at 2:58 AM, Waldemar Kornewald
> wrote:
>> On Tue, Jun 22, 2010 at 2:40 PM, Russell Keith-Magee
>> wrote:
>>> On Tue, Jun 22, 2010 at 2:55 PM, Waldemar Kornewald
>>> wrote:
>>> It also strikes me that a lot of th
On Sun, Jun 20, 2010 at 6:16 AM, Byron wrote:
> Yes I agree. I never quite understood why the
> CACHE_MIDDLEWARE_KEY_PREFIX was implemented, but not at the lower
> level (did the cache API become available after the middleware
> caching?). Of course a custom backend can be written, but then there
On Wed, Jun 23, 2010 at 5:50 PM, robin nanola wrote:
> i figured it out.. thanks anyway.
>
> On Wed, Jun 23, 2010 at 5:36 PM, hooda_28 wrote:
>>
>> how will i do something like "select from table1 where table1.col1 =
>> table1.col2" in django.
>>
>> thanks in advance.
For future reference - Djan
On Wed, Jun 23, 2010 at 6:43 PM, Andy Kelley wrote:
> I posted this in django-users but someone said I should post it in
> django developers, so here we are.
>
> I am coming up with a framework that helps serialization of models. My
> idea is for each field to have a view permissions level: PUBLIC
On Wed, Jun 23, 2010 at 7:53 PM, Gert Van Gool wrote:
> So in theory, if you change the mod_python handler to one of the projects
> mentioned (like paste.modwsgi).
> mod_python is "promoted" to the same status as FastCGI?
I'm not sure I understand your question.
I suppose the approach of using p
2010/6/23 Andy Kelley :
> I posted this in django-users but someone said I should post it in
> django developers, so here we are.
>
> I am coming up with a framework that helps serialization of models. My
> idea is for each field to have a view permissions level: PUBLIC,
> OWNER, or ADMIN. I want t
i figured it out.. thanks anyway.
On Wed, Jun 23, 2010 at 5:36 PM, hooda_28 wrote:
> how will i do something like "select from table1 where table1.col1 =
> table1.col2" in django.
>
> thanks in advance.
--
robin n. nanola
systems analyst / application developer
Philippine Dealing Systems Gr
I posted this in django-users but someone said I should post it in
django developers, so here we are.
I am coming up with a framework that helps serialization of models. My
idea is for each field to have a view permissions level: PUBLIC,
OWNER, or ADMIN. I want to have a model to dict function tha
how will i do something like "select from table1 where table1.col1 =
table1.col2" in django.
thanks in advance.
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To uns
So in theory, if you change the mod_python handler to one of the projects
mentioned (like paste.modwsgi).
mod_python is "promoted" to the same status as FastCGI?
-- Gert
Mobile: +32 498725202
Web: http://gert.selentic.net
On Wed, Jun 23, 2010 at 13:43, Russell Keith-Magee
wrote:
> On Wed, Jun
I've watched the video of the keynote speech, and the following struck me as
an "opportunity for django".
Ala the speech given.
http://www.google.com/buzz/ianbicking/BRWDjsMCGWQ/I-like-the-original-proposal-move-PyPI-stuff-into#127681396096
Thoughts?
--
You received this message because y
On Wed, Jun 23, 2010 at 5:26 PM, Tom Evans wrote:
> On Wed, Jun 23, 2010 at 12:22 AM, Gustavo Narea wrote:
>> Hello,
>>
>> I'm going to work on some patches to improve WSGI support, and I found
>> something that, if changed, could make my patches and django.core.handlers
>> simpler... As well as
On Wed, Jun 23, 2010 at 6:13 PM, Anton Bessonov wrote:
>
>> Hey folks,
>>
>> While people are throwing around 1.3 ideas... I think we should start
>> the process of deprecating and removing support for mod_python. Why?
>>
>> * mod_wsgi is better in every way.
>>
>
> And? Jinja2-Template Engine is
Hey folks,
While people are throwing around 1.3 ideas... I think we should start
the process of deprecating and removing support for mod_python. Why?
* mod_wsgi is better in every way.
And? Jinja2-Template Engine is every way better as Django Template
Engine. Drop DJango Template Engine a
On Wed, Jun 23, 2010 at 12:22 AM, Gustavo Narea wrote:
> Hello,
>
> I'm going to work on some patches to improve WSGI support, and I found
> something that, if changed, could make my patches and django.core.handlers
> simpler... As well as make it possible to use WSGI middleware with Django
> unde
Hello,
On 23 June, 01:00, Russell Keith-Magee
wrote:
> On Wed, Jun 23, 2010 at 7:22 AM, Gustavo Narea wrote:
> > To sum up, I'm proposing two things:
> > 1.- Making the WSGI handler the only handler.
> > 2.- If we want to keep mod_python support, use a mod_python<->WSGI wrapper.
>
> > What do
24 matches
Mail list logo
