As someone whose worked on various projects in different languages over the
last 15 years that heavily involved deciphering IP sent in headers to try
to determine the "real" IP address of a connection, I would urge caution
with anything around determining a "real IP". There is no standard in
+1 from me on DB defaults (constraints too). I've worked on many systems
where Django isn't the only place putting records into DBs and having DB
level defaults and constraints fixes a lot of common issues with that.
Currently I create an empty migrations to then add them in manually when
I also agree with raising a UnsupportedMediaType and having custom handlers
for 400, 415 is always useful IMO
On Saturday, 12 November 2022 at 12:24:45 UTC Adam Johnson wrote:
> I would have a slight preference for raising an UnsupportedMediaType as
>> well and letting that percolate to a 415
config.get is how python-decouple works which is what I use for config and
deployment settings.
On Tuesday, 1 November 2022 at 09:34:15 UTC f.apo...@gmail.com wrote:
> Right, that would work. I am wondering though if we want to go all in on a
> typed config object like that or in a first step
Hybrid sound the best way, with remote first as otherwise you are excluding
people who would need air travel that's not covered by someone else and can
be very expensive how and are thus increasing a carbon footprint for
something that really doesn't need it
On Thursday, 27 October 2022 at
I'd suggest the docs are updated with a warning relating to what's Uri's
found as it could be extremely important to someone and not highlighting it
would be misleading .
On Tuesday, 2 August 2022 at 16:31:33 UTC+1 Uri wrote:
> Hi,
>
> I created my own utility function:
>
>
>
> *from
