On Mon, Jun 20, 2011 at 10:57 PM, Benedict Holland
wrote:
> I ran into a problem with running unit tests against views where it
> said that:
>
> HINT: Truncate table "challenges_challenge_attachments" at the same
> time, or use TRUNCATE ... CASCADE.
>
> I patched it to be this, only for postgresq
Hi Luke,
This looks like it could be really interesting or useful, but at the
> moment I can't quite see my way to working out how to use it. I'd really
> like to be able to:
>
> 1) apply a patch (or two) to my copy of Django
>
Would you like me to attach a patch to a ticket? I could attach it to
On Jun 20, 12:13 pm, Andre Terra wrote:
> Have we moved forward with this issue at all? What is its current status?
I also maintain an external package that implements fieldsets (django-
form-utils [1]). Both django-form-utils and WTForm take the approach
of adding a Python data structure to Form
Have we moved forward with this issue at all? What is its current status?
Thank you in advance.
Sincerely,
André Terra
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To view this discussion on the web visit
https://groups.google.com/
I ran into a problem with running unit tests against views where it
said that:
HINT: Truncate table "challenges_challenge_attachments" at the same
time, or use TRUNCATE ... CASCADE.
I patched it to be this, only for postgresql. This patch seems to work
quite well. I don't know if there are any p
Hello,
Ticket #10938 [1] suggests declaring inlines in fieldsets, and was closed as
wontfix.
I think this ticket mixes two different things:
(1) make it possible to *declare* inlines in
ModelAdmin.fieldsets instead of ModelAdmin.inlines. This is a bad idea:
there should be only one way to dec
