Re: Consider making asgi_rabbitmq an official Django project.

Hi Artem, Thanks for adding the comments - it does look better. The thing I would like to have is more feedback from Django core about this; I've not heard anyone's opinion but mine, and I am not entirely sure if we should do this (I am also not entirely sure asgi_ipc should be a Django project so

Re: On ASGI...

On Mon, Jun 12, 2017 at 10:53 PM, Tom Christie wrote: > > def handler(channel_layer, channel_name, message): > > Oh great! That's not a million miles away from what I'm working towards on > my side. > Are you planning to eventually introduce something like that as part of > the ASGI spec? > I ha

Re: Makemigrations hooks for third-party apps?

Can you provide the operations that users can then import into their migrations, similarly to how contrib.postgres provides the HStoreExtension operation [0]? The import could even be a function taking the extended model that returns the appropriate operation. This might be a bit more lo-fi tha

Re: DEP201 / Simplified URL routing progress report

For those who don't know, the PR is here: https://github.com/ django/django/pull/7482 > However, in doing so I "had" to get rid of a minor performance > optimisation: the caching of `.regex` using LocaleRegexDescriptor, so there > might be a performance drawback in case one does not use the > laz

Re: Should contrib.auth include support for 2fa out of the box?

I would like to explain a potential solution I have been working on (See commit https://github.com/mlevental/django/commit/51dbaa6748076e06d91b361c2fa60ecf24f5c27e

Re: Should contrib.auth include support for 2fa out of the box?

I would like to explain a potential solution I have been working on (See commit https://github.com/mlevental/django/tree/ticket_25612). I think it's not complete but I don't have the time to continue working on it. *Overview:* - In order to check if a user is authenticated with one or two fa

Re: Why doesn't the framework provide support for translated database content?

Hi Bernhard, fyi: a similar topic was recently discussed here[0]. My point of view: I recently counted 19 packages for this purpose, six of them being actively maintained. You already mentioned that there are two ways that you can design the database layout (I argue there are three, but thats ni

Re: Why doesn't the framework provide support for translated database content?

80% covered by two approaches that aren't really compatible with each other doesn't get there :) Again: to get into Django, something really needs to be as close as possible to "one size fits all", not "one size fits some, another size fits some more". -- You received this message because you ar

Re: Why doesn't the framework provide support for translated database content?

The question is how we guess that it fits 80% of all use cases :) IMHO 80% are covered with the two approaches that I listed in the first mail. I mean you reach the limits of the ORM pretty quickly as well but you can always drop down to raw Sql and circumvent the built in API restrictions On 06

Re: Why doesn't the framework provide support for translated database content?

Generally, I'd like to see something satisfying the needs of around 80% of use cases out of the box before including it directly in Django. No database-translation tool I'm aware of is even close to that level. -- You received this message because you are subscribed to the Google Groups "Django

Re: Why doesn't the framework provide support for translated database content?

Why not build in the most common approach while still allowing people to override it like they do know? They could simply swap out the default manager right? On 06/13/2017 06:54 PM, James Bennett wrote: > Because even if you collapse the number of approaches to just two general > options, there's

Re: Why doesn't the framework provide support for translated database content?

Because even if you collapse the number of approaches to just two general options, there's still enough variability in the specifics of how to implement those options that there's no clear "one size fits all" solution at the moment. If there ever is one, it can be considered for inclusion in Django

Why doesn't the framework provide support for translated database content?

Hi guys, I'm running a "hobby" website with translations for roughly 83 languages and I've taken a thorough look at the available options (as in: Django apps): * django-modeltranslation: probably a bad idea to create 83 columns for each translated string * django-hvad: never got this to work *