On 13 juin 2011, at 18:07, Jannis Leidel wrote:
> On 13.06.2011, at 17:19, Carl Meyer wrote:
>> I agree with all of this. I would be in favor of simply removing the
>> wildcard feature with a note in the release notes, unless someone pops
>> up to argue that it's more widely-used than we think and
On 13.06.2011, at 17:19, Carl Meyer wrote:
> On 06/12/2011 03:35 PM, Aymeric Augustin wrote:
>> I checked the SVN history. This "feature" was never documented, even
>> before the reorganization at r8506. It appears in
>> django/conf/__init__.py when magic-removal is merged (r2809).
>>
>> We just
On 06/12/2011 03:35 PM, Aymeric Augustin wrote:
> I checked the SVN history. This "feature" was never documented, even
> before the reorganization at r8506. It appears in
> django/conf/__init__.py when magic-removal is merged (r2809).
>
> We just discussed it on IRC, and the consensus is that it d
On 12 juin 2011, at 22:35, Aymeric Augustin wrote:
> Hello,
>
> I checked the SVN history. This "feature" was never documented, even before
> the reorganization at r8506. It appears in django/conf/__init__.py when
> magic-removal is merged (r2809).
>
> We just discussed it on IRC, and the cons
Hello,
I checked the SVN history. This "feature" was never documented, even before the
reorganization at r8506. It appears in django/conf/__init__.py when
magic-removal is merged (r2809).
We just discussed it on IRC, and the consensus is that it dates back to before
Django was open-sourced. It
Hi,
I've read source code for django.conf package and as of Django 1.3
INSTALLED_APPS can accept wildcards for application names (e.g.
django.contrib.*). It seems that the official documentation doesn't
mention it in the Available Settings section.
Am I wrong?
--
You received this message becau
