Re: How do you set the python path for django-admin?

e the module itself is installed in the venv, but the tests module is at the package root, you can run the tests like: django-admin test --settings=tests.settings --pythonpath=. HTH. Kind Regards, Carlton On Wed, 8 Nov 2023 at 20:18, Tobias Bengfort wrote: > Hi ever

Re: Disabling dark / light mode UI toggle

Quite likely not, but such a niche feature isn’t worth the extra API surface area, I’d likely think. On Wednesday, 9 August 2023, Niccolò Mineo wrote: > Yes, not pretty, though, right? > > Il giorno martedì 8 agosto 2023 alle 07:33:12 UTC+2 Adam Johnson ha > scritto: > >> You should be able to d

Re: Proposing the removal of Oracle from the Django supported backend databases

he state of play today). The difference with Windows (of course) is that we have lots of contributors using it. Kind Regards, Carlton On Fri, 4 Aug 2023 at 15:19, Paolo Melchiorre wrote: > Hi Mariusz, > > On Thu, Aug 3, 2023 at 8:47 PM Mariusz Felisiak > wrote: > > I&

Re: Can we move the activity on this list to the Forum now?

r testing would be much appreciated! Right now Discourse > recognizes that this is a problem and is interested in solving it, but > getting it prioritized will require folks to A) speak up saying they want > it done B) test the underlying API to verify that it actually solves the > prob

Re: Feedback for my draft proposal

Hi Jayant. This sounds like a good idea for an ecosystem package, but I think it's the kind of thing that's out-of-scope for a GSoC project I'm afraid. 😬 Kind Regards, Carlton On Tuesday, 28 March 2023 at 20:27:47 UTC+2 jayant khanna wrote: > Hello everyone, >

Re: GSOC 2023 Discussion and Feedback: Database-level Cascades

d/supported way. Kind Regards, Carlton On Monday, 27 March 2023 at 18:16:37 UTC+2 David Sanders wrote: > Hi Akash, > > Database-level cascading deletes is a topic that has been discussed often > since, well probably the dawn of Django 😁 From recollection the main > issue

Re: Filtering chosen options

This was added in https://github.com/django/django/commit/be63c78760924e1335603c36babd0ad6cfaea3c4 and will be part of Django 4.2, which is currently at release candidate stage, for final release around 2023-04-03. On Friday, 24 March 2023 at 03:20:41 UTC+1 Marty wrote: > Hi, > > Is there a

Re: GSOC 2023 Proposal Feedback on Security: Bring CORS and CSP into core

Hi Anvesh. I replied to your forum post: https://forum.djangoproject.com/t/gsoc-2023-discussion-on-security-bring-cors-and-csp-into-core/18932/7 — let's keep the discussion in one place please. Thanks. On Tue, 7 Mar 2023 at 17:59, Anvesh Mishra wrote: > I created a draft proposal GSOC Proposal

Django security releases issued: 4.1.7, 4.0.10, and 3.2.18

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2023/feb/14/security-releases/ -- 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 st

Re: Async wrappers in contrib packages

Great. Thanks Jon. I will follow up there next week. On Saturday, 11 February 2023, Jon Janzen wrote: > Hey Carlton, > > Sorry I skipped over the suggestion in one of your earlier messages to > post on the Forum. > > I’ve done so now: https://forum.djangoproject.com/t/ &g

Re: Async wrappers in contrib packages

On Thu, 9 Feb 2023 at 23:38, Jon Janzen wrote: > Hey Carlton, > > Thanks for your thoughtful comments, a few things come to mind: > > A. It sounds like we’re in agreement about the utility and severability of > Phase 1 (just creating an async_to_sync-based wrapper around the auth

Re: Async wrappers in contrib packages

orators as that seems like an orthogonal issue while https://code.djangoproject.com/ticket/31949 is pending, am I missing something here? Do I need to consider decorators in this proposal? I don't think they're dependent. Kind Regards, Carlton On Mon, 6 Feb 2023 at 03:22, Jon Janz

Re: Multiple instances of DjangoAdmin share the same model LogEntry

suggesting a custom template and tag in that case. (But maybe that's just me.) A diff of what you actually have in mind would likely help (to at least be clear). C. On Thu, 26 Jan 2023 at 15:26, Jacob Rief wrote: > Hi Carlton, > that proposal makes a lot of sense. > > T

Re: Multiple instances of DjangoAdmin share the same model LogEntry

. That's pretty niche I'd say. Kind Regards, Carlton On Thu, 26 Jan 2023 at 10:01, Jacob Rief wrote: > Hi Carlton, > > As I understand it, separate admin sites may register different models, > but I'm only going to see the History for instances that are visible to th

Re: Multiple instances of DjangoAdmin share the same model LogEntry

Hi Jacob. Can I ask you to explain your use-case a little more please? As I understand it, separate admin sites may register different models, but I'm only going to see the History for instances that are visible to the current admin no? Maybe you mean the Recent actions > My actions bit of the ind

Re: Proposal for an "Age" PostgreSQL ORM function

estion: > the function wrappers are in the main really quite trivial to add to your own project if you want them. Can we make the docs point this out more clearly? Like custom fields, custom functions shouldn't be something folks shy away from. 🤔 Kind Regards, Carlton

Re: Can we move the activity on this list to the Forum now?

if no-one beats me to it :) Thanks. C On Thu, 19 Jan 2023 at 18:15, Andrew Godwin wrote: > We should at least update those Trac and Triage Workflow docs to point to > both, maybe with the Forum first? > > Andrew > > On Thu, Jan 19, 2023, at 12:30 AM, Carlton Gibson wrote:

Re: Can we move the activity on this list to the Forum now?

lar >> arguments could be made for consolidating those... >> >> (On the other hand, I see little value in switching django-announce and >> django-updates, but I'm not necessarily opposed to it either, especially if >> there's a way to import the subscribers to

Re: [Technical Board?] Project Ideas, and beginning GSoC 2023.

Hi Manav. Great, thanks! 👍 On Tue, 17 Jan 2023 at 22:26, Manav Agarwal wrote: > Hii All! > > I am a Google Summer of Code 2021 Student and have contributed to > The schema editor project. > I would be happy to mentor a project this year. > > On Tue, Jan 17, 2023 at 8

Re: [Technical Board?] Project Ideas, and beginning GSoC 2023.

only person, please put me instead. *(*If you *didn't* suggest an idea but might like mentoring do feel free to do the opposite :) It's Google *Summer *of Code — so there's ages before anything much else happens. Thanks again. Kind Regards, Carlton On Tuesday, 15 November 2022

Re: Backport for ticket 34063?

Just to clarify this point, which I think has been glossed over: > But unless I'm misunderstanding the nature of the bug, this seems like it basically makes async views un-testable ... This isn't correct. Under normal circumstances you just use the sync Client, as you've always done. `response =

Re: Backport for ticket 34063?

nwilling to support ... Following the backport policy is not being unwilling to support. Sorry (again) that I don't share your view. Sorry that undermines your faith (in me) — I assume we still think there's room for rational disagreement on how to weigh competing concerns in these kinds of

Re: Backport for ticket 34063?

27;d guess I'd say we're entering a new phase, but the async support is neither complete nor mature. There will be bugs. I'm -1 on making an exception to the backport policy in this case. (Sorry I don't agree with you.) Kind Regards, Carlton On Fri, 30 Dec 2022 at 10:38,

Re: Backport for ticket 34063?

or ourselves. On Fri, 30 Dec 2022 at 10:13, James Bennett wrote: > On Fri, Dec 30, 2022 at 1:09 AM Carlton Gibson > wrote: > > All you're talking about is adding this to your test cases right? > > > > # Work around Django #34063 until 4.2. > > request.body >

Re: Backport for ticket 34063?

James, All you're talking about is adding this to your test cases right? # Work around Django #34063 until 4.2. request.body # ... continue C. On Fri, 30 Dec 2022 at 10:04, James Bennett wrote: > On Fri, Dec 30, 2022 at 12:01 AM Carlton Gibson > wrote: > > When I looked

Re: Backport for ticket 34063?

ing to add async support to your third-party library: super; just say it's 4.2+ and move on. Folks who aren't on the LTS will be updating shortly enough anyway. A little-bit of carrot never hurt. Kind Regards, Carlton On Fri, 30 Dec 2022 at 01:44, James Bennett wrote: > https://co

Re: Standalon Django ORM

I think we already have this no? See https://docs.djangoproject.com/en/4.1/ref/databases/#s-third-party-notes for a list of 3rd party DB backends. On Tue, 13 Dec 2022 at 10:31, Vasanth Mohan wrote: > I second Jörg about better maintainability with tighter integrations. > > However, for the fun

Django bugfix release: 4.1.4

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2022/dec/06/bugfix-release/ -- 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

Re: Async wrappers in contrib packages

it's just noise at that point.) I hope that makes sense. Kind Regards, Carlton On Mon, 28 Nov 2022 at 16:53, Jon Janzen wrote: > Hey Carlton, > > There's: https://code.djangoproject.com/ticket/31949 "Allow builtin view >> decorators to be applied directly to async

Re: Potential way forward for DATABASE_URL

. I'd rather measure twice and cut once is all. The whole point of the "Do it in a third-party app" approach is that we get to make sure the APIs are right, without adding churn to Django, and without being tied to the long-release cycle fixing the unforeseen issues that arise. Kind R

Re: Integrate dj-database-url into Django

This must be do-able now. There was some discussion of something along these lines a couple of years ago, with the idea of doing it for GSoC. There was much back-and-forth but no consensus. It has then come up again with Peter's suggestions about making it easier to get to a deployment ready stat

Re: [Technical Board?] Project Ideas, and beginning GSoC 2023.

On this vein I'd also like to see DB Cascades implemented https://code.djangoproject.com/ticket/21961 On Mon, 28 Nov 2022 at 18:10, 'st...@jigsawtech.co.uk' via Django developers (Contributions to Django itself) < django-developers@googlegroups.com> wrote: > +1 from me on DB defaults (constraint

Re: Can we move the activity on this list to the Forum now?

wrote: > Hi > > I can't speak for others, but I personally STRONGLY value the fact that > this discussion happens in my inbox, not on yet another website. > > But perhaps the forum still supports this reading mode? > > On Mon, 2022-11-28 at 05:38 -0800, Carlton Gibson wro

Can we move the activity on this list to the Forum now?

7;s unnecessary. We can still access the history here (until such a day as Google takes it away) at worst -- but, rather, if we can get an archive we could import it into read-only Datasette instance[0] — and that would likely be good enough. Can we move now? Thanks. Kind Regards, Carl

Re: Technical Board vote on DEP 0012: The Steering Council

Kind Regards, Carlton On Monday, 28 November 2022 at 09:52:35 UTC+1 f.apo...@gmail.com wrote: > Hi, > > +1 from me, but I'd like to ask the wider community (ie DSF members) > whether they support this change. > > While there has been some opposition on whether a change

Re: Integrate dj-database-url into Django

27;s not a point of religion.) Kind Regards, Carlton On Mon, 28 Nov 2022 at 14:03, 'Tobias McNulty' via Django developers (Contributions to Django itself) wrote: > Hi Carlton, > > Responses inline below: > > On Mon, Nov 28, 2022, 2:40 AM Carlton Gibson > wrote: > >

Re: Integrate dj-database-url into Django

I see you posted afresh in the other thread, addressing some of the points here. C. On Mon, 28 Nov 2022 at 08:39, Carlton Gibson wrote: > Hi Raphael, thanks for picking this up. > > Looking at the history here, particularly the discussion here > https://groups.google.com/g/django-

Re: Async wrappers in contrib packages

#x27;re thinking of 🤔) > ...and django.contrib.syndication (views.Feed) Not sure what you have in mind here. Perhaps explaining that in more detail would help? (I'm not immediately sure I see the benefit of async for the feed views? 🤔) Kind Regards, Carlton On Sun, 27 Nov 2022 at 23:02, Jon Janzen

Re: Integrate dj-database-url into Django

f 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. Kind Regards, Carlton On Sun, 27 Nov 2022 at 20:40, Raphael G wrote: > Alright, I tried to revive Tom Forbe's work on this in >

Re: Set a reasonable default for EMAIL_TIMEOUT

ur own backend, without the BC concerns for others. So that's not a, yes, let's change it, but hopefully it doesn't leave you without optimism 🙂 Kind Regards, Carlton On Thu, 17 Nov 2022 at 16:33, Federico Capoano wrote: > Hi all, > > Why is there no default for EMAIL_TI

Re: [Technical Board?] Project Ideas, and beginning GSoC 2023.

Thanks Florian To you and all :) — casting the net wide right now is a good way forward I think. We can scope down for GSoC with some ideas on the table. (Don't be shy folks. :) Kind Regards, Carlton On Wed, 16 Nov 2022 at 19:52, Florian Apolloner wrote: > I do have ideas but no id

[Technical Board?] Project Ideas, and beginning GSoC 2023.

, to great success. I'd like to offer that help again to e.g. Jazzband or other established projects, assuming maintainers feel they have the capacity to mentor. (It's a minor increment to my effort for a good return I think.) No urgency but, can I ask you to put your grey

Advancing the "content negotiation" and "modernising request object" proposals.

sensible. (Prefetch evolved...) Matching ``request.data``, if Adam will pick it up, the modernised request API would be delightful. (The schedule leaves room for the code changes to come before the documentation updates if needed.) Does this seem like a reasonable plan? Thanks Kind Regards

Re: Proposal: Clarify individual members page

Great, Thanks Andrew. No urgency 😊 On Tue, 8 Nov 2022 at 16:16, Andrew Mshar wrote: > Will do, Carlton. > > Tim and Cory, thanks for the suggestions. I'll incorporate those in the PR > and post here when it's ready. Probably not today, but I should be able to > open

Re: Proposal: Clarify individual members page

ng 🤩 Thanks. Kind Regards, Carlton On Mon, 7 Nov 2022 at 19:51, Tim Allen wrote: > I'm of the opinion that if you care enough about Django to investigate > becoming a member of the DSF, that's enough of a qualification - it is just > challenging to formalize that into pro

Re: Proposal: Clarify individual members page

've been new members of the community, who didn't pass the *service* bit (even though *intending* to get involved). I think this is something that needs to be discussed on the DSF members list. Could I (cheekily) ask you to open the batting? Kind Regards, Carlton On Mon, 7 Nov 202

Re: Adjusting DEP 10 "How Django is released" section.

To simplify the remaining discussions, I'd like to move this forward to a Technical Board vote sooner rather than later. Thanks. Kind Regards, Carlton On Thursday, 27 October 2022 at 08:56:25 UTC+2 Carlton Gibson wrote: > Hi all, > > Almost scared to say it but, the discussion on th

Re: Proposal: cacheif template tag

Hi Igor, The sort of thing I had in mind was: {% with cache_timeout=request.user.is_authenticated|yesno:"0,500" %} {% cache cache_timeout sidebar %} ... {% endcache %} {% endwith %} Kind Regards, Carlton On Wednesday, 12 October 2022 at 17:17:57

Re: Proposal: Clarify individual members page

ants to draft new language, that would be great. If not, I may > have some time next week to try. > > Thanks, > Andrew > > P.S. Great meeting both of you at Djangocon last week! > On Thursday, October 27, 2022 at 7:41:15 AM UTC-4 schill...@gmail.com > wrote: > >>

Re: Proposal: Clarify individual members page

involved. One idea was a more open membership level that anyone interested could take up, that would allow easier communication if nothing else. I don't know how those discussions will turn out, but stay tuned 🙂 I hope that clarifies a litte? In any case, Welcome aboard! ⛵️ :) Please reach out

Adjusting DEP 10 "How Django is released" section.

ly discarding DEP 10, I don't see that at all. Rather, the most of it is great. It was written in abstract though, so it's to be expected that we would revise given experience of how it applies in practice. I will create the draft DEP to fulfil the formalities here, and ask for a TB vo

Re: Creating internal/admin pages without Models

Check out Django-admin-views https://github.com/frankwiles/django-admin-views I think it needs a bit of an update for recent versions of Django (but I suspect those are minor) and o tho knit does what you’re after (or close) On Tuesday, 25 October 2022, Vasanth Mohan wrote: > Hi Igor, > > Most

Re: Changing the role of the Technical Board

he ongoing pandemic has kept everyone busy. Having a pool of candidates can but help.) +1 to the proposal. Kind Regards, Carlton p.s. That a current Merger cannot also on the TB has proven correct: to have a fallback is essential for Merger sanity, e.g. the typing proposal, for which it’s not reasonab

Re: Model-level validation

> ... the duplication I was referring to is having both Forms and Serializers do validation. That's a separate issue. Can we merge various aspects of DRF into Django, so that it better handles building JSON APIs? Yes, clearly. One step of that is better content type handling, another is serialize

Re: Making max_length argument optional

x27;s version Tom linked before <https://github.com/jacobian/django-postgres-unlimited-varchar/blob/master/django_postgres_unlimited_varchar.py> My guess would be 1 or 3. (I'd rather 3 than 2.) So proof-of-concepts implementing those would be the way forward I think. Kind Regards, Car

Django security releases issued: 4.1.2, 4.0.8, and 3.2.16

Details are available on the Django weblog: https://www.djangoproject.com/weblog/2022/oct/04/security-releases/ -- 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 recei

Re: Optional URL parameters in django.urls.path

and related functionality such as reverse() that would also need updating.) (IRL I've rarely needed this pattern. I've used both the options above without issue) So, I'd probably be -1 at this point. Kind regards Carlton On Sun, 2 Oct 2022 at 08:16, Meiyer wrote: > Is the

Re: Proposal: cacheif template tag

Hey Igor, I wonder if you can achieve the same varying the timeout parameter based in user.is_authenticated? Kind Regards, Carlton On Sat, 24 Sept 2022 at 15:35, Igor Margitich wrote: > Hi django-developers, > > I would like to propose new template tag `cacheif`. Could be useful w

Re: Proposal: Add utility class "ClassList"

Hey Jacob. Thanks for this. Can I ask you to give a few examples of potential usages in Django, and showing the gain over use a set in these cases? I'm trying to imagine exactly what you have in mind, but I'm not entirely clear. Thanks again. Carlton On Friday, 23 September 202

Re: Model-level validation

Hi. I have to ask, did you search the history at all here? This has been discussed *several times* over the years. > Bringing View-level concepts such as forms down into celery tasks and management commands breaks separation of concerns... I think it's an error to think of forms (please read

Re: Revisiting multiline template tags in Django Templates (again)

this in person with Carlton > Gibson at the DjangoCon Europe sprints in Porto, who provisionally offered > to act as a shepherd for this proposed DEP. This is on the condition that I > find an implementation team as well. > > On Saturday, 24 September 2022 at 08:37:52 UTC+1 Thibaud

Re: Optional URL parameters in django.urls.path

One approach is to route two patterns (one with the parameter and one without) to the same URL. Some duplication but (perhaps) easier to read at a glance than either an optional `?` operator. Given that — and the alternative re_path() approach being available — unless there was a particularly sim

Re: Add support for IDNA 2008

OK, great, thanks. I'll await your PR. Let's continue on GitHub for the moment then Good hustle 👍 On Wed, 14 Sept 2022 at 15:54, 'Julien Bernard' via Django developers (Contributions to Django itself) wrote: > Hi Carlton, > > Le mardi 13 septembre 2022 à 07:17:31

Re: Add support for IDNA 2008

#x27;)) b'https://fuss.standcore.com/' # Was expecting https://xn--fu-hia.standcore.com/ from discussion 🤔 >>> import idna >>> idna.encode('https://fuß.standcore.com/') Traceback (most recent call last): File "", line 1, in

Re: Check constraint validation with NULLs

Hi David. This is https://code.djangoproject.com/ticket/33996 I think — it's a Release Blocker for 4.1.2 Your thoughts/review on work there would be welcome. :) Kind Regards, Carlton On Thu, 8 Sept 2022 at 14:30, David Sanders wrote: > Hi folks, > > I've noticed a di

Re: Need help on solving an issue

e for the issue, that shows how it fails, that's a great start. Then take a look at this PR, which looks related 🤔 — although that needs confirming (and it needs a test case at least). https://github.com/django/django/pull/15573 I hope that helps. Kind Regards, Carlton On Wed, 7 Sept 202

Re: Add support for IDNA 2008

895.html>, use the third-party idna module <https://pypi.org/project/idna/>. So the question is do we **need** the newer standard? I will have a read of the various resources here, and I'll also ask the Django Security Team if they have any thoughts. Kind Regards, Carlton On Tu

Re: Add support for IDNA 2008

packaging isn't what it was... — but **if** we take on an extra dependency it needs to be for a clear gain. Likely (still) a proof-of-concept at least showing what's added (as a separate package? 🤔) is the easiest way forward? Others may yet agree that this is something needed. Kind Reg

Re: Add support for IDNA 2008

but it does need weighing...) Kind Regards, Carlton On Fri, 2 Sept 2022 at 17:32, 'Julien Bernard' via Django developers (Contributions to Django itself) wrote: > Thanks Adam. > The ticket was targetting EmailValidator but the punycode method is used > at more places in Django

Re: Make timeout property for PasswordResetTokenGenerator

ply was attempting to expand the reason for the original decision to turn it down. C. On Wed, 24 Aug 2022 at 15:53, 'Robert Musił' via Django developers (Contributions to Django itself) wrote: > Hey Carlton, > > I'm reading through the replies and I feel

Re: #21978 include production-ready web server

yhow, other than a "I've been thinking along these lines", and a generally positive emote, I don't have too much more concrete at this stage. 👍 C. On Tue, 23 Aug 2022 at 19:00, Peter Baumgartner wrote: > Thanks for the additional background Carlton! I like the idea of &g

Re: #21978 include production-ready web server

pip install + a line in INSTALLED_APPS doesn't seem too much to ask (I think.) Was it really 4 years ago Tom left that comment on #21978 <https://code.djangoproject.com/ticket/21978> 😳 (We'd finally close this as wontfix: Django doesn't ship a webserver.) Does that fit in your

Re: About #33904, Many-To-Many field is deleted/ignored from internal JavaScript “filter” interface

Hi Carsten, Mariusz marked that as a duplicate The fix was applied to stable/4.1.x here: https://github.com/django/django/commit/82e9e19ebe6bc920f1cfffc42d86648644fd4a78 It'll be part of the next release. https://docs.djangoproject.com/en/4.1/releases/4.1.1/ Can you give stable/4.1.x a try and

Re: Make timeout property for PasswordResetTokenGenerator

TokenGenerator to use Signer or TimestampSigner internally > , but I was surprised to discover that it didn't use either. > > Isn't those entry points the better API to advise for use rather than the > direct use of hmac based algorithms? > > On Tue, 2022-08-23 at 12:45 +0

Re: Make timeout property for PasswordResetTokenGenerator

underlying signing code that you really want to lean on Django for.) Kind Regards, Carlton On Mon, 22 Aug 2022 at 17:26, Alexander Voloshchenko < voloshchenkoalexan...@gmail.com> wrote: > During project development our team needs to create several types of > tokens. One of them w

Re: transaction.on_commit() proposal

Related ticket from this weekend, suggesting a docs change: https://code.djangoproject.com/ticket/33939 On Mon, 22 Aug 2022 at 14:11, 'Adam Johnson' via Django developers (Contributions to Django itself) wrote: > Hi > > I just wrote a blog post on a late-binding bug that can occur with using > t

Re: Feature Request: get_default_backend() in django.template.Engine

-case comes up here? #27359 was a while back now so we might exposing a new hook to have come up more quickly. Thanks. Kind Regards, Carlton On Thursday, 11 August 2022 at 20:44:06 UTC+2 homa...@gmail.com wrote: > Hi, > > We're trying to create a template from string using

Re: More user friendly delete confirmation template

Sounds good. (You mentioned adding an additional template block. You could put that in a commit to look at as well if you think it's of value to you.) On Wed, 17 Aug 2022 at 08:14, Jacob Rief wrote: > On Wednesday, August 17, 2022 at 7:23:35 AM UTC+2 Carlton Gibson wrote: > >

Re: More user friendly delete confirmation template

> Can we at least agree to put an id="..." onto the element wrapping that list. That seems pretty minimal. 🙂 Do you want to open a PR so we can have a look? On Tue, 16 Aug 2022 at 21:58, Jacob Rief wrote: > Can we at least agree to put an id="..." onto the element wrapping > that list. > Tha

Re: More user friendly delete confirmation template

de a template or two, or add a rich JS widget to a form, or ... (there are a few *kinds* of use-cases that come up I think)... — would be a useful resource? I've always had to search for a while each time I've wanted to do this in the past. To me this would seem like something we could add

Django 4.1 released

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2022/aug/03/django-41-released/ -- 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 s

Django security releases issued: 4.0.7 and 3.2.15.

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2022/aug/03/security-releases/ -- 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 st

Re: timesince and timeuntil - should we use python-dateutil?

rty package. (I don't think we really document it, but one could shadow/override the built-in tags with the improved versions if your app was installed, I guess...) Or that would be my initial thought. 🤔 Kind Regards, Carlton ‪On Tue, 2 Aug 2022 at 03:27, ‫אורי‬‎ wrote:‬ > Hi, >

Re: Switching to PEP 621 project metadata

be appreciative of the contribution. Kind Regards, Carlton -- 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

Re: Switching to PEP 621 project metadata

a project like Django, there's a certain value in being second-to-last off the boat. Kind regards, Carlton On Sun, 24 Jul 2022 at 22:39, James Bennett wrote: > On Sun, Jul 24, 2022 at 1:34 PM Ofek Lev wrote: > >> > My initial reaction is "no", and that this

Django 4.1 release candidate 1 released

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2022/jul/19/django-41-rc1/ -- 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 r

Re: (Circa end of 2021) Localization issues with input type=date?

Thanks Denny. I'll follow-up on the PR. Let's see what folks have to say. 👍 Kind Regards, Carlton On Wed, 29 Jun 2022 at 22:20, Denny Biasiolli wrote: > Hi Carlton, > > Here we go: https://github.com/django/django/pull/15806 > Just a draft for now, tried on a local

Re: (Circa end of 2021) Localization issues with input type=date?

Hey Denny. Thanks for looking at this! > My idea was to change... Can I get you to put that into a (draft) PR on GitHub? It's much easier to think about with code in hand. :) Kind Regards, Carlton On Tuesday, 28 June 2022 at 18:47:57 UTC+2 denny.b...@gmail.com wrote: >

Re: JsonResponse have a DEFAULT_JSON_ENCODER setting

This is talking about HTTP responses, rather than fields, but I agree with Adam here: you should be able to encapsulate overriding the default encoder in a single location. It doesn't need a setting. On Thu, 23 Jun 2022 at 23:57, 'Adam Johnson' via Django developers (Contributions to Django itself

Django 4.1 beta 1 released

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2022/jun/21/django-41-beta-1-released/ -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this grou

Re: Decision on a 2FA PR

hat does WebAuthn in Django look like?" — answering that would be a major contribution. Kind Regards, Carlton On Sunday, 5 June 2022 at 19:48:22 UTC+2 Yonas wrote: > Hi, > > In light of what happened to the ctx package, this is a good time to get a > conclusion on the follo

Re: Feature Idea: Allow setting session cookie name dynamically

ought... -- interested to see others' thoughts.) Kind regards, Carlton Aside: Searching, there are lots of disparate resources for multi-tenant deploys; slightly orthogonal to your exact suggestion here, I imagine there's good work to be done corralling the interested parties and patterns. Maybe one

Django bugfix release: 4.0.5

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2022/jun/01/bugfix-release/ -- 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

Re: Django 4.1 alpha 1 released

— it looks like your use-case isn't covered by the existing tests. Can I ask you to open a ticket on Trac, with a minimal test and we can have a look? Thanks! 👍 Kind Regards, Carlton ‪On Thu, 19 May 2022 at 05:50, ‫אורי‬‎ wrote:‬ > Hi, > > In my code there is clean_fields with

Django 4.1 alpha 1 released

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2022/may/18/django-41-alpha-1-released/ -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this gro

Re: Performance does not scale when increasing file upload sizes

look at!) I'd very much want to dig into a dependency before deciding to take one on. I suspect it's not **that** complex, so it's likely something we'd want to re-implement to fit our needs exactly. (But we can see on review...) Please do open a PR when you're ready. Kind

Re: Status of 4.1 pre-release.

On Wed, 11 May 2022 at 13:53, thinkwel...@gmail.com < thinkwelldesi...@gmail.com> wrote: > Will the psycopg3 backend > land in time for the 4.1 release? I'm looking forward to it, as it should > support PyPy much better than psycopg2 does. > No. It's

Re: Status of 4.1 pre-release.

tweaks, so I wanted (want) to get it resolved. C. On Wed, 11 May 2022 at 09:04, Jacob Rief wrote: > Hi Carlton, > there is somehow a contradiction: > In https://code.djangoproject.com/wiki/Version4.1Roadmap it's written: > > Better yet, find someone to review your patch and

Status of 4.1 pre-release.

p, we have pre-releases through June and July, targeting August 3 for Django 4.1 final. Please test early and often. We will use this thread to inform you of any changes to the schedule. Thanks again. It wouldn't be possible without you! 🎁 Kind Regards, Carlton -- You received this messa

Re: Provide a way to pass kwargs when initializing the storage class

Hi Jarosław. Thanks for picking this up. There seems to be enough support for the general idea here, so worth pressing on. Let's think about any required deprecations on the PR. (It's easier there 😅). Kind Regards, Carlton On Sunday, 24 April 2022 at 01:25:28 UTC+2 jaro...

  1   2   3   4   5   6   7   8   >