Re: Adding aggregates to ModelAdmin.list_display

Can we agree on the suggested design? Or does anyone think it needs to be incorporated into *list_display*? On Wednesday, September 21, 2016 at 7:43:06 PM UTC+3, dor wrote: > > I recently suggested adding a *list_aggregates* member to ModelAdmin, > along with a patch to match: >

Re: is_valid as property

Hi Sven, On Thursday 29 September 2016 22:09:27 Sven R. Kunze wrote: > > Am Donnerstag, 29. September 2016 20:26:54 UTC+2 schrieb Aymeric Augustin: > > > Generally speaking, properties are expected to be cheap and methods can be > > expensive. In my opinion, for lack of a better guideline, we

Feature suggestion: Option to suppress system checks in commands

Hi everyone, I'd suggest an options for all commands to suppress a defined system checks when running a command. I know it is possible to defined SILENCED_SYSTEM_CHECKS in settings, but that has impact of everything including the check command itself. My point is to suppress system checks

Re: Feature suggestion: Option to suppress system checks in commands

Hi, wouldn't it be easier to create special settings for cron? Something like that: # myprj/settings/cron.py from myprj.settings import * SILENCED_SYSTEM_CHECKS = ... And in cron: ... python manage.py --settings=myprj.settings.cron > On 30 Sep 2016, at 11:31, Vlastimil Zíma

Re: is_valid as property

Hi everybody, On Fri, Sep 30, 2016 at 09:04:32AM +0300, Shai Berger wrote: > Hi Sven, > > On Thursday 29 September 2016 22:09:27 Sven R. Kunze wrote: > > > > Am Donnerstag, 29. September 2016 20:26:54 UTC+2 schrieb Aymeric Augustin: > > > > > Generally speaking, properties are expected to be

Re: Challenge teaching Django to beginners: urls.py

I also prefer URLs all concentrated in a single place, instead of spread out all over the codebase. The reason is that it is dead simple to track which view is associated with a URL, just look at the ROOT_URLCONF file and track the view following the patterns. If you have them spread out, you'll

Re: Feature suggestion: Option to suppress system checks in commands

Hi, You could add the setting through and env variable and obtain that variable inside the settings file with SILENCED_SYSTEM_CHECKS = bool(os.environ.get("SILENCED_SYSTEM_CHEKS", false)) On Fri, Sep 30, 2016 at 11:31 AM Vlastimil Zíma wrote: > Hi everyone, > > I'd suggest

Re: Form.Media: render inline css/js

On Thursday, September 29, 2016 at 4:11:04 PM UTC+2, is_null wrote: > > Thanks for the heads up, a similar ticket has been closed as wontfix, > because it isn't compatible with CSP: > https://code.djangoproject.com/ticket/13978 > > While I'm all against inline scripts, I have a use case which

Re: Autocomplete in Django 1.11: Widget in Forms Library?

Hi, "it could be possible to provide such a widget in contrib.admin". The current PR provides a django.contrib.admin.widgets.AutocompleteSelect widget. Does that work? You could subclass it to use a different URL instead of the built-in admin:autocomplete url if needed. My one worry is that if

Re: Autocomplete in Django 1.11: Widget in Forms Library?

I was thinking about a similar issue when looking at Curtis's patch for an admin HStoreField widget [0]. It doesn't seem so nice to give contrib.postgres special treatment in the admin. Rather, I think the admin should have a hook to register custom widgets for arbitrary fields. If it provided

Re: Adding support for importing models through the app registry while it is loading

Hello, Quick follow-up: I just updated my PR according to this discussion: https://github.com/django/django/pull/6547 While I was there, I made get_user_model() usable at import time. We’ll need feedback from actual projects to know it that works. -- Aymeric. -- You received this message