Re: should blank POST data fallback to use model field defaults?

2016-08-17 Thread Michael Foster
I believe Tom is right. The documentation is trivial but there is a need to raise an error or warning to the user when specifying required=False for boolean fields, as it is nonsensical. On Tuesday, August 16, 2016 at 12:52:06 AM UTC+1, Tom Christie wrote: > > It's not perfect but given that

Re: PEP 484 type hinting in Django

2016-08-17 Thread Tim Graham
The JetBrains announcement that they want to fund the project isn't a guarantee that it'll be implemented. The feature needs to go through the normal feature acceptance process, which as Markus said, might involve a DEP. Assuming the idea is accepted, my sense on timing would be to wait until

Re: PEP 484 type hinting in Django

2016-08-17 Thread ludovic coues
Dropping support for python 2.7 has been planned for some time. Django 1.11 will be the last one supporting python 2. The following release will be django 2 and will only support django 3.5+. See https://docs.djangoproject.com/en/dev/releases/1.11/ That's what Tim was talking about. You can

Re: django.core.mail.outbox and __all__

2016-08-17 Thread Tim Graham
I believe that would break things: >>> from django.core.mail import * AttributeError: module 'django.core.mail' has no attribute 'mailbox' On Wednesday, August 17, 2016 at 7:30:11 AM UTC-4, IL Ka wrote: > > Hello, > > ``django.core.mail`` package contains ``__all__`` with list of public >

Re: PEP 484 type hinting in Django

2016-08-17 Thread Daniel Moisset
Thanks for the replies, As I mentioned, I have already started implementation (and I'm willing to go through with it, having even some time from my work allocated to do it); I wasn't aware of the JetBrains plan (it's a nice plus, but I don't depend on it), and I'll probably do it as external

Re: should blank POST data fallback to use model field defaults?

2016-08-17 Thread Tim Graham
I completed the pull request to restore the fallback for empty data, except for CheckboxInput. If you have any input, please speak up. https://github.com/django/django/pull/7068 On Wednesday, August 17, 2016 at 7:40:56 AM UTC-4, Tim Graham wrote: > > I think there's a misunderstanding. As the

Re: PEP 484 type hinting in Django

2016-08-17 Thread Florian Apolloner
On Wednesday, August 17, 2016 at 11:06:47 AM UTC+2, dmoisset wrote: > > @Florian > Would you care to ellaborate? I couldn't find the post you mention > (although requests is one of the few 3rd party projects that have support > at the official typeshed repository,

Re: PEP 484 type hinting in Django

2016-08-17 Thread Daniel Moisset
Hi @Alex, I wasn't aware of the fellowship program, but I've been getting started to work at this and I already have some minimal things up I have a repo with type hints (currently just covering the HttpRequest object and other minor stuff) at https://github.com/machinalis/mypy-django ; I'm

Re: PEP 484 type hinting in Django

2016-08-17 Thread Florian Apolloner
I personally do not think that this is something belonging into Django itself -- at least not in the current state. The requests (I think) maintainers have a good blog post iirc on the current issues. On Wednesday, August 17, 2016 at 6:08:48 AM UTC+2, Alex Hill wrote: > > Hi all, > > I like the