There is really a bigger question in my mind about the appropriateness of using
django.utils.unittest in the testing overview section. It is an optimization
that the warning admits is fairly limited for real testing and is premature for
the first example. It would be better to break out the
>
> [1] http://amirouche.github.com/blog/django-admin-next-a-new-api.html
>
this doesn't work anymore I moved @
http://blog-amirouche.dotcloud.com/notes/2013/admin-next-a-new-api.html
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To
2013/3/30 Victor Hooi
> heya,
>
> Aha, yes - we need a roadmap, and somebody from the team to execute it
> *grins*.
>
> For the former - I believe there was already discussions on that sort of
> thing on this board?
>
> There's a wiki page with some notes as well:
>
>
heya,
Aha, yes - we need a roadmap, and somebody from the team to execute it
*grins*.
For the former - I believe there was already discussions on that sort of
thing on this board?
There's a wiki page with some notes as well:
https://code.djangoproject.com/wiki/AdminNext
I also had a look at
Hi,
On 03/30/2013 10:32 AM, Yo-Yo Ma wrote:
> A common pattern for larger applications is to maintain bits of reusable
> code outside of applications, but still inside of a project (e.g.,
> myproject/lib), due to synchronous development and modification of
> application and library code. They're
On Tuesday 19 March 2013, Florian Apolloner wrote:
> Hi,
>
> On Tuesday, March 19, 2013 8:21:05 AM UTC+1, Shai Berger wrote:
> > Is there any interest in fixing this, specifically?
>
> Sure, I just don't have to knowledge to debug cx_Oracle, so if you are up
> to please. Although I think the
Will dropping support for Python 2.6 have any effect here? I assumed the
example would just switch to using unittest.TestCase instead of
django.utils.unittest.TestCase, and the usability issue would remain.
I think having the warning above the example would help, but I'd still
prefer having
A common pattern for larger applications is to maintain bits of reusable
code outside of applications, but still inside of a project (e.g.,
myproject/lib), due to synchronous development and modification of
application and library code. They're parts that aren't really large enough
to warrant
Am Freitag, 29. März 2013 21:05:05 UTC+1 schrieb Andrew Ingram:
>
> I like the concept of this, because it's something I've often wanted
> myself. But I want to bring up a couple of points:
>
> 1) Some websites rely on the obscurity of some of their URLs as an
> additional security measure
Hey,
three weeks ago I posted a patch and test. I just asked on IRC what to do
to get things moving, and I was told to post
to the mailing list about it.
The issue is:
https://code.djangoproject.com/ticket/19998
Patch and tests are included.
best regards,
Christoph
--
You received this
10 matches
Mail list logo