I created a Django Trac ticket for
this: https://code.djangoproject.com/ticket/20165
On Saturday, March 30, 2013 11:30:44 PM UTC-4, Brian Schott wrote:
>
> There is really a bigger question in my mind about the appropriateness of
> using django.utils.unittest in the testing overview section. I
As Andrew says, some "rely" on the obscurity of this server side
information. The same can be said of translations. I'd like to see better
support for javascript preprocessing.
gettext(...) in javascript could be preprocessed if the language is known.
url_resolve('name', { ...}) could probably a
On Sat, Mar 30, 2013 at 7:20 PM, Victor Hooi wrote:
>
> From the existing projects, we can draw two clear requirements that people
> want:
>
>- Changing the look and feel - I'm not sure what Django core's
>feelings on it, but there seems to be a feeling from the community that the
>lo
Hi all,
There are some important design decisions to be made if we include
unittest2 discovery into Django.
This message documents a proposed API, the pros and cons, and
decisions that need to be made.
https://code.djangoproject.com/ticket/17365
-- Limitation of current test setup: --
* Tests
That's excellent news! Thanks, Carl.
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-developers+unsubscr...@googlegroups.com.
To post to this group,
On Sun, Mar 31, 2013 at 6:20 AM, Victor Hooi wrote:
> heya,
>
> Aha, yes - we need a roadmap, and somebody from the team to execute it
> *grins*.
>
No - We need someone from the core team to *commit* it. We don't need
someone from the core team to *build* it.
It's also worth pointing out that t
