Apologies for the length of this email, but I've been holding back on
my thoughts about Python version compatibility for a while, mostly due
to the fact that:
1. Until recently, we didn't have a stable Django release series on
which to begin considering the process of dropping support in
an
Thank you very much, Marc.
I 'm trying to generate one form using two models, I know how to generate
form using one model, but I really don't know how to point one form to two
models, I really appreciate if you can give me some suggestion or point me
to some helpful resource.
thanks and have a won
I'm +1 for the reasons of lack of upstream support.
On Wed, Nov 26, 2008 at 10:42 PM, mrts <[EMAIL PROTECTED]> wrote:
>
> On Nov 26, 3:20 am, Julien Phalip <[EMAIL PROTECTED]> wrote:
> > On Nov 26, 11:43 am, "Russell Keith-Magee" <[EMAIL PROTECTED]>
> > wrote:
> >
> >
> > > On Wed, Nov 26, 2008 a
On Tue, Nov 25, 2008 at 3:08 PM, Jacob Kaplan-Moss
<[EMAIL PROTECTED]> wrote:
>
> Hi folks --
>
> I'd like to officially drop Python 2.3 support in Django 1.1. Discuss.
>
> Jacob
+1 -- because reusable apps developers could all close those
py2.3-related bugs as wontfix. One less cost to share sha
On Wed, 2008-11-26 at 01:42 -0800, mrts wrote:
[...]
> * Python 2.3 is officially not supported by Python developers since
> 2.3.5; it
>doesn't even receive security patches -- so, effectively, everybody
> should
>avoid using it (the same is true for 2.4, 2.4.5 is supposedly the
> last r
On Wed, Nov 26, 2008 at 9:03 PM, xshen <[EMAIL PROTECTED]> wrote:
>
> is there anyone know how to create one view from multiple models? any
> input is appreciated
You may want to ask in http://groups.google.com/group/django-users
This groups is intended for the development of Django itself, not f
is there anyone know how to create one view from multiple models? any
input is appreciated
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develo
On Wed, Nov 26, 2008 at 10:05 PM, Diego Andrés Sanabria Martin
(diegueus9) <[EMAIL PROTECTED]> wrote:
> My point is to use the text of lorem2.com for the current lorem ipsum
> tag, this text is more effective for test the divs.
Unless you speak Latin, it's unlikely noone will notice the difference
Sorry,
My point is to use the text of lorem2.com for the current lorem ipsum
tag, this text is more effective for test the divs.
On Wed, Nov 26, 2008 at 14:30, Marc Fargas <[EMAIL PROTECTED]> wrote:
> On Wed, Nov 26, 2008 at 1:29 AM, Diego Andrés Sanabria Martin
> (diegueus9) <[EMAIL PROTECTED]>
On Wed, Nov 26, 2008 at 1:29 AM, Diego Andrés Sanabria Martin
(diegueus9) <[EMAIL PROTECTED]> wrote:
> Hi,
>
> In Django in somwhere is a tag Lorem Ipsum, i suggest to use Lorem Ipsum 2
>
> http://lorem2.com/
I do not get the point, and by your message I'd say you've not used
the lorem tag at all.
+1
Update your damn distros. Generators are important :)
On Nov 26, 10:33 am, "Gary Wilson Jr." <[EMAIL PROTECTED]> wrote:
> On Wed, Nov 26, 2008 at 7:23 AM, varikin <[EMAIL PROTECTED]> wrote:
> > On Nov 25, 7:16 pm, Malcolm Tredinnick <[EMAIL PROTECTED]>
> > wrote:
> >> However, even saying Dja
Diego Andrés Sanabria Martin (diegueus9) wrote:
> Hi,
>
> In Django in somwhere is a tag Lorem Ipsum, i suggest to use Lorem Ipsum 2
>
I don't see any benefits to using "Lorem Ipsum 2." This site looks like
they are just another lorem ipsum generator. Django could be used to
create a site like t
On Wed, Nov 26, 2008 at 7:23 AM, varikin <[EMAIL PROTECTED]> wrote:
> On Nov 25, 7:16 pm, Malcolm Tredinnick <[EMAIL PROTECTED]>
> wrote:
>> However, even saying Django 1.1 is the last 2.3-compatible version and
>> we drop it afterwards gives us a reasonable 3.0 support timeline, since
>> our time
On Tue, Nov 25, 2008 at 11:07 PM, Ambrish Bhargava
<[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I am trying to develop new backend support for Django. I ran "python
> manage.py test" command to execute test. Now I am facing following
> problem:
> 1. Python Database API Specification v2.0 implementation
And what are the benefits?
On Wed, Nov 26, 2008 at 16:36, Alexander Lyabah <[EMAIL PROTECTED]>wrote:
>
> I am already posted it on Django Snippets
> http://www.djangosnippets.org/snippets/1218/
>
> I want to introduce my idea about url resolving in Django.
>
> It can be useful for using object-o
I am already posted it on Django Snippets
http://www.djangosnippets.org/snippets/1218/
I want to introduce my idea about url resolving in Django.
It can be useful for using object-oriented includes in common patter.
It can be useful for created function which will be running only
before functi
On Nov 25, 7:16 pm, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
>
> However, even saying Django 1.1 is the last 2.3-compatible version and
> we drop it afterwards gives us a reasonable 3.0 support timeline, since
> our timeframe doesn't really encourage any official 3.0 support for 1.1.
I am +1
On Wednesday 26 November 2008 01:16:00 Malcolm Tredinnick wrote:
> However, even saying Django 1.1 is the last 2.3-compatible version
> and we drop it afterwards gives us a reasonable 3.0 support
> timeline, since our timeframe doesn't really encourage any official
> 3.0 support for 1.1.
Agreed,
On Nov 26, 3:20 am, Julien Phalip <[EMAIL PROTECTED]> wrote:
> On Nov 26, 11:43 am, "Russell Keith-Magee" <[EMAIL PROTECTED]>
> wrote:
>
>
> > On Wed, Nov 26, 2008 at 2:08 AM, Jacob Kaplan-Moss
>
> > <[EMAIL PROTECTED]> wrote:
>
> > > Hi folks --
>
> > > I'd like to officially drop Python 2.3 supp
On Wed, Nov 26, 2008 at 10:16 AM, Malcolm Tredinnick
<[EMAIL PROTECTED]> wrote:
>
> However, even saying Django 1.1 is the last 2.3-compatible version and
> we drop it afterwards gives us a reasonable 3.0 support timeline, since
> our timeframe doesn't really encourage any official 3.0 support for
+1 to Malcolm and Julien.
Having a clear roadmap before you make changes is really helpful. I've
been bitten by changes appearing in code suddenly because I've tuned
out for a few weeks. There is always the option of sticking to an
earlier revision, but that doesn't help for long.
I also agree i
Hi,
I googled and noticed
http://products.ingeniweb.com/catalog/iw-mock.ldapwhich allows mocking
/ monkey patching of the ldap interface. Also custom
ldif files could be created to test different settings / combinations (I'm
not sure how much they can cover - things like pre binding for LDAP loo
On Tue, Nov 25, 2008 at 18:08, Jacob Kaplan-Moss
<[EMAIL PROTECTED]> wrote:
> I'd like to officially drop Python 2.3 support in Django 1.1. Discuss.
Yes please.
Maybe put up a poll, prominently, on the djangoproject.com homepage?
Maybe make a timeline? Drop 2.3-support by date x, drop 2.4-suppo
23 matches
Mail list logo
