Re: Help for GSoC proposal (Formset improvements)

[PARTH PATIL]

Thanks for your help 

-- 
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 post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/ad7f8ce0-454a-45a0-9401-df3a17e50848%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Django 2.1 default of samesite=Lax for Session and CSRF cookies cause issues on Safari 12

[Flávio Junior]

So new iOS and Mac minor versions were launched, but issue is still there.
Created a new bug ticket on Webkit and they're being able to reproduce 
better the problem: https://bugs.webkit.org/show_bug.cgi?id=196375
Hope they can reach a solution soon!

Florian, you mean a blog post on Django's blog or anywhere else?

On Tuesday, March 19, 2019 at 5:58:01 AM UTC-3, Florian Apolloner wrote:
>
>
>
> On Monday, March 18, 2019 at 10:50:17 PM UTC+1, Flávio Junior wrote:
>>
>> What are the next steps?
>> A warning at the docs for these settings? 
>>
>
> I guess that is the big question. We'd have to remove the warning 
> "soonish" again I guess once safari is fixed (after all one wants the added 
> security benefit). Maybe a blog post? 
>

-- 
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 post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/aebf5595-33e0-4ad2-b247-8db0366bb308%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GSoC Proposal

[Sage M.A.]

Thank you! I'll share my proposal here when I'm done with my first draft.

On Thursday, 28 March 2019 21:49:36 UTC+7, Carlton Gibson wrote:
>
> Hi Sage. 
>
> Yes. It never hurts to apply. If we get two good proposals for the same 
> project, we can find a way to share or another project. 
> We can cross that bridge as and when we come to it. 
> ("Scale later" )
>
> Kind Regards,
>
> Carlton
>
>
> On Thursday, 28 March 2019 14:58:15 UTC+1, Sage M.A. wrote:
>>
>> Hi everyone,
>> Sorry to ask this, but can I also take a shot in this one? I've been 
>> interested in this issue since early February.
>>
>> On Thursday, 21 March 2019 22:28:41 UTC+7, Carlton Gibson wrote:
>>>
>>> Also, sorry, this was the key thread here, plus links therein 
>>> https://groups.google.com/d/topic/django-developers/zfred27yVPg/discussion
>>>
>>> On Thursday, 21 March 2019 16:27:14 UTC+1, Carlton Gibson wrote:

 Hey Marcio. 

 If you can demonstrate that your abilities are sufficient in your 
 proposal, I'm sure we can mentor you through the pull request bit. (It's 
 just "contributor" implies knowledge of the internals, and the ORM **is** 
 the scariest bit, so... it's a bit  this close to starting.) 

 You've read the contributing guide right, and had a mooch around? Jump 
 in! https://docs.djangoproject.com/en/dev/internals/contributing/


 On the Timeline 
  applications 
 go from 25/3 to 9/4 so there's time to work on a draft, but Tim's right, 
 we 
 do need that effort. 

 Standout areas for me:

 1. So we ship a JSONField. With SQLite in mind, most people can't use 
 it, so we need a How-To of some kind on compiling SQLite   with the json1 
 extension and putting it in the right place so Python can find it. 
 2. For the SQLite PoC, I'd like to see a more aggressive timeline right 
 at the beginning. The base field with save and load shouldn't be Too Hard™ 
 (c.f. jsonb.py 
 
 )

 The issue is (3) the lookups and how to handle integrating those with 
 the existing postgres ones, the MySQL package and, the Oracle example. 
 A decent sketch of an answer there and we have a proposal I think. 
  (Maybe it's an simple as `as_sqlite()`, `as_oralce()` etc, as with the 
 existing functions implementations, but...) 

 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 post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/5bc96405-f23c-4c6b-9580-767fd9710da1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GSoC Proposal

[Carlton Gibson]

Hi Sage. 

Yes. It never hurts to apply. If we get two good proposals for the same 
project, we can find a way to share or another project. 
We can cross that bridge as and when we come to it. 
("Scale later" )

Kind Regards,

Carlton


On Thursday, 28 March 2019 14:58:15 UTC+1, Sage M.A. wrote:
>
> Hi everyone,
> Sorry to ask this, but can I also take a shot in this one? I've been 
> interested in this issue since early February.
>
> On Thursday, 21 March 2019 22:28:41 UTC+7, Carlton Gibson wrote:
>>
>> Also, sorry, this was the key thread here, plus links therein 
>> https://groups.google.com/d/topic/django-developers/zfred27yVPg/discussion
>>
>> On Thursday, 21 March 2019 16:27:14 UTC+1, Carlton Gibson wrote:
>>>
>>> Hey Marcio. 
>>>
>>> If you can demonstrate that your abilities are sufficient in your 
>>> proposal, I'm sure we can mentor you through the pull request bit. (It's 
>>> just "contributor" implies knowledge of the internals, and the ORM **is** 
>>> the scariest bit, so... it's a bit  this close to starting.) 
>>>
>>> You've read the contributing guide right, and had a mooch around? Jump 
>>> in! https://docs.djangoproject.com/en/dev/internals/contributing/
>>>
>>>
>>> On the Timeline 
>>>  applications 
>>> go from 25/3 to 9/4 so there's time to work on a draft, but Tim's right, we 
>>> do need that effort. 
>>>
>>> Standout areas for me:
>>>
>>> 1. So we ship a JSONField. With SQLite in mind, most people can't use 
>>> it, so we need a How-To of some kind on compiling SQLite   with the json1 
>>> extension and putting it in the right place so Python can find it. 
>>> 2. For the SQLite PoC, I'd like to see a more aggressive timeline right 
>>> at the beginning. The base field with save and load shouldn't be Too Hard™ 
>>> (c.f. jsonb.py 
>>> 
>>> )
>>>
>>> The issue is (3) the lookups and how to handle integrating those with 
>>> the existing postgres ones, the MySQL package and, the Oracle example. 
>>> A decent sketch of an answer there and we have a proposal I think. 
>>>  (Maybe it's an simple as `as_sqlite()`, `as_oralce()` etc, as with the 
>>> existing functions implementations, but...) 
>>>
>>> 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 post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/b946345f-a7c9-4653-a909-6ae4d998cc1e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GSoC Proposal

[Sage M.A.]

Hi everyone,
Sorry to ask this, but can I also take a shot in this one? I've been 
interested in this issue since early February.

On Thursday, 21 March 2019 22:28:41 UTC+7, Carlton Gibson wrote:
>
> Also, sorry, this was the key thread here, plus links therein 
> https://groups.google.com/d/topic/django-developers/zfred27yVPg/discussion
>
> On Thursday, 21 March 2019 16:27:14 UTC+1, Carlton Gibson wrote:
>>
>> Hey Marcio. 
>>
>> If you can demonstrate that your abilities are sufficient in your 
>> proposal, I'm sure we can mentor you through the pull request bit. (It's 
>> just "contributor" implies knowledge of the internals, and the ORM **is** 
>> the scariest bit, so... it's a bit  this close to starting.) 
>>
>> You've read the contributing guide right, and had a mooch around? Jump 
>> in! https://docs.djangoproject.com/en/dev/internals/contributing/
>>
>>
>> On the Timeline 
>>  applications 
>> go from 25/3 to 9/4 so there's time to work on a draft, but Tim's right, we 
>> do need that effort. 
>>
>> Standout areas for me:
>>
>> 1. So we ship a JSONField. With SQLite in mind, most people can't use it, 
>> so we need a How-To of some kind on compiling SQLite   with the json1 
>> extension and putting it in the right place so Python can find it. 
>> 2. For the SQLite PoC, I'd like to see a more aggressive timeline right 
>> at the beginning. The base field with save and load shouldn't be Too Hard™ 
>> (c.f. jsonb.py 
>> 
>> )
>>
>> The issue is (3) the lookups and how to handle integrating those with the 
>> existing postgres ones, the MySQL package and, the Oracle example. 
>> A decent sketch of an answer there and we have a proposal I think. 
>>  (Maybe it's an simple as `as_sqlite()`, `as_oralce()` etc, as with the 
>> existing functions implementations, but...) 
>>
>> 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 post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/bf8de3b1-a444-40ce-8c9b-8397cd0eab5b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Help for GSoC proposal (Formset improvements)

[Carlton Gibson]

Hi Parth, 

Yes, something along those lines will be right. 

First-off, what are the existing work-arounds (i.e. how are people handling 
this in the wild: overriding `__init__()` methods etc...) — can these be 
summarised and documented, where worth recommending?

Then, API changes to improve on that situation, like passing in request 
objects. (From experience with DRF and django-filter, making the request 
available solves **most** issues for **most** users — "But I need X! — But 
that's just `request.X`" 9 times out of 10.) 

THEN, look at open accepted issues on Forms 
.
 
There are ≈70. Begin with FormSets issues, then spread out. Which are 
related? (#10403?) Which can you target? You don't have to solve them all 
(!) but a good goal for a 12 week project would be to become a total expert 
on django.forms, and to have handled a number of issues as part of that. 

HTH.

Kind Regards,

Carlton


On Tuesday, 26 March 2019 18:56:56 UTC+1, PARTH PATIL wrote:
>
> I was planning  to do the "Formset Improvements 
> " 
> project in GSoC. I would need some more explanation on what is expected as 
> nothing was clearly mentioned there.
> You can link the related tickets or elaborate on what is needed that would 
> be helpful.
>
> I dug a little bit deeper into this. and found some related issues 1 
> 
>  
> | 2. 
> 
>
> I'm planning to add a request variable in the BaseFormSet Class 
> 
>  
> and then handle it such that it will be available within every form (not 
> completely polished till now).
>
>1. Is this a good approach?
>2. Will this solve the problem? (If not please mention the problems 
>which will not be solved
>
> I am also looking for some additional features that maybe added to formset 
> so am open for suggestions.
> I'm currently in middle of making the abstract so before moving forward i 
> would like to get some confirmation that this is correct approach. Thank you
>

-- 
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 post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/739596dd-772d-42ac-808e-32c670b8b683%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.