Re: Ideas for a new DEP on long-term Django API compatibility

Hello Luke, thanks for your comments, mine are below On Thursday, August 1, 2019 at 10:34:22 AM UTC+2, Luke Plant wrote: > > Hi Pascal, > > I know this is a very late reply, but there have been some things going > round my head that I thought I should get down. > > *First,* some positive changes

Re: Discussing improvements of django.setup()

Hello, any news about this issue? Concerning the thread-safety of setup(), the PR is here - https://github.com/django/django/pull/11440 Concerning the tweakability of setup(), I don't get your argument Aymeric: "*One more or one less monkey patch isn't going to make a difference to these pro

Re: Ideas for a new DEP on long-term Django API compatibility

Pascal, you can read about the reason for the action actions change on the ticket https://code.djangoproject.com/ticket/29917 ...and on this mailing list... https://groups.google.com/d/topic/django-developers/-OWoYL_zryM/discussion. I hesitate to link to things like that in the release notes be

Ignoring accept_language in localization middleware based on prefixed URL patterns

Hi guys! I’m Janez Kranjc, I’ve been using Django for a bit now - since 1.3 and I’ve recently come across and issue that’s been bothering me in multiple projects that I’m working on. Localization middleware ignores the accept language header if ANY url pattern exists that is i18n prefixed regar

retriving all table from database

can anyone help me to pull all table name(schema wise ) from database into a dropdown. it will be best if someone give codesnippits or examples , how to do?? -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group

Display labels for autocomplete fields

At present the admin autocomplete docs mention `ModelAdmin.autocomplete_fields` and `ModelAdmin.search_fields` which are used to configure select2. There are also options for overriding the queryset used. However there seems to be no way of specifyng what is shown in the autocomplete... it just

Make Development More Accessible

I'd like to propose moving Django issues to github and make a real decision on it here in this thread. If there has been a recent discussion on this I apologize, but searching for issue tracking / github links to about every thread ever posted here. I believe this would lower the barrier to ent

Re: Ignoring accept_language in localization middleware based on prefixed URL patterns

Hello, Yes, I think this change makes sense, assuming no unexpected difficulties arise in the implementation. Best regards, -- Aymeric. > On 6 Aug 2019, at 10:58, Janez Kranjc wrote: > > Hi guys! I’m Janez Kranjc, I’ve been using Django for a bit now - since 1.3 > and I’ve recently come