Django 4.2 alpha 1 released

[Mariusz Felisiak]

Details are available on the Django project weblog:

https://www.djangoproject.com/weblog/2023/jan/17/django-42-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 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/96be0548-79f4-4a84-06d4-7b85cad63696%40gmail.com.

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

[Carlton Gibson]

Hi All! 

Thanks for your earlier replies, comments and ideas!

The organisation application period for GSoC begins next week, so I've 
pulled them together to begin the ideas page: 

https://code.djangoproject.com/wiki/SummerOfCode2023

It's not 100% — not least I need to go over the WIKI formatting, and make 
it consistent (but ignore that, or make clean ups :) 
*Please have a look *— see if the descriptions make sense. 
(I want to add a few more links and such, and tweak the descriptions — 
again, happy to take edits :) 

If you suggested an idea I put you as a *Possible Mentor*. 
That doesn't mean you're committed to anything — but equally we do need 
mentors… :)
What's involved? Not too much: being available to comment on a PR on your 
project is the main bit. 
If you know you're not happy to mentor, you can remove yourself: if you're 
the 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 at 10:11:45 UTC+1 Carlton Gibson wrote:

> Hi all. 
>
> Google Summer of Code (GSoC) for 2023 has just been announced. 
>
> https://opensource.googleblog.com/2022/11/get-ready-for-google-summer-of-code-2023.html
>
> Django has participated many times, and it's been a real boon. Recent 
> successes include: 
>
> * The django-stubs mypy plugin. 
> * The cross-db JSON field. 
> * The Redis cache backend. 
> * Per model-class (field instance) custom lookups
> * Setup of the django-asv benchmarking project. 
> * ... 
>
> Application deadline for Orgs is February 7. I'll begin working on it 
> after the New Year. 
>
> Main bit is an ideas list for projects. The GSoC guide has a Writing a 
> Good Ideas List
> section. 
>
> > Projects should take ~175 hours or ~350 hours for GSoC contributors to 
> complete. 
>
> i.e. "short" or "long" projects. 
> https://google.github.io/gsocguides/mentor/defining-a-project-ideas-list
>
> I'm writing here *to solicit input on project ideas*. 
>
> I put "Technical Board?" in the subject because we're short a list of 
> project
> ideas for the technical direction of Django going forward, and maybe 
> thinking
> in terms of GSoC could be a way of bootstrapping that. The "?" is because 
> that's not 
> meant to exclude other input.
>
> Here's last year's list for reference: 
> https://code.djangoproject.com/wiki/SummerOfCode2022
>
> - Some of those were done: benchmarking (but that could be built on) and 
> per-instance 
>   field lookups.
>
> - Rate-limiting is a no-go I think: we couldn't come to any decent 
> agreement on scope, 
>   so it's better to live as a third-party package. 
>
> - I've tried to include folks from the wider ecosystem in previous years. 
> Two years ago 
>   we had both Wagtail and django-stubs projects. Wagtail then (last year)
>   applied in their own right, 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 cells into action? 🙂
>
>
> Thanks. 
>
> 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 django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/58bf890d-28be-49b2-827e-a7cbe1f9587en%40googlegroups.com.

Proposal for a "contained_by_any" PostgreSQL lookup

[Niccolò Mineo]

How would you see adding a lookup allowing "X <@ ANY(Y)" in 
contrib.postgres?

-- 
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/61f07669-b40d-4199-b740-984429184454n%40googlegroups.com.

Proposal for an "Unnest" ORM function

[Niccolò Mineo]

How would you see adding the "UNNEST" PostgreSQL and Oracle functions to 
the current set of ORM functions?

-- 
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/76d3a1d8-76ab-45b5-ac81-ece80737767an%40googlegroups.com.

Proposal for an "Age" PostgreSQL ORM function

[Niccolò Mineo]

How would you see adding the "AGE" function to the current set of 
PostgreSQL ORM functions?

-- 
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/0d862afe-e940-4ae6-9832-42159250aac5n%40googlegroups.com.

Proposal for a "ToTimestamp" PostgreSQL ORM function

[Niccolò Mineo]

How would you see adding the "TO_TIMESTAMP" function to the current set of 
PostgreSQL ORM functions?

-- 
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/8f21875c-390b-4298-a619-b25b645e548an%40googlegroups.com.

Proposal for a "RegExpMatches" PostgreSQL ORM function

[Niccolò Mineo]

How would you see adding the "REGEXP_MATCHES" function to the current set 
of PostgreSQL ORM functions?

-- 
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/2905bb55-0a91-4000-bd25-624f06eff24bn%40googlegroups.com.

Re: Proposal for a "RegExpMatches" PostgreSQL ORM function

[Tim Graham]

Hi, please consolidate your proposal when your ideas are complete. There's 
no need to start a separate thread for every function. Also, please search 
this mailing list and ticket tracker for past discussions that might be 
relevant. A quick search turned up at least 
https://groups.google.com/g/django-developers/c/jHhzEmZk4xE/m/_EErl1GGDAAJ 
and https://code.djangoproject.com/ticket/28805 (Add database functions for 
regular expressions, e.g. RegexpReplace) which duplicates this proposal.

On Tuesday, January 17, 2023 at 11:41:26 AM UTC-5 niccol...@gmail.com wrote:

> How would you see adding the "REGEXP_MATCHES" function to the current set 
> of PostgreSQL ORM functions?
>

-- 
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/e4e678fe-3a89-4729-8e9b-008af20ddf5an%40googlegroups.com.

Request for Guidance

['Gairick52' via Django developers (Contributions to Django itself)]

  Hello sir, i am Gairick a second year MCA student and want to contribute ,can you please point to me some resources by reading i can contribute to codebase and learn new technologies and please share me the guide for installation Regards,Gairick  Virus-free.www.avast.com 


DisclaimerThis email is governed by the Disclaimer Terms of  somaiya.edu which may be viewed at https://www.somaiya.edu/en/email-disclaimerFinally, please do not print this email unless it is necessary. Every unprinted email helps the environment.



-- 
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/B95C3F85-61CC-4644-871F-E00363318A22%40hxcore.ol.

Re: Request for Guidance

[Tim Graham]

Hello, please take a look at 
https://docs.djangoproject.com/en/dev/internals/contributing/new-contributors/ 
to find advice for new contributors.

On Tuesday, January 17, 2023 at 2:07:02 PM UTC-5 gair...@somaiya.edu wrote:

>  
>
>  
>
> Hello sir, i am Gairick a second year MCA student and want to contribute 
> ,can you please point to me some resources by reading i can contribute to 
> codebase and learn new technologies and please share me the guide for 
> installation 
>
> Regards,
>
> Gairick
>
>  
>
>  
>
>
> 
>  
> Virus-free.www.avast.com 
> 
>  
> <#m_-5157259906153594593_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
> Disclaimer
> This email is governed by the Disclaimer Terms of  somaiya.edu which may 
> be viewed at https://www.somaiya.edu/en/email-disclaimer
>
> Finally, please do not print this email unless it is necessary. Every 
> unprinted email helps the environment.
>
>

-- 
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/7add6b7e-c4fc-44d1-8259-498be3f37b9fn%40googlegroups.com.

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

[Manav Agarwal]

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:23 PM Carlton Gibson 
wrote:

> Hi All!
>
> Thanks for your earlier replies, comments and ideas!
>
> The organisation application period for GSoC begins next week, so I've
> pulled them together to begin the ideas page:
>
> https://code.djangoproject.com/wiki/SummerOfCode2023
>
> It's not 100% — not least I need to go over the WIKI formatting, and make
> it consistent (but ignore that, or make clean ups :)
> *Please have a look *— see if the descriptions make sense.
> (I want to add a few more links and such, and tweak the descriptions —
> again, happy to take edits :)
>
> If you suggested an idea I put you as a *Possible Mentor*.
> That doesn't mean you're committed to anything — but equally we do need
> mentors… :)
> What's involved? Not too much: being available to comment on a PR on your
> project is the main bit.
> If you know you're not happy to mentor, you can remove yourself: if you're
> the 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 at 10:11:45 UTC+1 Carlton Gibson wrote:
>
>> Hi all.
>>
>> Google Summer of Code (GSoC) for 2023 has just been announced.
>>
>> https://opensource.googleblog.com/2022/11/get-ready-for-google-summer-of-code-2023.html
>>
>> Django has participated many times, and it's been a real boon. Recent
>> successes include:
>>
>> * The django-stubs mypy plugin.
>> * The cross-db JSON field.
>> * The Redis cache backend.
>> * Per model-class (field instance) custom lookups
>> * Setup of the django-asv benchmarking project.
>> * ...
>>
>> Application deadline for Orgs is February 7. I'll begin working on it
>> after the New Year.
>>
>> Main bit is an ideas list for projects. The GSoC guide has a Writing a
>> Good Ideas List
>> section.
>>
>> > Projects should take ~175 hours or ~350 hours for GSoC contributors to
>> complete.
>>
>> i.e. "short" or "long" projects.
>> https://google.github.io/gsocguides/mentor/defining-a-project-ideas-list
>>
>> I'm writing here *to solicit input on project ideas*.
>>
>> I put "Technical Board?" in the subject because we're short a list of
>> project
>> ideas for the technical direction of Django going forward, and maybe
>> thinking
>> in terms of GSoC could be a way of bootstrapping that. The "?" is because
>> that's not
>> meant to exclude other input.
>>
>> Here's last year's list for reference:
>> https://code.djangoproject.com/wiki/SummerOfCode2022
>>
>> - Some of those were done: benchmarking (but that could be built on) and
>> per-instance
>>   field lookups.
>>
>> - Rate-limiting is a no-go I think: we couldn't come to any decent
>> agreement on scope,
>>   so it's better to live as a third-party package.
>>
>> - I've tried to include folks from the wider ecosystem in previous years.
>> Two years ago
>>   we had both Wagtail and django-stubs projects. Wagtail then (last year)
>>   applied in their own right, 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 cells into action? 🙂
>>
>>
>> Thanks.
>>
>> 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 django-developers+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/58bf890d-28be-49b2-827e-a7cbe1f9587en%40googlegroups.com
> 
> .
>


-- 
Regards
Manav Agarwal

[image: https://www.linkedin.com/in/manav-agarwal-982553190/]


*"If your actions inspire others to dream more, learn more, do more and
become more, you are a leader.”*

-- 
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/CACbxD0CRGU_Wh_mabK8FBREYwg4TtmCheNc2kcx45K4KATDf6A%40mail.gmail.com.

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

[Carlton Gibson]

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:23 PM Carlton Gibson 
> wrote:
>
>> Hi All!
>>
>> Thanks for your earlier replies, comments and ideas!
>>
>> The organisation application period for GSoC begins next week, so I've
>> pulled them together to begin the ideas page:
>>
>> https://code.djangoproject.com/wiki/SummerOfCode2023
>>
>> It's not 100% — not least I need to go over the WIKI formatting, and make
>> it consistent (but ignore that, or make clean ups :)
>> *Please have a look *— see if the descriptions make sense.
>> (I want to add a few more links and such, and tweak the descriptions —
>> again, happy to take edits :)
>>
>> If you suggested an idea I put you as a *Possible Mentor*.
>> That doesn't mean you're committed to anything — but equally we do need
>> mentors… :)
>> What's involved? Not too much: being available to comment on a PR on your
>> project is the main bit.
>> If you know you're not happy to mentor, you can remove yourself: if
>> you're the 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 at 10:11:45 UTC+1 Carlton Gibson wrote:
>>
>>> Hi all.
>>>
>>> Google Summer of Code (GSoC) for 2023 has just been announced.
>>>
>>> https://opensource.googleblog.com/2022/11/get-ready-for-google-summer-of-code-2023.html
>>>
>>> Django has participated many times, and it's been a real boon. Recent
>>> successes include:
>>>
>>> * The django-stubs mypy plugin.
>>> * The cross-db JSON field.
>>> * The Redis cache backend.
>>> * Per model-class (field instance) custom lookups
>>> * Setup of the django-asv benchmarking project.
>>> * ...
>>>
>>> Application deadline for Orgs is February 7. I'll begin working on it
>>> after the New Year.
>>>
>>> Main bit is an ideas list for projects. The GSoC guide has a Writing a
>>> Good Ideas List
>>> section.
>>>
>>> > Projects should take ~175 hours or ~350 hours for GSoC contributors to
>>> complete.
>>>
>>> i.e. "short" or "long" projects.
>>> https://google.github.io/gsocguides/mentor/defining-a-project-ideas-list
>>>
>>> I'm writing here *to solicit input on project ideas*.
>>>
>>> I put "Technical Board?" in the subject because we're short a list of
>>> project
>>> ideas for the technical direction of Django going forward, and maybe
>>> thinking
>>> in terms of GSoC could be a way of bootstrapping that. The "?" is
>>> because that's not
>>> meant to exclude other input.
>>>
>>> Here's last year's list for reference:
>>> https://code.djangoproject.com/wiki/SummerOfCode2022
>>>
>>> - Some of those were done: benchmarking (but that could be built on) and
>>> per-instance
>>>   field lookups.
>>>
>>> - Rate-limiting is a no-go I think: we couldn't come to any decent
>>> agreement on scope,
>>>   so it's better to live as a third-party package.
>>>
>>> - I've tried to include folks from the wider ecosystem in previous
>>> years. Two years ago
>>>   we had both Wagtail and django-stubs projects. Wagtail then (last year)
>>>   applied in their own right, 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 cells into action? 🙂
>>>
>>>
>>> Thanks.
>>>
>>> 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 django-developers+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/django-developers/58bf890d-28be-49b2-827e-a7cbe1f9587en%40googlegroups.com
>> 
>> .
>>
>
>
> --
> Regards
> Manav Agarwal
>
> [image: https://www.linkedin.com/in/manav-agarwal-982553190/]
> 
>
> *"If your actions inspire others to dream more, learn more, do more and
> become more, you are a leader.”*
>
> --
> 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