Re: Ability to change LoginView inside custom AdminSite

Read documentation for customization. I hope you need to pass template parameter and form class. That's all. On Fri, May 15, 2020 at 7:44 PM Nikita Krokosh wrote: > Hello everyone. > > > There's a way to set your own AdminSite class as said in docs: > > >

Re: Proposal: Allow stopwords in slugs generated by ModelAdmin.prepopulated_fields

I very much prefer a slug "to-be-or-not-to-be-that-is-the-question" than "be-or-not-be-question" (which doesn't make sense). אורי u...@speedy.net On Wed, Apr 8, 2020 at 11:35 PM Andy Chosak wrote: > Automatic slug generation in ModelAdmin via prepopulated_fields >

Re: Proposal: Allow stopwords in slugs generated by ModelAdmin.prepopulated_fields

I'm in favor of the change. It seems to me that most slugs I see these days have stop words in them and they read better because of that. I don't think JavaScript warnings would be helpful. A release note is sufficient. Admin users still get a preview of the slug and can edit it if needed. On

Re: Proposal: django project name

Christian González - Wed, 13 May 2020 at 22:13:34 > TL;DR: Django has no (builtin/explicit) settings variable like > PROJECT_NAME. Should have. 4 of those were comments (i wish the project templates stopped doing that) 3 of those were env variables which a deployment can override with an actual

Re: Reverting Django 3.1. to Django 3.0.6 raises "binascii.Error: Incorrect padding".

Adam Johnson - Fri, 15 May 2020 at 17:53:21 > At least two of the major database servers that Django supports, PostgreSQL > and MySQL, provide zero downgrade-ability. It's too hard for them to do. while this is now officially true for both MariaDB and MySQL, until recentlyish it was possible to

Re: Proposal: Allow stopwords in slugs generated by ModelAdmin.prepopulated_fields

Does anyone else have an opinion on whether or not we should still be removing these stopwords? Hopefully someone more involved in i18n can weigh in. > I'm not sure if there are any i18n concerns here. In fact, ceasing this practice removes the impetus for the recurring issues being raised

Re: Proposal: django project name

Hi Adam, > > TL;DR: Django has no (builtin/explicit) settings variable like > PROJECT_NAME. Should have. > > > I can see how it would be useful in several situations. But in most > long-lived projects I've come across, the "project name" is different > to the website name (or names,

Re: Reverting Django 3.1. to Django 3.0.6 raises "binascii.Error: Incorrect padding".

Hi Uri Smooth upgrade-ability is hard. Smooth downgrade-ability is even harder. It also imposes a tax on development, and can slow the roll out of new features as they can need roll out over multiple versions. I agree both would be nice to have, but given the limited engineering resources for

Re: Signal on management command exception

Yo-Yo Ma, Typically I've edited manage.py to handle this use case: def main(): # ... try: execute_from_command_line(sys.argv) except Exception: # whatever raise This doesn't capture programmatic calls via call_command() . But in my experience that's rarely

Re: Signal on management command exception

Hi Yo-Yo Ma, A subset of your use case should be handled by https://code.djangoproject.com/ticket/21429 -- BaseCommand should use logging instead of custom output wrappers. I’m actively working on it and hope to have it ready for Django 3.2. It allows configuring the reporting of exceptions for

Signal on management command exception

Request exceptions have always been easy to manage, because you can use middleware, and there is the built-in signal: https://docs.djangoproject.com/en/3.0/ref/signals/#got-request-exception Problem: However, if you want to send data to e.g., Sentry or perform some other action (logging,

Ability to change LoginView inside custom AdminSite

Hello everyone. There's a way to set your own AdminSite class as said in docs: https://docs.djangoproject.com/en/3.0/ref/contrib/admin/#overriding-the-default-admin-site But I also want to change login view behavior. I want to replace *LoginView* in

Re: Proposal: django project name

thank you for reply Virus-free. www.avast.com <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Wed, May

Reverting Django 3.1. to Django 3.0.6 raises "binascii.Error: Incorrect padding".

Hi, I submitted this ticket today and it was closed: https://code.djangoproject.com/ticket/31592 I think Django should handle downgrading versions without raising exceptions. If objects (such as sessions) are invalid because of downgrading, they should be deleted automatically. It may happen

Re: Django Version 3.2 Roadmap

OK, thanks thus far all. I've bumped the final release date to April 6 2021. (I left the other dates as were: a handful of extra days over the weekend there will be a nice to have when they arrive :) C. -- You received this message because you are subscribed to the Google Groups "Django