New to GSOC

2021-03-29 Thread 18-051_sumek agarwal
Hello sir,
I have a firm grip on DJANGO framework. I have contributed to open source 
(Girlscript summer of code) and still contributing to it. I have used 
DJANGO as the backend framework and had quite good results using it.
Now, I want you to suggest me whether I should first have some 
contributions in Django organization or shall I directly apply for the 
proposal?
Hope that I get a response quickly and positively.
Thank you, Regards.

-- 
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/a28243e3-836f-40f2-9e63-d61bb7fe1d72n%40googlegroups.com.


GSOC Proposal: Adding Redis Cache Backend To Django Core.

2021-03-29 Thread Girish Sontakke
Hello, I am Girish Sontakke from India. I am willing to start contributing 
to Django through GSOC 2021. I have gone through the Idea List available on 
the Django wiki page for GSOC 
 and select the 
project of adding Redis Cache Backend To Django Core. For this, I have 
explored the django.core.cache 
 section of 
the framework and take some Ideas for Django's Cache Framework 
 from the 
documentation available at djangoprojects.com.
There are some caching backends already available in the django core but 
Redis being one the popular caching engines, there should be the 
implementation of Redis Backend in the core django package.  There are some 
Greate packages out there for integrating Redis into Django such as 
django-redis  and 
django-redis-cache , still, 
there is a need for inner Redis Backend in django.
For this I am writing a proposal here 
. 
I request all of the fellow developers and mentors to give some suggestions 
for this Idea and share your views on this project.
 
With Regards, 
Girish Sontakke.

-- 
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/77fcb2b0-98f3-45a9-883f-a5ff1d76c00bn%40googlegroups.com.


Re: New to GSOC

2021-03-29 Thread Manav Agarwal
Hey,
IMO you should be familiar with How to contribute to Django. For that, you 
may refer https://docs.djangoproject.com/en/dev/internals/contributing/ 
.Then, you can select a topic/Project Idea for your proposal from 
https://code.djangoproject.com/wiki/SummerOfCode2021 .
Hope that helps.
Regards,
Manav Agarwal

On Monday, March 29, 2021 at 5:01:33 PM UTC+5:30 sumekag...@gmail.com wrote:

> Hello sir,
> I have a firm grip on DJANGO framework. I have contributed to open source 
> (Girlscript summer of code) and still contributing to it. I have used 
> DJANGO as the backend framework and had quite good results using it.
> Now, I want you to suggest me whether I should first have some 
> contributions in Django organization or shall I directly apply for the 
> proposal?
> Hope that I get a response quickly and positively.
> Thank you, Regards.
>

-- 
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/153ba68c-ba6e-4eb7-b6b4-00add2d3e260n%40googlegroups.com.


Re: Fellow Reports - March 2021

2021-03-29 Thread Mariusz Felisiak
Week ending March 28, 2021

*Triaged:*
   https://code.djangoproject.com/ticket/32578 - Handle request.get_host() 
raising DisallowedHost in CsrfViewMiddleware._origin_verified() (accepted) 
   https://code.djangoproject.com/ticket/32581 - to_locale should be 
idempotent (accepted) 
   https://code.djangoproject.com/ticket/32580 - Document that 
HttpRequest.get_host() can raise DisallowedHost (accepted) 
   https://code.djangoproject.com/ticket/32582 - Extra dot in cloned test 
database file names on SQLite when using --parallel. (accepted) 
   https://code.djangoproject.com/ticket/32583 - Allow mass emails with 
EmailMessage Object (wontfix) 
   https://code.djangoproject.com/ticket/32573 - Query optimization in 
YearLookup breaks filtering by "__iso_year" (accepted) 
   https://code.djangoproject.com/ticket/32579 - Two outdated code comments 
in CsrfViewMiddleware.process_view() (accepted) 
   https://code.djangoproject.com/ticket/32585 - Value() with DecimalField 
crashes on SQLite. (accepted) 
   https://code.djangoproject.com/ticket/32586 - ASGI responses from Django 
do not provide lowercased HTTP headers as required by the spec (invalid) 
   https://code.djangoproject.com/ticket/32588 - Exception handling in 
contrib.postgres (invalid) 
   https://code.djangoproject.com/ticket/32590 - Add option to avoid 
subtransactions by default when using transaction.atomic() (wontfix) 
   https://code.djangoproject.com/ticket/32592 - Add places argument to 
Round database function. (duplicate) 
   https://code.djangoproject.com/ticket/32593 - Cast() to DecimalField() 
raises DataError. (invalid) 
   https://code.djangoproject.com/ticket/32587 - Use RelatedManager of 
parent object in get_queryset of inlines and support prefetching 
(duplicate) 
   https://code.djangoproject.com/ticket/32594 - Signal.disconnect() 
returns None when passing sender as string (accepted) 
   https://code.djangoproject.com/ticket/32595 - mysql DatabaseSchemaEditor 
can't `quote_value` on byte strings (invalid) 
   https://code.djangoproject.com/ticket/32596 - Add a method to 
CsrfViewMiddleware to encapsulate its referer logic (accepted) 
   https://code.djangoproject.com/ticket/32572 - ResolverMatch.__repr__() 
doesn't handle functools.partial() nicely. (accepted) 
   https://code.djangoproject.com/ticket/32598 - Issue in models.SlugField 
(invalid) 
   https://code.djangoproject.com/ticket/32599 - 
django.contrib.auth.forms.py should always refer to User as 
get_user_model() (duplicate) 
   https://code.djangoproject.com/ticket/32600 - Multi geometries cause 
Segmentation fault 11 on Macbook with M1 CPU (duplicate) 

*Reviewed/committed: *
   https://github.com/django/django/pull/14164 - Fixed #32581 -- Prevented 
to_locale() from corrupting locale names. 
   https://github.com/django/django/pull/14160 - Fixed #32576 -- Corrected 
dumpdata docs for passing model names to the --exclude option. 
   https://github.com/django/django/pull/14153 - Refs #31732 -- Fixed 
django.utils.inspect caching for bound methods. 
   https://github.com/django/django/pull/13906 - Optimized 
django.utils.text.capfirst(). 
   https://github.com/django/django/pull/14170 - Fixed #32573 -- Fixed 
bounds in __iso_year lookup optimization. 
   https://github.com/django/django/pull/14022 - Fixed #32460 -- Allowed 
"label"/"do_not_call_in_templates" members in model choice enums. 
   https://github.com/django/django/pull/14149 - Fixed #29606 -- Added type 
check for ALLOWED_HOSTS setting. 
   https://github.com/django/django/pull/14177 - Refs #32532 -- Added 
DiscoverRunner.load_tests_for_label(). 
   https://github.com/django/django/pull/14169 - Fixed #32582 -- Removed 
unnecessary dot in names of cloned test databases on SQLite. 
   https://github.com/django/django/pull/14176 - Fixed #32579 -- Fixed 
outdated comments in CsrfViewMiddleware.process_view(). 
   https://github.com/django/django/pull/14179 - Fixed #32578 -- Fixed 
crash in CsrfViewMiddleware when a request with Origin header has an 
invalid host. 
   https://github.com/django/django/pull/14183 - Refs #31003 -- Moved note 
about return value of QuerySet.bulk_create() to the first paragraph. 
   https://github.com/django/django/pull/14181 - Fixed #32580 -- Doc'd that 
HttpRequest.get_host() may raise DisallowedHost. 
   https://github.com/django/django/pull/14192 - Refs #32355 -- Corrected 
comments about Python's _NamespacePath. 
   https://github.com/django/django/pull/14191 - Fixed #32591 -- Made 
DiscoverRunner order _FailedTest objects first. 

*Reviewed: *
   https://github.com/django/djangoproject.com/pull/1078 - Re-added 
reCaptcha to fundraising page. 

*Authored: *
   https://github.com/django/django/pull/14167 - Refs #32353, Refs #32352 
-- Fixed GIS tests with PROJ 7.X. 

Best,
Mariusz

-- 
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 i

Bug with order_by and reverse on a __in exclusion query

2021-03-29 Thread Nathaniel Brown
Basically when I try to exclude all members that have cancelled standing 
from all the poems it breaks and includes all Poems no matter if the member 
was cancelled.

You can remove the order_by and reverse clauses on the poems_created and 
the list shows fine, yet when I add a order_by it has no effect. And when I 
add the reverse it does as previously explained, shows all poems no matter 
if the member was cancelled.

Member has lets say two fields, a User pk and a standing; a Poem has 
created by and a Title with a submitter relating to the User pk. 

Here is the sample code:

members_cancelled = 
Member.objects.exclude(standing=settings.MEMBER_STANDING_CANCELLED).values_list('pk',
 
flat=True)
poems_created = Poem.objects.exclude(submitter__in=list(members_cancelled), 
hidden=True).order_by('created').reverse()

Thanks in advance in you've got this far.

Nate

-- 
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/c76e2a29-e036-495b-8b03-397b943217b9n%40googlegroups.com.


Re: Bug with order_by and reverse on a __in exclusion query

2021-03-29 Thread אורי
Did you open a ticket?

https://code.djangoproject.com/


אורי
u...@speedy.net


On Mon, Mar 29, 2021 at 11:18 PM Nathaniel Brown  wrote:

> Basically when I try to exclude all members that have cancelled standing
> from all the poems it breaks and includes all Poems no matter if the member
> was cancelled.
>
> You can remove the order_by and reverse clauses on the poems_created and
> the list shows fine, yet when I add a order_by it has no effect. And when I
> add the reverse it does as previously explained, shows all poems no matter
> if the member was cancelled.
>
> Member has lets say two fields, a User pk and a standing; a Poem has
> created by and a Title with a submitter relating to the User pk.
>
> Here is the sample code:
>
> members_cancelled =
> Member.objects.exclude(standing=settings.MEMBER_STANDING_CANCELLED).values_list('pk',
> flat=True)
> poems_created =
> Poem.objects.exclude(submitter__in=list(members_cancelled),
> hidden=True).order_by('created').reverse()
>
> Thanks in advance in you've got this far.
>
> Nate
>
> --
> 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/c76e2a29-e036-495b-8b03-397b943217b9n%40googlegroups.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/CABD5YeEGp6Y1vEFvUmBhHTn3SWMBoqKdBeXp%3DBgqAXbOQSfvDA%40mail.gmail.com.