While I think Adam's right that adding one or two new settings
wouldn't be a problem, I do worry about the ongoing proliferation, and
it's a thing that I keep wanting to try to find the time to work on
but never actually succeed at.
Separate from the suggestion of a generic way to add headers on e
> Backwards compatibility is the bigger concern here.
I understand that, I believe there is always a way, because prior to 2008 when
I switched to Django, I was commiter on a PHP library group that not only had
the best code quality: but COMMITS to maintaining BC. Code that I have made
prior to
Hi,
But when you are making a governmental website for example: you need
actual identity.
Django makes it possible (I'd even say easy) to setup your forms /
models to enforce stricter requirements if you have to. We don't have to
treat these cases as the default. Backwards compatibility is t
> This may be true - not all people have first_name & last_name or want to use
> them online. But it's also convenient to be able to call a person by their
> first name, and also allow them to use their full name on the website.
I completely agree with you, for example on dating sites like speed
Opened an issue on the OWASP project, reporting the reasoning of the consensus
made on this mailing list as best as I could:
https://github.com/OWASP/CheatSheetSeries/issues/472
Please feel free to comment or request changes on the issue.
--
You received this message because you are subscribed
> Input validation is performed to ensure only properly formed data is entering
> the workflow in an information system, preventing malformed data from
> persisting in the database and triggering malfunction of various downstream
> components. Input validation should happen as early as possible
Hey Sam.
(“I” is a placeholder in what follows…)
What I’m missing here, personally, having read this thread, and the old-one is
motivating examples where I go "wow, yeah, that would really make my life
easier”.
I read it and think yeah maybe. I see a couple of positive comments from people
And I'm sorry if I offended Mister alert("pwnd") :)
--
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+unsu
Thanks for the comment Florian, it's just basic hygiene really, don't leave
open ports you don't need, never trust user inputs for characters they don't
need, and so on.
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django it
Hi Carlton,
Thanks for chipping in.
As a long time user of Django (I first stated with it back in 2006) from my
experience where is excels is in providing a full toolbox for building
things for the web. The most successful “third party” apps and library’s
tend to be very large editions of f
It definitely does. Thanks.
Jure
On 19/08/2020 14:03, Carlton Gibson wrote:
From the thread, I’d suggest collaboration with Curtis if the ideas are
similar enough.
Also from the thread: the idea seems to fit between include as we have it now,
and a custom tag.
Maybe that gap hasn’t been wid
>From the thread, I’d suggest collaboration with Curtis if the ideas are
>similar enough.
Also from the thread: the idea seems to fit between include as we have it now,
and a custom tag.
Maybe that gap hasn’t been wide enough to grasp sufficient interest?
I think the standard path for inclus
Hi Sam,
It seems that even your complete proposal with working code did not
receive any attention from the core developers at the time. It would
seem from that thread that Jonathan Slenders also made a similar
proposal / solution and it too was rejected. Well, his was at least
rejected - judg
Hi all.
Calendar Week 32 -- ending 09 August.
Triaged:
https://code.djangoproject.com/ticket/31864 -- Session data cannot be
decoded during the transition to Django 3.1. (Accepted)
https://code.djangoproject.com/ticket/31862 -- Add ArrayField for all
supported databases - not only postgres
14 matches
Mail list logo