+ 1
2010/6/22 Robert Coup :
> 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.
> * mod_python hasn't had a release since 2007, or a commit since 2008;
You could release the "officially endorsed" external package together with
1.3. So people can start migrating towards that.
However, I assume that people who're still using mod_python, won't be
upgrading to 1.4/1.5 without updating the rest of the system...
We're currently running two websites on
On Jun 23, 9:48 am, Alex Gaynor wrote:
> On Tue, Jun 22, 2010 at 6:47 PM, Graham Dumpleton
>
>
>
>
>
> wrote:
>
> > On Jun 23, 9:41 am, Russell Keith-Magee
> > wrote:
> >> On Wed, Jun 23, 2010 at 5:51 AM, Jacob Kaplan-Moss
> >> wrote:
> >> > On Tue, Jun 22, 2010 at 4:47 PM, Robert Coup
> >>
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 this is being configured at the
>> global level -- i.e., you have to nom
Please send questions about how to use Django to django-users. The topic of
this list is the development of Django itself.
Karen
--
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...@googleg
Hi All,
I want to built a django application for hardware compatibility
testing
Some hardwares are compatible with certain mother board. And
attributes of each hardware are different (I use a ugly table to store
attributes), which are compatible with Hardware types, such as MEM as
SIZE, HDD has Fi
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 you think?
As noted in a separate thread -- we're looking to de
Nice timing :)
On Wed, Jun 23, 2010 at 11:22 AM, Gustavo Narea wrote:
>
> 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
On Tue, Jun 22, 2010 at 6:48 PM, Alex Gaynor wrote:
...
> http://code.djangoproject.com/browser/django/trunk/django/core/handlers/profiler-hotshot.py
>
> (Honestly does anyone use this?)
I think I did a few times in the dark days before debug-toolbar, etc.
--
You received this message because y
On Tue, Jun 22, 2010 at 6:47 PM, Graham Dumpleton
wrote:
>
>
> On Jun 23, 9:41 am, Russell Keith-Magee
> wrote:
>> On Wed, Jun 23, 2010 at 5:51 AM, Jacob Kaplan-Moss
>> wrote:
>> > On Tue, Jun 22, 2010 at 4:47 PM, Robert Coup
>> > wrote:
>> >> While people are throwing around 1.3 ideas... I th
On Jun 23, 9:41 am, Russell Keith-Magee
wrote:
> On Wed, Jun 23, 2010 at 5:51 AM, Jacob Kaplan-Moss wrote:
> > On Tue, Jun 22, 2010 at 4:47 PM, Robert Coup
> > wrote:
> >> While people are throwing around 1.3 ideas... I think we should start
> >> the process of deprecating and removing support
On Wed, Jun 23, 2010 at 11:31 AM, Jerome Leclanche wrote:
> Agreed. mod_python was already "not recommended" for very long; now
> it's dead, I don't see any reason to support it for three full release
> cycles.
I don't either, but I figured the deprecation policy[1] applies to
deployment-related
On Wed, Jun 23, 2010 at 7:28 AM, Alex Gaynor wrote:
> On Tue, Jun 22, 2010 at 6:24 PM, Gustavo Narea wrote:
>> Whoops, I wan't aware of this topic when I posted this:
>>
>> http://groups.google.com/group/django-developers/browse_thread/thread/2e20f4ae486800a1
>>
>> Anyway, I'm +1 on this.
>>
>> O
On Wed, Jun 23, 2010 at 5:51 AM, Jacob Kaplan-Moss wrote:
> On Tue, Jun 22, 2010 at 4:47 PM, Robert Coup
> wrote:
>> While people are throwing around 1.3 ideas... I think we should start
>> the process of deprecating and removing support for mod_python. Why?
>
> The other huge win -- besides your
Agreed. mod_python was already "not recommended" for very long; now
it's dead, I don't see any reason to support it for three full release
cycles.
On Wed, Jun 23, 2010 at 2:28 AM, Alex Gaynor wrote:
> On Tue, Jun 22, 2010 at 6:24 PM, Gustavo Narea wrote:
>> Whoops, I wan't aware of this topic w
On Tue, Jun 22, 2010 at 6:24 PM, Gustavo Narea wrote:
> Whoops, I wan't aware of this topic when I posted this:
>
> http://groups.google.com/group/django-developers/browse_thread/thread/2e20f4ae486800a1
>
> Anyway, I'm +1 on this.
>
> On Jun 22, 10:47 pm, Robert Coup wrote:
>> Hey folks,
>>
>> Wh
Whoops, I wan't aware of this topic when I posted this:
http://groups.google.com/group/django-developers/browse_thread/thread/2e20f4ae486800a1
Anyway, I'm +1 on this.
On Jun 22, 10:47 pm, Robert Coup wrote:
> Hey folks,
>
> While people are throwing around 1.3 ideas... I think we should start
>
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
under mod_python.
At the moment, Django has two so-called handlers:
On Tue, Jun 22, 2010 at 4:47 PM, Robert Coup
wrote:
> While people are throwing around 1.3 ideas... I think we should start
> the process of deprecating and removing support for mod_python. Why?
The other huge win -- besides your great versions -- is that without
mod_python support Django just be
On Tue, Jun 22, 2010 at 4:51 PM, Jacob Kaplan-Moss wrote:
> The other huge win -- besides your great versions -- is that without
... er, *reasons*.
Damned wires getting crossed in my brain.
Jacob
--
You received this message because you are subscribed to the Google Groups
"Django developers"
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:
> My initial impression of django-filetransfers is that you've
> constructed a lot of very complex infrastructure for what is
> ultimately a couple of very simple changes --
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.
* mod_python hasn't had a release since 2007, or a commit since 2008;
it's a dead end. The Apache Foundation b
On Tue, Jun 22, 2010 at 12:24 PM, Paul McMillan wrote:
> I've posted an update with my project status. I made a little progress
> this week, converting 7 model tests. In order to meet my goals for
> finishing the project, I plan to be converting 25 directories a week
> moving forward.
I have two
On Tue, Jun 22, 2010 at 10:01 AM, Alex Gaynor wrote:
> Hey all,
>
> This past week was mostly spent getting lookup's working (and
> negation), that's gone fairly well. Well enough, in fact, that I
> spent most of today getting some low hanging fruit working: namely
> ordering, slicing, and values
On Tue, Jun 22, 2010 at 6:48 AM, Gustavo Narea wrote:
> Hello.
>
> On Jun 14, 1:39 pm, Russell Keith-Magee
> wrote:
>> Ok - at this point, I'm broadly happy with your proposals (subject to
>> the caveats I've given along the way). The next step is to show us
>> actual code. This won't get applied
Jannis,
thanks for the quick and competent reply. It's always fascinating how
one can fail in searching for existing issues and discussions ;)
Flo
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django
Hi Flo,
> I am just wondering why the admin actions are only available through
> the dropdown in the changelist and not as buttons in the change view
> of the object - this is a much requested feature (see
> http://code.djangoproject.com/ticket/5412 and
> http://code.djangoproject.com/ticket/2409
On Tue, Jun 22, 2010 at 2:55 PM, Waldemar Kornewald
wrote:
> Hi,
> first I should say that I'm not 100% sure if this feature should be in
> Django core, so I'm kind-of asking for you opinion.
>
> Problem:
> Currently, Django already has an API for file uploads, but it's not
> useful for the new cl
I am just wondering why the admin actions are only available through
the dropdown in the changelist and not as buttons in the change view
of the object - this is a much requested feature (see
http://code.djangoproject.com/ticket/5412 and
http://code.djangoproject.com/ticket/2409
for slightly outda
On 22 June 2010 19:59, Massimiliano della Rovere <
massimiliano.dellarov...@gmail.com> wrote:
> Anyway using this method I can't sort columns any more.
> This is why I was suggesting having links created by the framework:
> callable aren't sortable.
>
They can be -- set admin_order_field on the c
Anyway using this method I can't sort columns any more.
This is why I was suggesting having links created by the framework: callable
aren't sortable.
On Mon, Jun 21, 2010 at 15:37, Karen Tracey wrote:
> On Mon, Jun 21, 2010 at 4:37 AM, Massimiliano della Rovere <
> massimiliano.dellarov...@gmail
On Tue, Jun 22, 2010 at 9:00 AM, Gert Van Gool wrote:
> What's wrong with the current StorageBackends?
> Apart from the fact that everything goes through Django first, which imho
> isn't a bad default solution (easier for parsing and the like...).
Just to clarify: django-filetransfers is an addit
+ 1 emulation
2010/6/22 Alex Gaynor :
> Hey all,
>
> This past week was mostly spent getting lookup's working (and
> negation), that's gone fairly well. Well enough, in fact, that I
> spent most of today getting some low hanging fruit working: namely
> ordering, slicing, and values. In slicing w
Hi,
first I should say that I'm not 100% sure if this feature should be in
Django core, so I'm kind-of asking for you opinion.
Problem:
Currently, Django already has an API for file uploads, but it's not
useful for the new cloud-based file services which support the more
efficient asynchronous upl
Hi Alex,
On Jun 22, 4:01 am, Alex Gaynor wrote:
> Hey all,
>
> This past week was mostly spent getting lookup's working (and
> negation), that's gone fairly well. Well enough, in fact, that I
> spent most of today getting some low hanging fruit working: namely
> ordering, slicing, and values. I
What's wrong with the current StorageBackends?
Apart from the fact that everything goes through Django first, which imho
isn't a bad default solution (easier for parsing and the like...).
-- Gert
Mobile: +32 498725202
Web: http://gert.selentic.net
On Tue, Jun 22, 2010 at 08:55, Waldemar Kornewa
36 matches
Mail list logo
