Re: django-formtools is neglected/unmaintained

Hi Tim, In case there is lack of active maintainers for the project then you could add me to the list of maintainers. I do contribute to django eco system regularly. my github activities: github.com/auvipy And about moving to jazzband, I do take part in django-admin2 maintenance there with

django-formtools is neglected/unmaintained

Hi, django-formtools seems neglected. It's been several months since the release of Django 1.10 but a compatible version of formtools hasn't been released to PyPI. Personally, I don't know if it's important to maintain it as an "official project." An alternative could be to "donate" it to Jazz

Re: CSRF_COOKIE_HTTPONLY is misleading and not useful

Meanwhile, there's a ticket [0] asking to expand the documentation of the settings.CSRF_COOKIE_HTTPONLY. If this setting doesn't provide any value, then I figure we should remove the system check that suggests to enable it and deemphasize it in the documentation and/or remove it. Is there conse

Re: New to django

Hi there. you've reached the Django Developers list, the list we use for people who are working on Django itself. It sounds like you're interested in building things with Django; if so, we recommend starting with the tutorial: https://docs.djangoproject.com/en/1.10/intro/tutorial01/ Cheers, Philip

New to django

I am new to django. so can someone help me in getting started quickly. -- 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 stop receiving emails from it, send an email to dj

Re: Provide a simpler way to default runserver IP/port to 0.0.0.0:8000

I recon i use a single settings module that feeds from env vars for any project i touch myself, but I suggested adding a setting because that would leave the choice up to the user like it's currently the case in django projects (some people still rely on local_settings import or use several setting

Re: Provide a simpler way to default runserver IP/port to 0.0.0.0:8000

-1 on a setting for that. I'd be okay with a DJANGO_RUNSERVER_BINDHOST environment variable or similar. On Monday, November 28, 2016 at 3:10:06 PM UTC+1, is_null wrote: > > Perhaps we could override this default with a setting ? > -- You received this message because you are subscribed to the G

Re: #27485 new New feature Allow ALLOWED_HOSTS to accept an IP-range / wildcard

There is a non-development use case here, which is being able to accept the IP range for a subnet used in an EC2 VPC (used by load balancers for health checks). Sure, I could iterate through all the potential IPs and add them, divine a way

Re: Provide a simpler way to default runserver IP/port to 0.0.0.0:8000

Perhaps we could override this default with a setting ? -- 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 stop receiving emails from it, send an email to django-developers+

Re: Provide a simpler way to default runserver IP/port to 0.0.0.0:8000

On Monday 28 November 2016 15:48:21 emor...@mozilla.com wrote: > This was filed as https://code.djangoproject.com/ticket/27537 , but moving > here for discussion. > It seems all you need in the overridden runserver is: from (...)runserver import Command as BaseCommand class Command(BaseCommand):

Provide a simpler way to default runserver IP/port to 0.0.0.0:8000

This was filed as https://code.djangoproject.com/ticket/27537 , but moving here for discussion. We have the following use case: * An app uses a VM for the local development environment (eg via Vagrant). * It's required to be accessible from the VM host (either on it's own IP, or on localhost via