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

Hello Arthur, I agree that option 1 is the way to go. It would be nice to make the migration reversible. If someone upgrades to Django 2.2.x, migrates the database, and later discovers a blocking issue, they should have the option to migrate backwards and downgrade to 2.1.y. Best regards, --

Re: Simplify authentication backend interface

Hello Tobias, And sorry for the late answer! Yes, this is a good idea. https://docs.djangoproject.com/en/2.1/topics/auth/customizing/#handling-authorization-in-custom-backends reads

Re: Ticket 2273: django.contrib.auth.models.User: username is case-sensitive

The "local part" of the email address is the username. But I know not all websites who use Django provide email services. Probably most of them don't. אורי u...@speedy.net On Sat, Jan 5, 2019 at 11:57 PM Nicolas Le Manchet wrote: > As Kye Russell mentioned, email addresses being case-sensitive

Re: New optional settings - disable bulk_create in all managers and call self.full_clean() before saving the models

Thank you, Aymeric. I appreciate your feedback. אורי u...@speedy.net On Sun, Jan 6, 2019 at 12:24 AM Aymeric Augustin < aymeric.augus...@polytechnique.org> wrote: > Hello, > > Your ValidateModelMixin and ManagerMixin look perfectly reasonable. You > wanted to customize two aspects of Django's

Re: BitBounce Spam Replies From the Mailing List

On Sun, 6 Jan 2019 11:11:38 +0100 Aymeric Augustin wrote: > I was pessimistic; it seems that a BitBounce employee might read this > message. > Last week, Adam twitted at BitBounce about this, and I retweeted with a comment. This week a person presenting themselves as a BitBounce employee said

Re: BitBounce Spam Replies From the Mailing List

I've got same replies from bitbounse too. :/ On Sun, Jan 6, 2019, 3:11 PM Aymeric Augustin < aymeric.augus...@polytechnique.org wrote: > I was pessimistic; it seems that a BitBounce employee might read this > message. > > So, BitBounce, if you’re reading this: > > 1. Please drop

Re: BitBounce Spam Replies From the Mailing List

I was pessimistic; it seems that a BitBounce employee might read this message. So, BitBounce, if you’re reading this: 1. Please drop aphiso...@gmail.com from your service before they do more harm to your reputation — there are thousands of subscribers to this mailing list — and until they

Re: BitBounce Spam Replies From the Mailing List

On Sun, Jan 6, 2019, Aymeric Augustin wrote: >[[ I'm adding BitBounce support to this discussion, even though I expect >I'll just get one more of their spam -- "we'll ignore the spam problem we >cause to you until you pay money to us". ]] >Here's one possible solution: > >- we export the

Re: BitBounce Spam Replies From the Mailing List

[[ I'm adding BitBounce support to this discussion, even though I expect I'll just get one more of their spam — "we'll ignore the spam problem we cause to you until you pay money to us". ]] > On 2 Jan 2019, at 01:39, Daniele Procida wrote: > > On Wed, Jan 2, 2019, Daniele Procida wrote: >