python path in that
case? Is this assumption even correct? I could not find anything about
it in the docs.
In any case, I think the docs need an update because currently, all
examples use `django-admin`, which does not work out of the box in my
experience.
thanks,
tobias
--
You received this
allows you to set a priority list of languages to fall back to³.
Tobias
¹ https://docs.python.org/3/library/gettext.html
² https://docs.python.org/3/library/gettext.html#gettext.GNUTranslations
³ https://www.gnu.org/software/gettext/manual/gettext.html#The-LANGUAGE-variable
--
Tobias K
Thank you Barhamou for raising the question here and starting the
discussion.
I agree with Adrian that this feels like a pretty niche use case.
Depending on the needs, other possible implementations might include:
4. A form field mapping to multiple model fields
5. A custom queryset/manager that
At Florian's suggestion in another thread, I propose that we move further
discussion of the settings refactor to the forum:
https://forum.djangoproject.com/t/settings-refactor/17352
On Wednesday, November 2, 2022 at 2:58:29 PM UTC-4 f.apo...@gmail.com wrote:
> The speckenv example highlights t
..
Cheers,
Tobias
--
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+unsubscr...@googlegrou
o those lists...)
Cheers,
*Tobias McNulty*Chief Executive Officer
tob...@caktusgroup.com
www.caktusgroup.com
On Mon, Nov 28, 2022 at 9:05 AM Carlton Gibson
wrote:
> Hey Roger,
>
> Indeed it does. You can set up Email Mode (that may not be the actual
> name) and it’ll work just like a mai
ould be a Roadmap drawn from the
> historical discussion.)
> Once (if) that gets to the point where it clearly addresses the 90% of
> needs, then there's a case for adding it to core. I don't think we can just
> push forward given that nothing changed in the last few years.
>
said it still supplies an
easily searchable answer for "Django DATABASE_URL."
Cheers,
Tobias
On Sun, Nov 27, 2022, 2:40 PM Raphael G wrote:
> Some base industry background. It's a pretty common convention to share
> credentials in environment variables. For many Paa
djangoproject.com/en/4.1/intro/tutorial01/
Cheers,
Tobias
On Sat, Oct 29, 2022, 7:15 PM Peter Baumgartner
wrote:
>
>
> On Sat, Oct 29, 2022 at 10:06 AM Peter Baumgartner
> wrote:
>
>> Thanks for the thorough review Florian! Some comments inline...
>>
>> On Wed, Oct
Hi,
I also may be missing some context, but is this the mentioned package?
https://github.com/waveaccounting/dj-inmemorystorage
I have not used it, but it looks like a useful tool to have!
Tobias
On Thu, Oct 20, 2022 at 7:50 PM David Sanders
wrote:
> Hi,
>
> I may be missing som
Hi Yonas,
Thanks for sharing this list. Even so, in my opinion, this feature lives
best outside of Django where it can be appropriately customized as needed
for a given project.
I hope this helps.
Best,
Tobias
On Wed, May 11, 2022, 6:46 PM Yonas
wrote:
>
> Would syncing the block lis
do this for the community.
Can you provide some examples? I support the general idea, but having
some concrete APIs to discuss might be helpful.
thanks
tobias
--
You received this message because you are subscribed to the Google Groups "Django
developers (Contributions to Django i
s myself. Personally I think I prefer the orderliness of nesting
everything under a single Python package that is the project name, but I'm
not sure how to do that and solve the "two folders with the same name"
problem. In any event, I support whatever the consensus is.
Cheers,
Tobi
ally the weird "half
authenticated" state.
- Different protocols need different UI (e.g. "enter a 6-digit code" for
OTP or "activate your token" for WebAuthn).
thanks
tobias
--
You received this message because you are subscribed to the Google Groups "Django
ot widely used yet.
Is it possible to start some kind of poll? Options could include:
- "I already use 2FA with django, using the library …"
- "I already use 2FA with django, using custom code"
- "I do not use 2FA with django yet, but I would like to"
- &
Hi Jacob,
I actually do like that idea! I don't think it is a good default for
django in general, but I would be interested in a reusable app that
implements this. Is this already available somehwere?
thanks,
tobias
On 05/04/2022 16.04, Jacob Rief wrote:
How about this proposal?
So
clearly a good thing. But I still think this works better in a third
party app such as django-mfa3.
best,
tobias
On 07/04/2022 14.42, Yonas wrote:
Hello,
The idea to implement MFA (2FA) has been brought up a couple of times
over the past years. And the community seems interested.
I am willing
ponse cycle for the view being cached.
(But that's a bigger ask, because there's less existing infrastructure to pass
down a changed key function – I'd be pretty happy with just a dynamic prefix.)
Best,
Tobias
--
Tobias Kunze / rixx (er/he)
--
You received this message because yo
bit. Why are
session cookies not treated as sensitive, just like passwords are?
thanks,
tobias
[1]: https://code.djangoproject.com/ticket/29714
--
You received this message because you are subscribed to the Google Groups "Django
developers (Contributions to Django itself)"
attrs={'type': 'date'}`.
Another thing to be aware of: The native date picker UI uses the
system/browser locale, not the one that is used on the page. (See also
https://bugs.chromium.org/p/chromium/issues/detail?id=263320)
Hope that helps
tobias
--
You received this message
to a very popular browser this might lower
the threshold for testing even further.
tobias
--
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 ema
Here's the incident report from Fastly:
https://status.fastly.com/incidents/vpk0ssybt3bj
*Tobias McNulty*Chief Executive Officer
tob...@caktusgroup.com
www.caktusgroup.com
On Tue, Jun 8, 2021 at 9:58 AM danushka padrushka
wrote:
> Hi Wadinga Leonard,
>
> I checked from diff
his is possible as a third party
library. I am still not sure how much interest there actually is though.
tobias
PS: There is a small typo in the first link in your blog post.
On 15/03/2021 04.49, schinckel wrote:
Hi Tobias.
I've done a bit of stuff on this, and found there were actually l
with QuerySet/Query.
thanks
tobias
--
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-developer
ne of them, but at this point
that is probably too drastic.
tobias
--
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
. The last commit to
staff_member_required was 2015. It was documented shortly after that.
So it seems like the documentation is up to date with the code.
On 09/03/2021 14.50, Carlton Gibson wrote:
Hi.
On 9 Mar 2021, at 14:33, Tobias Bengfort <mailto:tobias.bengf...@posteo.de>> wrote
e calling the admin site's get_permission
method and using the admin login page rather than the default auth one:
According to [0] staff_member_required also uses the admin login page by
default. That contradicts both your answers, doesn't it? Now I am more
confused than before.
that
staff_member_required is more low-level and I should use
AdminSite.admin_view in most cases. Is that correct?
I will try to make a pull request to add the answer to the documentation.
thanks
tobias
[0]:
https://docs.djangoproject.com/en/3.1/ref/contrib/admin/#django.contrib.admin.ModelAdmin.get_ur
3.4.
https://docs.python.org/3/library/unittest.html?highlight=unittest#distinguishing-test-iterations-using-subtests
tobias
--
You received this message because you are subscribed to the Google Groups "Django
developers (Contributions to Django itself)" group.
To unsubscribe from this gro
> Here is a great explanation of this exact issue, cleared it up for me:
> https://blog.jooq.org/2018/07/13/how-sql-distinct-and-order-by-are-related/
>
>
>
> On 28.10.2020., at 20:04, Tobias McNulty wrote:
>
>
> Hi all,
>
> Starting a thread on ticket #28560
> <
order_by() as-is, or not add "name" to the SELECT
in this case either?
>>> str(School.objects.values("county").order_by("name").distinct().query)
'SELECT DISTINCT "testapp_school"."county", "testapp_school"."name"
aise an
error if the list of columns in values() is insufficient to run the
requested query (i.e., never add a column implicitly if the user specified
a list of columns via values() or values_list()).
What do others think? What are other potential fixes I'm not thinking of?
Cheers,
Thanks for the report. The SPF record was updated today around 1:30pm EDT.
Please let us know if you continue to see issues.
On Thu, Oct 22, 2020 at 12:10 PM Adam Johnson wrote:
> Perhaps there's a task for the ops team to check the SPF/DKIM/DMARC
> records for djangoproject.com ?
>
> On Thu,
en as someone who does not self-identify as a Redis enthusiast.
*Tobias McNulty*Chief Executive Officer
tob...@caktusgroup.com
www.caktusgroup.com
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" g
hacky and not intended.
Tobias
--
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+unsubscr.
;you have to commit for 9 months" is a tad
big. I keep wondering if we can do something to improve the options in
between those. One idea would be to formalize an "a11y" keyword so
interested contributors can easily find related tickets.
tobias
--
You received this message because
you should inspect the
created migration BEFORE running `manage.py migrate` to ensure it does what
you expect. Press Y to continue or N to cancel." (needs copyediting of
course)
It would be easy enough to bypass with --no-input if someone doesn't want
the interruption.
Cheers,
*Tob
completely agree personally. Also note that many national regulations
are based on WCAG. So this question seems to be answered.
tobias
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from
s good to me, especially since it's easy to keep the default behaviour
*and* provide the new flexible behaviour. I'd definitely be more willing to
use `timesince` instead of my cobbled up solutions if it had the behaviour you
suggest.
Tobias
--
You received this message because you are su
more Pythonic, probably would not stick out so well / not be as easy to
search for. :D
Tobias
On Sat, May 9, 2020, 12:41 PM Tim Allen wrote:
> I'm tentatively +1 on this change... but...
>
> While it may be a straightforward operation to do a case sensitive search
> and replace in
itical part in my experience is to convince people that this
should be included in django itself rather than a third party library. I
usually fail with that so I cannot say anything useful about that.
tobias
--
You received this message because you are subscribed to the Google Groups
"Django
On 14/03/2020 09.43, Tobias Bengfort wrote:
> Another option could be to add system checks for this: Instead of
> silently "fixing" missing code it would inform developers about missing
> decorators/mixins. (If I have time I might try to come up with a
> prototype of this.)
ssing code it would inform developers about missing
decorators/mixins. (If I have time I might try to come up with a
prototype of this.)
tobias
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To u
s also a major/breaking modification. Adding a
sidebar, especially with an option to disable it, won't hurt in upgrades
generally, but losing/changing home page functionality would be painful.
Tobias
--
You received this message because you are subscribed to the Google Groups
"Djan
n.
Please remember that we are all volunteers, and rely on the work of fellow
volunteers (like you!) to make Django the best that it can be. Thank you
for following up about this issue, and good luck in tracking down a fix!
Best,
Tobias
On Sat, Nov 23, 2019, 11:25 PM אורי wrote:
> Hi,
>
&
e updated; i.e., it's simply a matter of timing that it
happened to break with Django 2.2.
There is some sample code in the ticket which might be good to try, to see
if it fixes the issue for you:
https://code.djangoproject.com/ticket/30439#comment:7
Cheers,
*Tobias McNulty*Chief
econd options as I believe it allows to have
cleaner application designs. But it think it is hard to get the right
balance.
tobias
On 05/11/2019 12:03, Tom Clark wrote:
> I'd be very interested in this. But it seems like one helluva lot of work,
> to enable people to customise their Gro
On Wed, Oct 30, 2019 at 12:29 PM Carlton Gibson
wrote:
> That _highly recommend_ sentence could go:
>
> > We highly recommend and only officially support the latest point release
> of each support Python series.
>
👏 Love it! (though perhaps drop or edit the second "sup
*, but I'm still not entirely sure about that. (The
other possibility being that that language is a holdover from the time when
we were supporting both Python 2 and 3.)
Cheers,
*Tobias McNulty*Chief Executive Officer
tob...@caktusgroup.com
www.caktusgroup.com
On Wed, Oct 30, 2019 at 10:56
efforts on the really valid ones. And if all the open
ones are valid, I see no advantage to closing them.
Best regards,
Tobias
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from t
I think it's a great idea.
On Thu, Jul 18, 2019, 12:46 PM Jacob Kaplan-Moss wrote:
> Hi folks -
>
> I’d like to gauge interest in adopting dj-database-url
> (http://github.com/jacobian/dj-database-url) as an official project
> (
> https://github.com/django/deps/blob/master/final/0007-official-pr
Hello,
This mailing list is for development. You are probably searching for the
list for users to ask questions: django-us...@googlegroups.com
Alternatively you might ask your question on freenode irc in the channel
#django
--
Tobias Wiese
PGP KEY: https://tobiaswiese.com/pgp.asc
PGP FPR
rsion, and/or keeping backwards compatibility.
You're mentioning `asgiref` a lot – do you expect it to become a
dependency of Django? Do you expect any other new dependencies to be
introduced?
Thank you again for your work (and making it through this “light reading”)
Tobias
--
Yo
for the introduction of
template-based form rendering, which has been part of Django for some
time now.) Adding a comment that the issue still persists currently (and
linking to the tested commit for reference) can be helpful to show that
an 8 year old bug is still relevant.
I hope this helps,
ad lawyers go over that…
>
This is great. Is there someone from the DSF on this list who would be
willing to consult with a DSF attorney to see if language like this (and no
signature requirement) would work?
Tobias
--
You received this message because you are subscribed to the Google Grou
I'd be happy to try setting something up, but a quick search didn't turn up
any obvious choices.
In the absence of information to the contrary, I'd hazard a guess that we
still need the CLAs...
Tobias
On Sat, Apr 27, 2019, 1:26 PM Carlton Gibson
wrote:
>
> On 27 Apr 20
already, or cluttering an
ongoing discussion with a lot of "+1", so there is no way to know who is
nodding along with which arguments.
Tobias
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" gro
, IMO). I do feel there's a pragmatic solution in here
somewhere.
Best to all,
Tobias
*Tobias McNulty*Chief Executive Officer
tob...@caktusgroup.com
www.caktusgroup.com
On Fri, Apr 19, 2019 at 8:52 AM Tim Graham wrote:
> I'm sorry for establishing some (foolish?) guidelines t
ps via add/remove? I'm not sure if "forced validation …
on some cases" wouldn't be even more confusing in those tricky cases.
Tobias
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" g
lack would have on the Django
code base and the Django development process – educating our
contributors cannot be a primary concern, compared to making
contributions as easy as possible.
Tobias
--
You received this message because you are subscribed to the Google Groups
"Django developer
re introduces warning fatigue, which Django
so far does a good job of avoiding).
Tobias
--
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
-step
form wizard).
Cheers,
Tobias
On Tue, Apr 16, 2019, 8:34 PM Will Gordon wrote:
> In the same way that editable fields are forced to not be included in a
> ModelForm (
> https://github.com/django/django/blob/master/django/forms/models.py#L146),
> I would like to propose that &qu
wrapping,
etc. in comments and docstrings. (Again, as of mid-2018 there is
the max-doc-length option for flake8 that could help with this somewhat,
but that change can be made independently.)
I'm not arguing against Black adoption, but I don't think it's going to
eliminate from the revie
ngth kept at 119, no string normalization:
> https://github.com/hermansc/django/pull/2
Apologies, somehow I missed these links on the first read. Go here for an
overview of lines changed, don't use my numbers. :-)
Tobias
--
You received this message because you are subscribed to the Googl
on't pass our own tests...
In any case, while this sounds like a non-trivial project with some
questions to work through yet, I too like not having to worry about code
formatting and don't have any real objections to this.
Cheers,
*Tobias McNulty*Chief Executive Officer
tob...@caktusgro
s own domain may actually be saving us a
good bit of bandwidth (previously each subdomain had its own /s/ prefix
from which an identical set of static files was served).
Cheers,
*Tobias McNulty*Chief Executive Officer
tob...@caktusgroup.com
www.caktusgroup.com
On Sun, Mar 31, 2019 at 3:08 PM T
the original
ticket that got this started). If that's correct, that seems fair to me
(and worth keeping this check), along with an update to the docs to clarify
this dependency and why it exists.
Tobias
On Tue, Apr 9, 2019, 8:06 AM Adam Johnson wrote:
> Other ideas:
>
>- Bypas
quot;) could be modified to clarify this
reasoning and its relationship to LANGUAGES? (What exactly this would say
is not obvious to me at the moment...)
Tobias
On Tue, Apr 9, 2019, 7:28 AM Adam Johnson wrote:
> Hi Matthias,
>
> I can see why this is annoying. At least the resol
sz may be able to add something about the
when/how he saw this; I do think it was fairly intermittent. Anyways, I'm
pretty sure this would have gone undiagnosed for weeks if not months if he
had not noticed and alerted us to the issue (causing all sorts of
frustration and confusion in the meant
e consistent: If a
permission is returned by `get_all_permissions()`, then checking that
permission with `has_perm()` should return `True`. The only reason to do
anything special in `has_perm()` is for performance optimizations.
tobias
--
You received this message because you are subscribed to the Googl
ewere else, were it is also easier to
detect (the existance of the bug, not exactly where it happens)
Beside that I don't see a vaild use case where something like this would
actually happen.
--
Tobias Wiese
--
You received this message because you are subscribed to the Google Grou
ack to the DB, you should add them to .only(). But in any case it protects
you from silently losing data by forgetting to include them in
update_fields (at the risk of generating extra queries if you forget to
include them in .only(), but at least you can see those and optimize them
away).
Consider
Agreed it's probably better to make the switch now, and I'd be fine without
a replacement shorthand alternative for --keepdb.
Cheers,
*Tobias McNulty*Chief Executive Officer
tob...@caktusgroup.com
www.caktusgroup.com
On Mon, Mar 11, 2019 at 8:19 AM Carlton Gibson
wrote:
> Th
irm or deny
most of these. They are HTTPS checks, and I believe the numbers represent
the time to connect and retrieve the page content (for
https://docs.djangoproject.com/en/2.1/).
Cheers,
*Tobias McNulty*Chief Executive Officer
tob...@caktusgroup.com
www.caktusgroup.com
On Mon, Feb 25,
erged in time?
Cheers,
*Tobias McNulty*Chief Executive Officer
tob...@caktusgroup.com
www.caktusgroup.com
--
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 receivi
igned to them).
Tobias
On Fri, Mar 8, 2019, 3:22 PM Markus Holtermann
wrote:
> Hi Carlton,
>
> my only question would be why you picked 2 months over 1 or 3. Generally
> in favor. I think de-assigning somebody after $time of inactivity on a
> ticket is fair, regardless of the comp
Tom,
That's great! Thanks for the feedback.
I've updated the PR <https://github.com/django/djangoproject.com/pull/870>
with something along the lines of what you suggested (along with the
corresponding configuration in Fastly).
Take a look and let me know what you think.
Chee
I don't think CloudFront supports passing a
custom Host header to the origin like Fastly does (i.e., you'll probably
need to edit /etc/hosts).
Cheers,
Tobias
On Sat, Feb 23, 2019, 7:15 PM Tom Forbes wrote:
> Sorry, I did not completely grok your message. I would be in favour of
ter cache time? And what's a good cache timeout
for such pages?
* How long are we comfortable waiting for *other* (not frequently updated)
pages to timeout, in the event they do change?
Tobias
On Fri, Feb 15, 2019 at 7:13 AM Tobias McNulty
wrote:
> Thanks for sharing the results.
>
> I d
Thanks for sharing the results.
I did manage to get a domain set up with working SSL, in case you want to
use it: https://django-docs.global.ssl.fastly.net/en/2.1/
Tobias
On Thu, Feb 14, 2019, 11:49 PM Cheng C Thanks for the test site, Tobias.
>
> Tested from Melbourne, Australia:
>
ango-dev on FreeNode.
Cheers,
Tobias
On Thu, Feb 14, 2019 at 8:26 AM Adam Johnson wrote:
> I have not had great experience with Fastly in the past and would avoid
> them. They run an old fork of Varnish which is not fun to configure.
>
> On Thu, 14 Feb 2019 at 11:16, Josh Smeaton wrot
Fastly could be a good fit. I've reached out to see if they'd be willing to
provide a free account. If anyone on this list works at Fastly or knows
someone who does, feel free to email/introduce me off list, too.
Tobias
On Thu, Feb 14, 2019, 5:58 AM Tom Forbes That makes sense, but in
For me it's the trust factor (allowing someone else to decrypt and
re-encrypt all our data). This may be less of an issue for the docs site,
*if* we don't have to assign DNS authority for the whole domain to the CDN
provider.
Tobias
On Wed, Feb 13, 2019, 7:47 PM Kye Russell I’ve be
Hello,
On 1/11/19 6:42 PM, George-Cristian Bîrzan wrote:
> the only thing that I can think of is whether HSTS preload will
> support anything except 301.
All my pages redirect via a 308 from the http to the https version.
And most of them are HSTS preloaded. So no problem here.
--
Tobias
ave
> it out of the issue and focus the discussion on usernames.
There was another Ticket about the email casing #17561 [1].
[1]: https://code.djangoproject.com/ticket/17561
--
Tobias Wiese
--
You received this message because you are subscribed to the Google Groups
"Django developer
On Fri, Nov 30, 2018, 1:03 PM Adam Johnson Tobias - using database updates isn't always viable. Also the system under
> test might need to take in the model instance, mutate it and execute its
> own save(), and then there's no way of rolling that back if the object
> wasn
aise an error or warning when a test does modify
an object that it shouldn't?
Tobias
On Wed, Nov 28, 2018 at 11:42 PM charettes wrote:
> Hey Josh, glad the package can help in the mean time!
>
> > Is there anyway to determine the pickle-ability of something without
> just try
Personally, I like the simplicity and elegance of a single SECRET_KEYS
setting. It's also a good way to raise awareness that rotation is A Good
Thing to be doing anyways.
In any case, I second all of those who've already endorsed this idea. If I
can help, let me know.
Tobias
On S
tly related to documentation:
https://github.com/django/django/pull/10636
This is still pretty rough. I feel like I overdid it. But I tried to
split it into different commits so that the individual changes can be
cherry-picked.
tobias
--
You received this message because you are subscribed to the
e the situation:
- Either add get_user_permissions() or remove get_group_permissions()
- Add default implementations for get_all_permissions() and
has_perm(), either in PermissionMixin or in a new BaseBackend class.
Any thoughts?
tobias
--
You received this message because you are subscribed t
e already been underdocumented before these changes. I would like to
help improving the documentation in general. However, the content and
structure of the documentation could be very different depending on
which of my changes get accepted. So my idea was to rework the
documentation afterwards.
t
o you think? Should I proceed writing pull requests for the
proposed changes?
tobias
[1]:
https://docs.djangoproject.com/en/2.1/topics/auth/customizing/#handling-object-permissions
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contri
Thank you for your feedback. I would like to answer some statements to
either convince you or make it more clear, where my idea stems from:
The fundamental reason why iterator() cannot be used with
> prefetch_related() is that the latter requires a set of model instance to
> be materialized to
Hi everyone!
The docs
(https://docs.djangoproject.com/en/2.1/ref/models/querysets/#iterator)
state that the
use of iterator() causes previous prefetch_related() calls to be ignored
> since these two optimizations do not make sense together.
I am wondering, if this is still true with the int
Hello,
I don't think this is something Django can or should handle. You need to
make your change in smaller increments so it doesn't break.
The proper forum for discussing this is the Django users list (or IRC or
Google...).
Good luck!
Tobias
On Mon, Oct 1, 2018, 8:47 PM marti
nce we're already used to that pattern
from create() vs bulk_create().
update_fields() alone may also work. Upside: it's shorter. Downside:
it's not immediately clear that it takes an iterable and not an
instance. I'd be happy with both options.
Best regards,
Tobias
--
Y
d my preference would be for a loud failure
(i.e., an exception rather than a log message) when this "strict" mode is
enabled. One can easily downgrade that to a log message when needed, less
so the other way around.
*Tobias McNulty*Chief Executive Officer
tob...@caktusgroup.com
www
behavior)? One could then use `.only()` or
`.values*()` to avoid fetching the related model, if needed.
*Tobias McNulty*Chief Executive Officer
tob...@caktusgroup.com
www.caktusgroup.com
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contr
hat will suffice. I don't recommend this because I
think existing Django developers would find it confusing, but technically
it would be possible to change or swap out instances of AnonymousUser via
middleware, too.
Lastly, this related ticket might be of interest:
https://code.djangoproject.com
t) see a reason to say no.
Tobias
*Tobias McNulty*Chief Executive Officer
tob...@caktusgroup.com
www.caktusgroup.com
On Mon, May 8, 2017 at 10:07 AM, Marc Tamlyn wrote:
> Yes, don't need that sorry.
>
> On 8 May 2017 at 14:40, Adam Johnson wrote:
>
>> I'm pretty
1 - 100 of 254 matches
Mail list logo