Re: django.channels: "async" for Django

It might be a better idea to set the task-pool and intersocket--async into two namespaces. It would become confused if we put them together under the "Channel". Like in Java, Channel is like a wrapped-socket, but here in django-channel, it also means a task queue. On 17 June 2015 at 23:40,

Re: django.channels: "async" for Django

Sorry, I haven't read the source code. But I basically read the doc. Thus in a multithreaded env, we will use Redis or something to implement the one to one chat function, am I right? Thus people might be confused with the different channels' definitions. On 16 June 2015 at 08:51, Andrew Godwin

Re: Proposing DEP 3 (JS tests and linting) for acceptance

On Monday, June 8, 2015 at 2:29:22 PM UTC-6, Carl Meyer wrote: > > After lots of great work by Trey Hunner on the draft implementation (and > review from Tim Graham, Aymeric Augustin, Tomasz Paczkowski, and James > Da Costa), I think DEP 3 is ready for acceptance. > > The latest draft of the

Re: Custom Model field, to_python() / from_db_value() and unittests...

Am 17.06.2015 um 16:48 schrieb charettes: I suggest you use the following pattern which also accounts for py2/3: ... This is stepping into the django-user@ territory so I suggest we move the discussion over there if the provided example doesn't match your needs but you are really just trying

Re: Custom Model field, to_python() / from_db_value() and unittests...

Hi Jens, I'm not sure I understand what you are trying to achieve but I assume you want to write a third-party field that supports both Django 1.7 and 1.8 without raising deprecating warnings? I suggest you use the following pattern which also accounts for py2/3: import django from django.db

Re: Password validation in Django revisited

This seems like a great example of something which can live as an external package, and you document how to use it with `AUTH_PASSWORD_VALIDATORS`. You could add a minimum entropy parameter as an option which can be passed in the dict. On 17 June 2015 at 03:38, Alex Becker

Re: Custom Model field, to_python() / from_db_value() and unittests...

Am 16.06.2015 um 18:43 schrieb Tim Graham: The doc about how to ignore warnings in tests is here: https://docs.djangoproject.com/en/dev/internals/contributing/writing-code/submitting-patches/#deprecating-a-feature Alternatively, you can temporarily remove these lines in runtests.py:

Re: Password validation in Django revisited

Hi Erik, I've done some work on pattern-based password validation in python, something intermediate in complexity between these validators and zxcvbn. The rough version is on github[1]. I was thinking of turning this into a password validator for django, one which would not be turned on by