Re: structural & functional review of django documentation

The written quality of the Django docs has been a selling point for years, but discoverability has never been great. I wanted to add two notes: 1) The front page of the docs says docs are organized into four sections (Tutorials, Topic Guides, Reference Guides, How-To Guides). And it's been

Re: structural & functional review of django documentation

Hi Ned -- That is an excellent point! There was some back-and-forth about bread crumbs. It would be awesome if we not only implemented that, but used it to track user's progress through the docs, and collect this info. Thanks, -- You received this message because you are subscribed to the

Re: structural & functional review of django documentation

Hello Aymeric -- Yes indeed, I misunderstood. Thank you for lining things out for me. Loosely, the group I am talking about is the group of a couple thousand who completed that survey in the first 48 hours. It would be great to know why a lot of those ~2000 folks feel so stongly and

Re: structural & functional review of django documentation

Hello Aymeric -- Yes indeed, I misunderstood. Thank you for lining things out for me. Loosely, the group I am talking about is the group of a couple thousand who completed that survey in the first 48 hours. It would be great to know why a lot of those ~2000 folks feel so stongly and

Support for auto fields can be set by database triggers or default column values instead of django

Hi, I'm trying to add support for auto-fields to django. By auto-fields, I mean fields that django skips during INSERT or UPDATE and let's the database assign a value. I'm using an existing ticket to track this: https://code.djangoproject.com/ticket/21454#comment:21 A working PR is present at:

URL dispatching framework: feedback requested

A quick question: Aymeric suggested to merge django.conf.urls into django.urls as well. Does anyone think we should not make this move? If no one disagrees, I will proceed with a new PR to make the move. -- You received this message because you are subscribed to the Google Groups "Django

Re: argon2 PasswordHasher

Hynek weighted in[1]. I think the PR is ready to merge. Best wishes, Bas [1] https://github.com/django/django/pull/5876#issuecomment-168411156 > On 27 Dec 2015, at 13:39, Florian Apolloner wrote: > > I do not see anything wrong in the PR and there is probably no