Re: Support for unittest -k option

2019-03-11 Thread Arthur Rio
I’m +1 on no short-hand. Also “kdb” is a little to close to “pdb” and doesn’t really make sense to me. — Arthur On March 11, 2019 at 3:33:50 PM, Dan Davis (dansm...@gmail.com) wrote: I personally don't think a short-hand is needed. On Mon, Mar 11, 2019 at 10:41 AM Tim Graham wrote: > -kdb

Re: Migration strategy for proxy model permissions to use their own content type

2019-01-07 Thread Arthur Rio
. Best regards, -- Aymeric. On 26 Nov 2018, at 16:10, Arthur Rio wrote: Hi all, I have been working on a 9 years old ticket that I'd like to close once and for all. The outstanding question is about the migration path to choose in order to update existing proxy model permissions. I have

Re: IRC Channel

2018-12-13 Thread Arthur Rio
Hi Avi, There are #django (for usage) and #django-dev (for contributing), both on irc.freenode.net, as mentioned here: https://docs.djangoproject.com/en/dev/internals/contributing/ Regards — Arthur On December 13, 2018 at 11:03:51 PM, Avi Garg (avi.grg4...@gmail.com) wrote: Does Django have

Migration strategy for proxy model permissions to use their own content type

2018-11-26 Thread Arthur Rio
Hi all, I have been working on a 9 years old ticket that I'd like to close once and for all. The outstanding question is about the migration path to choose in order to update existing proxy model permissions. I have explained three different approaches I can think of in the pull request:

Re: Content types shouldn't be created on post_migrate signal

2018-10-07 Thread Arthur Rio
right. Right now the auto-detector is a black box that deals with dependencies and model state deltas resolution." If now is the time to take a stab at it, I'd be happy to help as much as I can. Regards -- Arthur On Friday, October 5, 2018 at 10:28:06 AM UTC-7, Arthur Rio wrote: > >

Re: Content types shouldn't be created on post_migrate signal

2018-10-05 Thread Arthur Rio
which faces similar issues. Regards -- Arthur On October 5, 2018 at 9:30:58 AM, Arthur Rio (arthur.ri...@gmail.com) wrote: Hey Marcin, The problem is that data migration based on app layer (python objects, ie. Models and Managers here) will cause troubles after some time (when app is cha

Re: Content types shouldn't be created on post_migrate signal

2018-10-05 Thread Arthur Rio
Hey Marcin, The problem is that data migration based on app layer (python objects, ie. Models and Managers here) will cause troubles after some time (when app is changing). In the other words - you cannot rely on your app layer when doing database changes. You should never do that, especially for

Re: Content types shouldn't be created on post_migrate signal

2018-10-04 Thread Arthur Rio
BTW: RunPython() is another thing, which can break your migrations, and should not be used (especially not by Django internally), because it relies on the application layer. How else can you do a data migration? There is no `migrations.InsertIntoTable`, the only other way currently would be to