Hi,
Raising this here as suggested by Tim on this
bug: https://code.djangoproject.com/ticket/25374, with discussion also on
django users
here: https://groups.google.com/forum/#!topic/django-users/lsDP5oUWOsw
The underlying bug is that ModelAdmin checks are run against the class not
the instan
The enum seems fine. Where should it be defined? Should the docs mention
the integer values at all, or are you required to use the enum?
I don't think setting date_hierarchy to a tuple is any cleaner.
On Monday, August 31, 2015 at 12:54:21 PM UTC-6, Tim Graham wrote:
>
> This seems okay at first
I created a ticket: https://code.djangoproject.com/ticket/25376#ticket
You can read about how to get started contributing to Django in our docs:
https://docs.djangoproject.com/en/dev/internals/contributing/
If you have any trouble, #django-dev is a good place to ask questions.
Thanks!
On Thurs
As this thread is most likely leading to a dead-end, let me try to close it
by summarizing it:
Original proposal:
- adding a property to the current migration class to make it more
extendable
Idea behind the proposal:
- being able to move the migrations generated in my venv when running
makemi
On Wednesday 09 September 2015 16:35:16 Markus Holtermann wrote:
> On Wednesday, September 9, 2015 at 9:21:43 PM UTC+10, Shai Berger wrote:
> > On 9 בספטמבר 2015 13:29:58 GMT+03:00, Marten Kenbeek > >
> > >The order of migrations within a single app is fixed.
> >
> > No, actually it isn't. It is
Yes, this is a perfect solution to this issue. But how do we proceed with
it ?
Sorry, but I am new to django contribution !
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group a
Yes, that's the perfect solution to this problem.
How do we proceed with it then, as I am new to contributing to Django?
-Anjul
On Thursday, 10 September 2015 00:55:27 UTC+5:30, Tim Graham wrote:
>
> I think a better use of time could be to update the docs to more strongly
> recommend virtualenv
At the risk of re-opening this thread, I have just run into a very similar
situation (see https://code.djangoproject.com/ticket/25374) and find that
having the errors printed to the console is actually helpful - as I've had
to silence errors to get the correct code to run, seeing if there's any
Thanks
El miércoles, 9 de septiembre de 2015, 17:27:25 (UTC+2), Tom Evans escribió:
>
> On Wed, Sep 9, 2015 at 4:11 PM, Xavier Palacín Ayuso
> > wrote:
> > I want to collects current user in model signal pre_save, to prevent
> remove
> > super user permission to current super users.
>
> Hi Xa
