Re: ManyToManyField not generating ON DELETE CASCADE clauses on (default) through table

Hi Carlton, I'm sorry that your mail was left unanswered for so long. Generally, "is it a bug" questions are better suited to django-users than to this list. In particular, I believe this is not a bug: The behavior you see is Django's default way of defining foreign keys, and indeed, as you

Re: Feedback on Django Channels

> > > Well, in that case I would consider defining the consumer as a required, > but > keyword (and keyword-only in Python3) argument, specified in the end by > convention. Putting it between the channel and channel parameters is ugly > IMO. > > It would be easy enough to change all the docs and

Re: Feedback on Django Channels

On Saturday 02 April 2016 00:38:31 Andrew Godwin wrote: > On Fri, Apr 1, 2016 at 11:32 PM, Shai Berger wrote: > > Hi, > > > > Finally found the time to go through this discussion. > > > > The first note that comes to mind is: > > > > Although it has already been pointed out

Re: Feedback on Django Channels

On Fri, Apr 1, 2016 at 11:32 PM, Shai Berger wrote: > Hi, > > Finally found the time to go through this discussion. > > The first note that comes to mind is: > > Although it has already been pointed out more than once that positional > arguments cannot follow keyword

Re: Feedback on Django Channels

Hi, Finally found the time to go through this discussion. The first note that comes to mind is: Although it has already been pointed out more than once that positional arguments cannot follow keyword arguments, you both (Andrew and Vincent) keep giving examples such as # SYNTAX ERROR

Re: Value of tightening URLValidator/EmailValidator regular expressions?

-1 on less strict validation. Saying we need less strict validation because emails are usually confirmed by sending an email to it, is akin to saying urls are only valid if the url can be fetched. "Looks vaguely like a url" would not be enough for validation purposes. I believe we should strive

[ANNOUNCE] Django bugfix releases issued: 1.9.5 and 1.8.12

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2016/apr/01/bugfix-releases/ -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and

Re: A helpful ImportError for manage.py when Django isn't installed/available

An idea: Catch the exception; in the handler, try to simply "import django". If this works, reraise, if it fails, print helpful message. On Thursday 31 March 2016 20:15:05 Tim Graham wrote: > Ben Welsh (palewire) raised a proposal on a GitHub pull request [0]: > > I've seen newbies flounder