Russ,
Apologies for forcing the issue & for making a mess of the
``django.core`` namespace. The goal was to help improve the user experience
of sanity-checking their kit, but it seems I did more harm than good.
I'm fine with unifying the two (with option #2 probably being more
likely
Please do not crosspost to both django-users and django-developers: pick
the correct list and post there. The topic of this list is the development
of Django itself, questions about using Django are suited to django-users,
not here.
Karen
--
You received this message because you are subscribed
Hi Group,
could someone please help me with -
http://stackoverflow.com/questions/17184386/providing-admin-actions-to-group-members-in-a-multi-tenant-django-crm-applicatio
Thanks!
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To
On Wed, Jun 19, 2013 at 5:34 AM, Russell Keith-Magee
wrote:
> 1) Keep checksetup as a name, and integrate the GSoC work under that new
> name (including making the API entry points called check() or checksetup()
> ).
>
> 2) Rename `checksetup` to `verify`, setting the
On 19 juin 2013, at 10:34, Russell Keith-Magee wrote:
> 1) Keep checksetup as a name, and integrate the GSoC work under that new name
> (including making the API entry points called check() or checksetup() ).
>
> 2) Rename `checksetup` to `verify`, setting the
Hi all (but especially Daniel)
I've got a quick question about a recent commit and some naming
consequences that I think we need to sort out before we cut the 1.6 beta.
tl;dr - I think we either need to rename the recently added checksetup
command, or do some light refactoring of it's internals