Thanks all. This has been a helpful and enlightening glimpse into the
values and priorities the Django project is stewarded with.
I appreciate the time and attention.
-Phill
On Tuesday, August 28, 2012 4:53:26 PM UTC-7, Russell Keith-Magee wrote:
>
> I'm in complete agreement with Alex. -1 from
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 a
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 o
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 cur
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 for all of my models
> an
'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 for
