Re: getting started with contributions

Hello Adam This helps a lot I will get started as soon as possible and ask for your guidance along the way Regards Vanshita On Tue, 4 Jan 2022, 15:31 'Adam Johnson' via Django developers (Contributions to Django itself), wrote: > Welcome! > > There are many different ways to contribute to

Re: Django security releases issued: 4.0.1, 3.2.11, and 2.2.26

> > I would argue that the Django team always said that the documentation is > the public API. Everything else works by luck. I agree with Florian, this is Django’s policy. To go against it and restore the undocumented behaviour requires a strong case, perahps that many users were affected or

Re: Django security releases issued: 4.0.1, 3.2.11, and 2.2.26

Hi, On Tuesday, January 4, 2022 at 2:09:18 PM UTC+1 Sjoerd Job Postmus wrote: > Unfortunately (at least for us), this breaks the case where dictsort was > used with a static argument that looked up a callable. A quick code search > showed that the pattern dictsort.*get​ ( >

Re: getting started with contributions

Hi Adam, I also want to start my contribution journey, can I follow up the same details. Thanks and Regards Vijayant On Tue, Jan 4, 2022 at 3:31 PM 'Adam Johnson' via Django developers (Contributions to Django itself) wrote: > Welcome! > > There are many different ways to contribute to Django

Re: getting started with contributions

Thank you for your time , I will get started as soon as possible . On Tue, 4 Jan 2022, 04:24 Ayush, wrote: > Did you look at the issue tracker? Choose the "Easy Pickings" Tickets > from there > that will help you get familiar with django

Re: Django security releases issued: 4.0.1, 3.2.11, and 2.2.26

Hi! I have a question regarding the fix for CVE-2021-45116. In this fix the resolving logic for 'paths' passed to dictsort is simplified to no longer support indexing into lists, nor to support method-calls on objects. The explanation here is that: > Due to leveraging the Django Template

Implementation of view permission in Django admin

Hello everyone! I have been looking into the implementation of ModelAdmin and how it processes the view only permission. While rendering a ModelAdmin for a user with view-only permission, the ModelAdmin disregard widget defined for the field and uses the AdminReadonlyField

Django security releases issued: 4.0.1, 3.2.11, and 2.2.26

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

Re: getting started with contributions

Welcome! There are many different ways to contribute to Django - the forum, blogging, translating, documenting, writing code, and more. Our Contributing Guide can help you get started with many of these: https://docs.djangoproject.com/en/stable/internals/contributing/ If you’re looking to work