So I read the entire thread so far, and I saw some miscommunication induced
hostility. I wasn't sure what was miscommunicated, just progressively more
sure with each post that `something` had been miscommunicated.
So I read the ticket... and I can see why it was rejected.
Without at least some g
On Sun, Dec 27, 2015 at 7:53 AM, Samuel Bishop wrote:
> Once again I have to thank you for taking the time to keep replying. These
> longer explanations are proving very helpful (at least to me) in
> understanding Django Channels. :-)
>
> I definitely understand the compatibility reasons, I'm als
I do not see anything wrong in the PR and there is probably no reason not
to include it. It would be great if you could get feedback from dstufft
and/or hynek in #cryptography-dev -- not that we miss something.
Cheers,
Florian
On Sunday, December 27, 2015 at 12:36:02 AM UTC+1, Bas Westerbaan wr
By default, when you create a formset from a model, the formset will use a
queryset that includes all objects in the model (e.g., Author.objects.all()
).
In most use cases, people will want to use a specific subset of data and
will construct queryset by hand. Or they want to use an empty querys
Hi Doug,
I get lost regularly in Django's docs as well, so you are not alone there.
I think it is a good proposal to add:
"find what you were looking for" or "was this page helpful" or "rate this
page on its organization, clarity, brevity, etc." data on every single
existing page of the docum
My main concern is that it will be non-trivial to setup that type of
feedback system, and I'm not sure how we would go about turning that type
of data into actionable tickets. If anyone has experience with such a
system, I'd be interested to hear about it.
On Sunday, December 27, 2015 at 10:19:
Again, I am sorry if my comments have ruffled anyone's feathers. I am not
going to argue. My sole intent is a positive one. And, indeed, I am
humbled by the ongoing work of this community over a period of time that I,
until now, have not been involved.
I beleive, it is my impression, that be
Adding a survey link is not difficult. We conducted a community survey [1]
earlier this year with one question related to documentation, "What parts
of the Django documentation do you find most useful?" What questions to ask
and how to turn the answers into actionable items is the part I'm not s
On Sun, Dec 27, 2015 at 11:00 PM, Wim Feijen wrote:
> By default, when you create a formset from a model, the formset will use a
> queryset that includes all objects in the model (e.g.,
> Author.objects.all()).
>
> In most use cases, people will want to use a specific subset of data and
> will co
Tim --
Thank you so much for the link to that blog post. I am going away now to
think about that data a little, but I'll be back.
I was not aware of the "topics", "reference", and "how-to" assortment. But
I have scanned the Table of Contents, and I find almost nothing here
addressing documen
On Tuesday, December 22, 2015 at 1:20:23 AM UTC+2, Shai Berger wrote:
>
> > We could add a documented API to check wanted models for foreign key
> > constraint violations (.check_constraints(Model1, Model2) would be a
> > likely API). Then lets just document that depending on the database
> > th
11 matches
Mail list logo
