gt; I feel like there's almost always a way to avoid metaclasses.
>
> Have you tried adding your relations in the
>
> signal?
>
> For more context, could you post some of your metaclass code and maybe
> part of a "AppRegsitryNotReady" traceback or two?
>
> Also, get_field_by_na
Hi guys,
I am using a metaclass to standardize how I link two classes, on Django
1.6. This is done in order to have a generic way of connecting classes
without having to know the name of the fields being linked.
Basically, I have in my metaclass '*post_new*' method to get the 'other'
model,
Hi Russel,
On Tuesday, March 11, 2014 1:16:19 AM UTC+1, Russell Keith-Magee wrote:
>
>
> On Tue, Mar 11, 2014 at 2:14 AM, Matthieu Rigal
> <matt@googlemail.com
> > wrote:
>
>> Hi guys,
>>
>> I wanted to talk about the ticket
>> https://code
Hi guys,
I wanted to talk about the
ticket https://code.djangoproject.com/ticket/7231 in the django-dev forum,
but my contribution was just deleted, so I'm posting it here to at least
get a chance for a discussion.
One argument of the core devs in the ticket is that extra is a bad thing to
Is it somehow planned that Django Users can dialog with him to express some
desires ?
For example, I would be very happy to see a reimplementation of the
annotate and aggregate functions, as they make the queries so slow by
grouping by all the fields that I always have to use raw SQL to group
Hi all,
I had already post it as an answer to a previous problem, but since I did
not see any answer, I create a new topic. On a RC1, just after upgrading
from b4 and without changing nothing, this is what I get when trying to run
the tests :
It tries to apply migrations on the test DB it is
Hi Ramiro,
Thanks for the fix ! I've checked the diff and this looks great :-) Also no
need to add i18n anymore to the pip, you save some MB and some install time
:-)
BUT I actually couldn't test it, because some other changes just prevent me
to run any test with any runner...
It tries to
On Wednesday, October 23, 2013 12:14:45 PM UTC+2, Matthieu Rigal wrote:
>
> Do you plan to release the C1 with a tag also on Github ? I'm used to grab
> versions from there...
> https://github.com/django/django/releases
>
> Thanks,
> Matt
>
> On Wednesday, Octobe
Do you plan to release the C1 with a tag also on Github ? I'm used to grab
versions from there...
https://github.com/django/django/releases
Thanks,
Matt
On Wednesday, October 23, 2013 5:08:33 AM UTC+2, James Bennett wrote:
>
> It's almost here!
>
> Tonight we've issued a release candidate for
Hi all,
I know that TransRealMixin already was a problem in the past and I thought
it was "fixed" in the meaning that it was incorporated in the project.
(https://github.com/django/django/pull/1147)
I tried to run my actual tests (developed on 1.4.x) on the 1.6b4 and here
is what comes out
Hi all,
I was trying to update a snippet to create a custom filter for the Django
Admin running under versions 1.4/1.5, but I came across a point I am not
able to solve myself anymore... Could anybody get a look at the following
(code is imho more readable on stackoverflow) and eventually
11 matches
Mail list logo