Re: Pendolumn
Hi, Damiano I suspect we chatted on IRC yesterday about this... On Wed, 9 Sep 2020, at 11:01, Damiano Porta wrote: > Hello everybody! > Can I use Pendolumn (https://pendulum.eustace.io/) as default datetime > library for my models? > This library is good, it has very intuitive and clean API design. It is > relying on the standard library. So, it is basically a "more advanced" > datetime. You can use whatever tools you want in your application. Where do you see this library in particular providing benefit in your models? What I understood of your query yesterday [if it were, indeed, you] was you were proposing Django used this lib throughout. If that is the case, you would need to clearly describe what benefits the project as a whole would gain by bringing on this dependency that couldn't already be managed by a 3rd party package that individual projects could opt to use. -- Curtis -- 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...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/30434283-7856-47a9-9720-a3204f084af4%40www.fastmail.com.
Pendolumn
Hello everybody! Can I use Pendolumn (https://pendulum.eustace.io/) as default datetime library for my models? This library is good, it has very intuitive and clean API design. It is relying on the standard library. So, it is basically a "more advanced" datetime. Thanks -- 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...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/4150ad6f-09b4-4166-b2ed-78c23de7e8e0n%40googlegroups.com.
Re: Regression in Set-Cookie which affects Django users
django-cookie-samesite has a browser version guesser, because different browsers interpret samesite differently. The best solution I've heard of is setting two cookies with two different names, one the old way and one the google way. Then check for both where checking needs done, one of them being a fallback. On Sun, 23 Aug 2020 at 03:41, אורי wrote: > > > > On Sat, Aug 22, 2020 at 10:07 PM Adam Johnson wrote: >> >> (The workaround is in this comment: >> https://github.com/django/django/pull/11894#issuecomment-577681440 , and if >> you want, a package: https://github.com/jotes/django-cookies-samesite ) > > > Thank you. I was not aware of this package and middleware. > > אורי. > > -- > 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...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/CABD5YeGTtzHQMrsB%3Dc%3DHBeymNxWFJc1En9vqj%3DF1HEtO5P0odA%40mail.gmail.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 receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CACQ%3DrrdpXMcQUmHVF9hQgXtD-1pADQMO5WoyySBw3OB-p5Oqeg%40mail.gmail.com.
