Re: Future-proofing django.template (and elsewhere) against circular imports

2008-02-02 Thread Adrian Holovaty
On Feb 1, 2008 12:47 PM, Tom Tobin <[EMAIL PROTECTED]> wrote: > That said, I'd like to propose that the majority of the contents of > django.template.__init__ be preemptively moved to > django.template.main, and imported back into __init__ as necessary. > Furthermore, I'd like to see all use of __

Re: Proposal: deprecated Model.__init__(*args)

2008-02-02 Thread Adrian Holovaty
On Jan 29, 2008 2:13 PM, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote: > I'd like to deprecate initializing models using positional arguments > (i.e. ``p = Person(1, 'Joe Somebody')``) in favor of only allowing > keyword-argument initialization (i.e. ``p = Person(id=1, name='Joe > Somebody')``). I

Re: Future-proofing django.template (and elsewhere) against circular imports

2008-02-02 Thread Tom Tobin
On 2/2/08, Justin Bronn <[EMAIL PROTECTED]> wrote: > > > I'm *way* off base at the moment (and stuck gradually walking towards > > HEAD, fixing my patch in increments; this is where git definitely has an > > advantage over hg, but I'm using the latter). > > I've found hg-svn to be particularly usef

Re: Future-proofing django.template (and elsewhere) against circular imports

2008-02-02 Thread Justin Bronn
> I'm *way* off base at the moment (and stuck gradually walking towards > HEAD, fixing my patch in increments; this is where git definitely has an > advantage over hg, but I'm using the latter). I've found hg-svn to be particularly useful in helping me pull changes from the various SVN Django bra