Adrian Holovaty wrote:
> This is a nice, clean approach -- good work! The patch is looking
> good. Go ahead and check it in at your leisure.
Checked in as http://code.djangoproject.com/changeset/5803
--~--~-~--~~~---~--~~
You received this message because you are
On 8/5/07, Andy Gayton <[EMAIL PROTECTED]> wrote:
>
> Adrian Holovaty wrote:
> I'm worried about the emphasis in Django tests to share enormous fixture
> datasets. Some rules of thumbs I've drifted towards after ending up
> with unruly test suites a couple of times are:
I'm not sure I understand
On 8/4/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
> On 8/4/07, A Mele <[EMAIL PROTECTED]> wrote:
> > Does that mean generic relations are production ready although they
> > are not yet implenteed in the admin?
>
> Exactly - the code's fine; there's just no admin support yet.
Though if you h
Howdy --
Thanks for the code. However, in the future, please post code snippets
to djangosnippets.org; that's what it's there for.
Jacob
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To
On 8/4/07, Tom Tobin <[EMAIL PROTECTED]> wrote:
> On 8/4/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
> >
> > On 8/1/07, James Bennett <[EMAIL PROTECTED]> wrote:
> > > Let's just do:
> > >
> > > 1. Autoescape on by default.
> > > 2. Autoescape is turned off by the {% autoescape off %}
> > > 3. A
On 8/4/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> On 8/1/07, James Bennett <[EMAIL PROTECTED]> wrote:
> > Let's just do:
> >
> > 1. Autoescape on by default.
> > 2. Autoescape is turned off by the {% autoescape off %}
> > 3. Autoescape happens irregardless of what the template's source fil
On 7/31/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
> #3297 - FileField/ImageField for newforms
> http://code.djangoproject.com/ticket/3297
>
> #4001 - saving m2m fields on newforms with commit=False
> http://code.djangoproject.com/ticket/4001
>
> #4418 - Newforms media
> http://code.django
On 8/4/07, Gary Wilson <[EMAIL PROTECTED]> wrote:
> I attached a new patch which issues a PendingDeprecationWarning.
>
> The new patch also uses a metaclass for FormField and Field classes to
> decorate __init__ instead of having to call legacy_maxlength in almost
> every subclass's __init__. Thi
On 8/1/07, James Bennett <[EMAIL PROTECTED]> wrote:
> Let's just do:
>
> 1. Autoescape on by default.
> 2. Autoescape is turned off by the {% autoescape off %}
> 3. Autoescape happens irregardless of what the template's source file
> or source string happened to be named.
I'm +1 on this approach.
Jacob Kaplan-Moss wrote:
> On 7/30/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>> That sounds like the best thing to do -- I don't see a huge need to
>> deprecate maxlength immediately, or even issue warnings about it. The
>> change gets a +1 from me.
>
> I'd say that making maxlength issue a
Adrian Holovaty wrote:
> Hi all (but mostly Russell, the Test Master General :) ),
>
> I have a significantly large set of fixture data for Django unit tests
> in a work project, and the time lag in clearing and reinserting the
> data between each test is getting to be frustrating. However, a
from django.conf.urls.defaults import *
from django.views.generic.simple import direct_to_template
from django.contrib.admin.views.decorators import
staff_member_required
def login_url(regex, view, *p,**args):
return url(regex,staff_member_required(view),*p,**args)
def login_patterns(*p):
That's fine! Thank you Jacob!
On 4 ago, 16:34, "Jacob Kaplan-Moss" <[EMAIL PROTECTED]>
wrote:
> On 8/4/07, A Mele <[EMAIL PROTECTED]> wrote:
>
> > Does that mean generic relations are production ready although they
> > are not yet implenteed in the admin?
>
> Exactly - the code's fine; there's ju
On 8/4/07, A Mele <[EMAIL PROTECTED]> wrote:
> Does that mean generic relations are production ready although they
> are not yet implenteed in the admin?
Exactly - the code's fine; there's just no admin support yet.
Jacob
--~--~-~--~~~---~--~~
You received this m
hey mike, we use a modified version of dbmigration in production at
work, I sent you an email with our mods.
cheers,
peter
> This part of the plan looks quite similar to the dbmigration project
> athttp://www.aswmc.com/dbmigration/- hope that its useful in some way :)
> If not, ah well, it work
Simon Willison wrote:
> Generally I'm really glad to see that most people have come round to
> autoescaping being on by default now. I personally don't see it as a
> way of protecting newbie developers so much as it's a way of
> protecting all developers from one tiny mistake blowing the security
On 8/3/07, pk11 <[EMAIL PROTECTED]> wrote:
> the issue with object_id is that mssql can not insert an integer PK
> into a TEXT field.
>
I guess I'm confused. Admin LogEntryManager forces object_id to a
string before saving. Do you see somewhere that's directly filling
LogEntry.object_id with
Hi,
The generic relations status showed in the wiki is "Code move is done
(Malcolm), admin support (Jacob) not done. Needs newforms-admin merge
first."
Does that mean generic relations are production ready although they
are not yet implenteed in the admin?
Regards,
A Mele
--~--~-~--~--
Hi,
> 6) The user can define evolutions. They exact sequence is defined in
> the Meta property of the model:
>
> class Author(Model):
>...
>class Meta:
> evolution = [
> 'v1',
> 'v2',
> 'pre_christmas_2006',
> 'valentines_day_2007',
> 'v5
On 8/4/07, Brantley Harris <[EMAIL PROTECTED]> wrote:
>
> ps. Did you ever see my long-ago proposal?
> (http://code.djangoproject.com/wiki/SchemaEvolutionProposal)
Looking at this, we share a few similar ideas. Here goes my attempt at
a description of what I was thinking.
My goals:
* Keep the mo
20 matches
Mail list logo
