I'm in complete agreement with Alex. -1 from me. Explicit is better
than implicit, and to my mind, hiding imports just complicates the
learning curve associated with Django's package tree.
If you *really* want this, there are hooks into ipython et al that can
do this; I don't see it as something
Hi Peter,
Thanks for that; I've just marked the ticket as a release blocker, so
at the very worst, this should be corrected for the 1.5 release.
Yours,
Russ Magee %-)
On Tue, Aug 28, 2012 at 11:56 PM, peter wrote:
> The wrong rows being deleted is a possibility. Here's
Hi Phill,
On 08/28/2012 03:51 PM, Phill Tornroth wrote:
> 2. Are you also -1 on making it easier for projects like shell_plus to
> add locals to the shell? What's happening right now is pretty
> unfortunate. I can only see upside in an adjustment to the internal API
> that doesn't make this kind
Totally fair, couple of things:
1. For backward compatibility and the confusion you mentioned, I'd suggest
this be not enabled by default. Let people who want the feature (the people
who download shell_plus for instance) enable it. My pull request leaves it
totally off by default, retaining
On Tue, Aug 28, 2012 at 2:40 PM, Phill Tornroth wrote:
> 'Ello.
>
> I'm gauging support for a tiny new feature, or at least a refactoring of
> an internal API that will allow the feature to be developed without code
> duplication. I'd like to stop typing import statements
'Ello.
I'm gauging support for a tiny new feature, or at least a refactoring of an
internal API that will allow the feature to be developed without code
duplication. I'd like to stop typing import statements for all of my models
and other common stuff into my django shell. In fact, I'd love
Hello all,
I have a suggestion for improving the tabular inline view of the admin site
(contained in /contrib/admin/templates/admin/edit_inline/tabular.html). I recently
overloaded this template for my own purposes, and am wondering if the
Django community would find my changes useful. If so,
The wrong rows being deleted is a possibility. Here's an example:
class Through(models.Model):
two = models.ForeignKey('Model2', to_field='spot')
one = models.ForeignKey('Model1')
class Model1(models.Model):
name = models.CharField(max_length=100)
class Model2(models.Model):
Hi all,
During Piotr's GSOC addressing customizable serialization I've been
continued to work on my own implementation.
I've now got what feels to me to be a natural conclusion of the design,
which is the 'forms' branch of the
The worst in this situation is that we have 2012 3Q in the yard but the
issue still open :(
Четвер, 12 серпня 2010 р. 10:32:32 UTC+3 користувач Tomi Pieviläinen
написав:
>
> I first approached the users-list to find out if I was simply doing
> something wrong, but seems like there's no
10 matches
Mail list logo