There was already a discussion several times about that. It would be
definitely woth reviewing.
There's another ticket related to this with patches and tests (duplicate?)
http://code.djangoproject.com/ticket/13941
A.
--
Ales Zoulek
+420 604
.
A.
--
Ales Zoulek
+420 604 332 515
Jabber: ales.zou...@gmail.com
--
On Thu, Jul 15, 2010 at 2:01 PM, Ales Zoulek <ales.zou...@gmail.com> wrote:
> Okay,
>
> ticket created as #13941
>
> I'll try to find
Okay,
ticket created as #13941
I'll try to find out more and let you know in this thread.
Thanks,
A.
--
Ales Zoulek
+420 604 332 515
Jabber: ales.zou...@gmail.com
--
On Thu, Jul 15, 2010
ricRelation fields.
On the other hand, I'm not sure it's possible to edit just
GenericRelation class to fix that.
Regards,
Ales
--
Ales Zoulek
+420 604 332 515
Jabber: ales.zou...@gmail.com
-
I like the option (2).
Could some of you provide a patch for the ticket in the proposed fashion?
Ales
--
Ales Zoulek
+420 604 332 515
Jabber: ales.zou...@gmail.com
--
On Sat, Feb 20, 2010
as
well (global actions, extra context, items per page in change list, etc...)
What are your thoughts about that?
Regards,
Ales
------
Ales Zoulek
+420 604 332 515
Jabber: ales.zou...@gmail.com
--
Since this would obviously create a lot of external dependecies of Django
package (X, GTK, reinteract). I'd prefer if you'd just create a reausable
app, that would add ./manage.py reinteract command.
Ales
--
Ales Zoulek
+420 604 332 515
be great to have them both in the same timeline in order of execution.
(That could ease tracking down some SQLs called "magicaly" somewhere outside
the views eg. in template rendering.)
------
Ales Zoul
happen, but Python's indirection facility has gotten
> me in trouble more often than I like to admit. Anybody have any
> concrete examples of what could go wrong, rather than a generalized
> queasy feeling
