Re: Request for closing #25139 -- ModelFormSet: allow swapping unique values

[PARTH PATIL]

Yup sounds right. 

On Thursday, August 15, 2019 at 3:13:23 PM UTC+5:30, Carlton Gibson wrote:
>
> Hi Parth. 
>
> Thanks for looking at this. I think you're right that there's no (suitably 
> obvious at least to me) simple way of solving this. I guess that's why it's 
> sat there for 4 years. 🙂
>
> What would it take: fetching the set of to_be_unique values and comparing 
> it to the set of values submitted and then assigning both within a 
> transaction... — meh, possible but I'm not sure it'd be clean, or something 
> we'd want to bundle in even if we had the solution available, vs, putting 
> it in a third-party package...
>
> Anyhow, I'll bump it to Someday/Maybe for now. If someone pops up with a 
> solution we can look at that then. 
>
> Kind Regards,
>
> Carlton
>
>
> On Sunday, 11 August 2019 09:20:49 UTC+2, PARTH PATIL wrote:
>>
>> Hey can someone please have look at this ticket, I feel the requested 
>> feature is not really feasible to implement, also it's not applicable in 
>> the general case.
>>
>> I don't think so this is feasible, this will require n(n-1)/2 comparisons 
>> to determine whether any two of the models are swapped.
>> This looks easy in the above case but won't be a good idea for a general 
>> case.
>>
>> Correct me if I'm wrong or if anyone has a better approach for 
>> implementation of this feature. I would like to work on it.
>>
>> But as of now, I feel this ticket should be closed
>>
>>
>> Here is a link to the ticket 
>> <https://code.djangoproject.com/ticket/25139>
>>
>

-- 
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/7892adb1-908c-4cb3-b059-ba8454982f26%40googlegroups.com.

Request for closing #25139 -- ModelFormSet: allow swapping unique values

[PARTH PATIL]

Hey can someone please have look at this ticket, I feel the requested 
feature is not really feasible to implement, also it's not applicable in 
the general case.

I don't think so this is feasible, this will require n(n-1)/2 comparisons 
to determine whether any two of the models are swapped.
This looks easy in the above case but won't be a good idea for a general 
case.

Correct me if I'm wrong or if anyone has a better approach for 
implementation of this feature. I would like to work on it.

But as of now, I feel this ticket should be closed


Here is a link to the ticket 

-- 
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/61c73eca-c618-4c11-b5e6-6feaf407e8e6%40googlegroups.com.

How to test whether a formset instance is properly initialized

[PARTH PATIL]

I'm currently working on ticket #10403 
 -- Declarative syntax for 
Formsets

How to test whether a formset instance is correctly initialized??

The thing which I'm trying to achieve is to initiate a formset without 
using formset_factory(). I'm able to create objects of class derived from 
the BaseFormSet, but its really difficult for me to check whether it is 
properly initiated or not as expected from a formset instance.

Should I write tests for this??
And if yes, which all parameter values should I assert in the test to 
conclude that my formset instance is indistinguishable from the one created 
using formset_factory.

Also is there any better way to test this? I'm currently using a python 
shell to create objects and then check manually its attributes, etc. which 
I know is not a good way. 

-- 
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/583effcf-041e-4d30-9693-62a8f9559901%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GSoC Proposal (FormSet Improvement)

[PARTH PATIL]

Thank you, Asif.

And yes surely I would like to take forward your work, and it will surely
help me in my project.

On Tue, May 7, 2019 at 6:58 PM Asif Saif Uddin  wrote:

> Congrats Parth. It would be great If your contributions could be accepted
> in the next versions of django, I have some od works related to declarative
> formsets. I will clean them up and bring to you so that you can move that
> forward with mentors/communities help.
> Best of luck.
>
> On Tuesday, May 7, 2019 at 7:15:45 PM UTC+6, PARTH PATIL wrote:
>>
>> Hello everyone,
>>
>> I would like to thank everyone here and everyone who helped me to improve
>> my project idea. This project has been accepted and I will try my best to
>> completewhatvI have promised.
>>
>> I was wondering what is the next step? Are there any kind of formalities
>> to be completed?
>>
>> Best Regards,
>> PARTH PATIL
>>
>> On Mon, 8 Apr 2019, 3:05 am PARTH PATIL,  wrote:
>>
>>> I have done some MAJOR changes/improvements to my proposal please have a
>>> look. I have added technical description and addressed more issues related
>>> to the forrmsets. Suggest any changes if needed.
>>>
>>>
>>>
>>> On Saturday, April 6, 2019 at 10:38:42 PM UTC+5:30, Asif Saif Uddin
>>> wrote:
>>>>
>>>> I will try to come up with an initial step for that hopefully by
>>>> tomorrow. In the meantime, I hope you will keep trying to improve your
>>>> proposal by analyzing open form/formset related issues, some of whom you
>>>> could try to fix to get more insight.
>>>>
>>>> On Saturday, April 6, 2019 at 10:30:02 PM UTC+6, PARTH PATIL wrote:
>>>>>
>>>>> Sure that would be nice, as I even mentioned in my abstract I
>>>>> definitely need help for that one.
>>>>>
>>>>> On Saturday, April 6, 2019 at 8:59:01 PM UTC+5:30, Asif Saif Uddin
>>>>> wrote:
>>>>>>
>>>>>> Regarding the declarative syntax, I might share some insights later
>>>>>> with you.
>>>>>>
>>>>>> On Tuesday, April 2, 2019 at 1:29:33 AM UTC+6, PARTH PATIL wrote:
>>>>>>>
>>>>>>> Here is a link to my GSoC proposal
>>>>>>> Its a first draft so you are open to comment and suggest changes
>>>>>>>
>>>>>>>
>>>>>>> https://docs.google.com/document/d/1JuoVOU5xMwXY7JrHJshezIyuIpFfoEM49rO3e0rfNhE/edit?usp=sharing
>>>>>>>
>>>>>>>
>>>>>>> Best Regards,
>>>>>>>
>>>>>>> PARTH PATIL
>>>>>>>
>>>>>>> SOFTWARE DEVELOPER, AUV-IITB
>>>>>>>
>>>>>>> CONVENOR, ELECTRONICS & ROBOTICS CLUB IIT BOMBAY.
>>>>>>>
>>>>>>> [image: Image result for FACEBOOK ROUND ICON]
>>>>>>> <https://www.facebook.com/parth.patil.77> [image: Image result for
>>>>>>> instagram ROUND ICON] <https://www.instagram.com/code_blooded18/> 
>>>>>>> [image:
>>>>>>> Image result for linkedin ROUND ICON]
>>>>>>> <https://www.linkedin.com/in/parth-patil-256291117/>
>>>>>>>
>>>>>>> --
>>> 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-d...@googlegroups.com.
>>> To post to this group, send email to django-d...@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/8b9f7237-db7a-4bcb-949a-03197382eeb0%40googlegroups.com
>>> <https://groups.google.com/d/msgid/django-developers/8b9f7237-db7a-4bcb-949a-03197382eeb0%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> 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/d2d55010-6032-4467-be66-3bc94e04731e%40googlegroups.com
> <https://groups.google.com/d/msgid/django-developers/d2d55010-6032-4467-be66-3bc94e04731e%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAJSC-ifJ7%3DY2GrFZLtaJhGNOv4bT-CB1eKBr9ZRY_NxVAp3ASw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: GSoC Proposal (FormSet Improvement)

[PARTH PATIL]

Hello everyone,

I would like to thank everyone here and everyone who helped me to improve
my project idea. This project has been accepted and I will try my best to
completewhatvI have promised.

I was wondering what is the next step? Are there any kind of formalities to
be completed?

Best Regards,
PARTH PATIL

On Mon, 8 Apr 2019, 3:05 am PARTH PATIL,  wrote:

> I have done some MAJOR changes/improvements to my proposal please have a
> look. I have added technical description and addressed more issues related
> to the forrmsets. Suggest any changes if needed.
>
>
>
> On Saturday, April 6, 2019 at 10:38:42 PM UTC+5:30, Asif Saif Uddin wrote:
>>
>> I will try to come up with an initial step for that hopefully by
>> tomorrow. In the meantime, I hope you will keep trying to improve your
>> proposal by analyzing open form/formset related issues, some of whom you
>> could try to fix to get more insight.
>>
>> On Saturday, April 6, 2019 at 10:30:02 PM UTC+6, PARTH PATIL wrote:
>>>
>>> Sure that would be nice, as I even mentioned in my abstract I definitely
>>> need help for that one.
>>>
>>> On Saturday, April 6, 2019 at 8:59:01 PM UTC+5:30, Asif Saif Uddin wrote:
>>>>
>>>> Regarding the declarative syntax, I might share some insights later
>>>> with you.
>>>>
>>>> On Tuesday, April 2, 2019 at 1:29:33 AM UTC+6, PARTH PATIL wrote:
>>>>>
>>>>> Here is a link to my GSoC proposal
>>>>> Its a first draft so you are open to comment and suggest changes
>>>>>
>>>>>
>>>>> https://docs.google.com/document/d/1JuoVOU5xMwXY7JrHJshezIyuIpFfoEM49rO3e0rfNhE/edit?usp=sharing
>>>>>
>>>>>
>>>>> Best Regards,
>>>>>
>>>>> PARTH PATIL
>>>>>
>>>>> SOFTWARE DEVELOPER, AUV-IITB
>>>>>
>>>>> CONVENOR, ELECTRONICS & ROBOTICS CLUB IIT BOMBAY.
>>>>>
>>>>> [image: Image result for FACEBOOK ROUND ICON]
>>>>> <https://www.facebook.com/parth.patil.77> [image: Image result for
>>>>> instagram ROUND ICON] <https://www.instagram.com/code_blooded18/> [image:
>>>>> Image result for linkedin ROUND ICON]
>>>>> <https://www.linkedin.com/in/parth-patil-256291117/>
>>>>>
>>>>> --
> 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/8b9f7237-db7a-4bcb-949a-03197382eeb0%40googlegroups.com
> <https://groups.google.com/d/msgid/django-developers/8b9f7237-db7a-4bcb-949a-03197382eeb0%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAJSC-icamh40Yj843Vi_ngXhd0X5L2DAbO%3D%3D6MN2ZPMysqJWDA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Force "required" fields to be included in a ModelForm

[PARTH PATIL]

Yes I agree with others, that this should not be implemented. As I find
this too much specific to just your case.

There are many cases, like what if there is some required field which the
developer wants to set by themselves and don't want user to edit that
(transaction details maybe for a shopping site).

You may Inherit a class from modelform and overide the behaviour for your
project, buy I dont think this should be included in Django.

Best Regards,
PARTH PATIL


On Wed, 17 Apr 2019, 12:15 pm Harro,  wrote:

> I'm against, there are lots of cases where a modelform is used to edit an
> exitsting object and thus the required fields are already set and you don't
> want them to be editable.
>
> If it's a trivial patch then you should think about extending modelform in
> your own project enforce it there and then use it instead of the normal
> modelform.
>
> I also think a good test setup/protocol will catch missing fields pretty
> quickly as you won't be able to actually create the object.
>
> On Wednesday, 17 April 2019 02:34:12 UTC+2, Will Gordon wrote:
>>
>> In the same way that editable fields are forced to not be included in a
>> ModelForm (
>> https://github.com/django/django/blob/master/django/forms/models.py#L146),
>> I would like to propose that "required" fields (`blank=False`) be forced to
>> be included in a ModelForm.
>>
>> While I understand that a developer can force this inclusion themselves,
>> but on a large project, it should not be necessary to always ensure that a
>> Model and ModelForm are in sync.
>>
>> Since this is probably a non-trivial patch (
>> https://docs.djangoproject.com/en/dev/internals/contributing/writing-code/submitting-patches/#non-trivial-patches)
>> I need to provide evidence that this has been discussed. As such, I'm open
>> to any and all opinions!
>>
> --
> 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/a51d1c72-c724-448f-b804-344cb33d176f%40googlegroups.com
> <https://groups.google.com/d/msgid/django-developers/a51d1c72-c724-448f-b804-344cb33d176f%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAJSC-ifeKKX0zp1F48dm%3DQSRe%2BBds4r4_nM_0fn3ih9CpTVQUw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Help for GSoC proposal (Formset improvements)

[PARTH PATIL]

I researched a bit on FormWizards, and what I felt is that it is 
oriented more towards the idea of multiple form submission similar to that 
of Google forms where we have multiple pages. 

I was thinking of creating a *FormSetContainer* which would be like a 
collection instance of different Forms, FormSets. or FormSetContainers 
themselves. It would be oriented more towards how we handle it in the 
backend, like the saving process, validation, etc rather than the 
frontend side. And the FormWizard View may be revived to display the 
FormContainer.

This would be another level of abstraction over the FormSet and can be 
helpful in the case where the user needs to get data for different model 
objects at once.

Please comment on need and feasibility of this. 


On Monday, April 8, 2019 at 11:54:57 AM UTC+5:30, Carlton Gibson wrote:
>
> Hi Parth. 
>
> Well, the wizard (&co) got moved out to it's own app 
> https://django-formtools.readthedocs.io/en/latest/
> But yes, there's no reason why this sort of thing wouldn't potentially in 
> scope. 
>
> Kind Regards,
>
> Carlton
>
>
> On Sunday, 7 April 2019 23:47:23 UTC+2, PARTH PATIL wrote:
>>
>> (Sorry I typed the incomplete message in the last post)
>>
>> I came across this ticket while going over the feature list of Forms and 
>> Formsets (# 18830 <https://code.djangoproject.com/ticket/18830>)
>>
>> Feature requested in this thicket is something like
>>
>> *FormWizard:*
>> * It will be like a container which can have forms, formsets, and 
>> formwizards itself.*
>>  
>>
>>1. Is this kind of feature still required?
>>2. Will this be a good addition to the Form?
>>3. Should I mention this in my proposal, as there is few time left 
>>for the final submission I may not be able to draft it properly?
>>
>> The possible use of this will be to attach different forms in an HTML and 
>> this form wizard will handle saving, etc of the forms. I was thinking of 
>> keeping something like a management form similar to formset which will 
>> handle the individual object and ensure which fields correspond to which 
>> form/formset element within the wizard.
>>
>>
>>
>> On Tuesday, March 26, 2019 at 11:26:56 PM UTC+5:30, PARTH PATIL wrote:
>>>
>>> I was planning  to do the "Formset Improvements 
>>> <https://code.djangoproject.com/wiki/SummerOfCode2019#Formsetimprovements>" 
>>> 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 
>>> <https://stackoverflow.com/questions/622982/django-passing-custom-form-parameters-to-formset>
>>>  
>>> | 2. 
>>> <https://stackoverflow.com/questions/52269308/django-unable-to-pass-request-to-form-while-using-formset-produces-init>
>>>
>>> I'm planning to add a request variable in the BaseFormSet Class 
>>> <https://github.com/Parth1811/django/blob/8ec7ded3706fe66bf307ed339eb852d73f6d10d0/django/forms/formsets.py#L46-L61>
>>>  
>>> 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/1fbb3ac2-c66a-413b-b409-ba0856fa1cb2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Help for GSoC proposal (Formset improvements)

[PARTH PATIL]

(Sorry I typed the incomplete message in the last post)

I came across this ticket while going over the feature list of Forms and 
Formsets (# 18830 <https://code.djangoproject.com/ticket/18830>)

Feature requested in this thicket is something like

*FormWizard:*
* It will be like a container which can have forms, formsets, and 
formwizards itself.*
 

   1. Is this kind of feature still required?
   2. Will this be a good addition to the Form?
   3. Should I mention this in my proposal, as there is few time left for 
   the final submission I may not be able to draft it properly?

The possible use of this will be to attach different forms in an HTML and 
this form wizard will handle saving, etc of the forms. I was thinking of 
keeping something like a management form similar to formset which will 
handle the individual object and ensure which fields correspond to which 
form/formset element within the wizard.



On Tuesday, March 26, 2019 at 11:26:56 PM UTC+5:30, PARTH PATIL wrote:
>
> I was planning  to do the "Formset Improvements 
> <https://code.djangoproject.com/wiki/SummerOfCode2019#Formsetimprovements>" 
> 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 
> <https://stackoverflow.com/questions/622982/django-passing-custom-form-parameters-to-formset>
>  
> | 2. 
> <https://stackoverflow.com/questions/52269308/django-unable-to-pass-request-to-form-while-using-formset-produces-init>
>
> I'm planning to add a request variable in the BaseFormSet Class 
> <https://github.com/Parth1811/django/blob/8ec7ded3706fe66bf307ed339eb852d73f6d10d0/django/forms/formsets.py#L46-L61>
>  
> 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/0e6fe881-ea44-41b4-99e5-190841e66e20%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Help for GSoC proposal (Formset improvements)

[PARTH PATIL]

I came across this ticket while going over the feature list of Forms and 
Formsets (# 18830 <https://code.djangoproject.com/ticket/18830>)

Feature requested in this thicket is something like

*FormWizard:*
* It will be like a container which can have forms, formsets, and 
formwizards itself.*




On Tuesday, March 26, 2019 at 11:26:56 PM UTC+5:30, PARTH PATIL wrote:
>
> I was planning  to do the "Formset Improvements 
> <https://code.djangoproject.com/wiki/SummerOfCode2019#Formsetimprovements>" 
> 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 
> <https://stackoverflow.com/questions/622982/django-passing-custom-form-parameters-to-formset>
>  
> | 2. 
> <https://stackoverflow.com/questions/52269308/django-unable-to-pass-request-to-form-while-using-formset-produces-init>
>
> I'm planning to add a request variable in the BaseFormSet Class 
> <https://github.com/Parth1811/django/blob/8ec7ded3706fe66bf307ed339eb852d73f6d10d0/django/forms/formsets.py#L46-L61>
>  
> 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/b5ed1b63-84f7-4acc-8633-6c72336f2f82%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GSoC Proposal (FormSet Improvement)

[PARTH PATIL]

I have done some MAJOR changes/improvements to my proposal please have a 
look. I have added technical description and addressed more issues related 
to the forrmsets. Suggest any changes if needed.



On Saturday, April 6, 2019 at 10:38:42 PM UTC+5:30, Asif Saif Uddin wrote:
>
> I will try to come up with an initial step for that hopefully by tomorrow. 
> In the meantime, I hope you will keep trying to improve your proposal by 
> analyzing open form/formset related issues, some of whom you could try to 
> fix to get more insight.
>
> On Saturday, April 6, 2019 at 10:30:02 PM UTC+6, PARTH PATIL wrote:
>>
>> Sure that would be nice, as I even mentioned in my abstract I definitely 
>> need help for that one.
>>
>> On Saturday, April 6, 2019 at 8:59:01 PM UTC+5:30, Asif Saif Uddin wrote:
>>>
>>> Regarding the declarative syntax, I might share some insights later with 
>>> you.
>>>
>>> On Tuesday, April 2, 2019 at 1:29:33 AM UTC+6, PARTH PATIL wrote:
>>>>
>>>> Here is a link to my GSoC proposal
>>>> Its a first draft so you are open to comment and suggest changes
>>>>
>>>>
>>>> https://docs.google.com/document/d/1JuoVOU5xMwXY7JrHJshezIyuIpFfoEM49rO3e0rfNhE/edit?usp=sharing
>>>>
>>>>
>>>> Best Regards,
>>>>
>>>> PARTH PATIL
>>>>
>>>> SOFTWARE DEVELOPER, AUV-IITB
>>>>
>>>> CONVENOR, ELECTRONICS & ROBOTICS CLUB IIT BOMBAY.
>>>>
>>>> [image: Image result for FACEBOOK ROUND ICON] 
>>>> <https://www.facebook.com/parth.patil.77> [image: Image result for 
>>>> instagram ROUND ICON] <https://www.instagram.com/code_blooded18/> [image: 
>>>> Image result for linkedin ROUND ICON] 
>>>> <https://www.linkedin.com/in/parth-patil-256291117/>
>>>>
>>>>

-- 
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/8b9f7237-db7a-4bcb-949a-03197382eeb0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GSoC Proposal (FormSet Improvement)

[PARTH PATIL]

Sure that would be nice, as I even mentioned in my abstract I definitely 
need help for that one.

On Saturday, April 6, 2019 at 8:59:01 PM UTC+5:30, Asif Saif Uddin wrote:
>
> Regarding the declarative syntax, I might share some insights later with 
> you.
>
> On Tuesday, April 2, 2019 at 1:29:33 AM UTC+6, PARTH PATIL wrote:
>>
>> Here is a link to my GSoC proposal
>> Its a first draft so you are open to comment and suggest changes
>>
>>
>> https://docs.google.com/document/d/1JuoVOU5xMwXY7JrHJshezIyuIpFfoEM49rO3e0rfNhE/edit?usp=sharing
>>
>>
>> Best Regards,
>>
>> PARTH PATIL
>>
>> SOFTWARE DEVELOPER, AUV-IITB
>>
>> CONVENOR, ELECTRONICS & ROBOTICS CLUB IIT BOMBAY.
>>
>> [image: Image result for FACEBOOK ROUND ICON] 
>> <https://www.facebook.com/parth.patil.77> [image: Image result for 
>> instagram ROUND ICON] <https://www.instagram.com/code_blooded18/> [image: 
>> Image result for linkedin ROUND ICON] 
>> <https://www.linkedin.com/in/parth-patil-256291117/>
>>
>>

-- 
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/5951644c-fe20-4c12-beff-462451681455%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GSoC Proposal (FormSet Improvement)

[PARTH PATIL]

I have updated my proposal please have a look

On Wednesday, April 3, 2019 at 9:22:57 PM UTC+5:30, Carlton Gibson wrote:
>
> Yes, just pseudo code — so when reviewing your proposal next week it's 
> easy to see that it'll be the right approach. 🙂
>
> On Wednesday, 3 April 2019 17:51:18 UTC+2, PARTH PATIL wrote:
>>
>>
>>
>> On Wednesday, April 3, 2019 at 8:58:26 PM UTC+5:30, Carlton Gibson wrote:
>>>
>>> Hey Parth. 
>>>
>>> Right. So, thanks for making the effort so far. Good. 
>>>
>>> Can you add more detail about yourself. You've not contributed to Django 
>>> right? So the concern at this point would be whether you're able to fulfil 
>>> the project. 
>>>
>>
>> I have contributed to Django (see #30189 
>> <https://code.djangoproject.com/ticket/30189>), I have mentioned it at 
>> the end of my proposal, I would try to highlight that. 
>>
>>  
>>
>>> What's your experience with Django? (and if you want to implement a 
>>> declarative formset syntax, Python more generally?)
>>> (Perhaps you said this, but it needs to be in the proposal.) 
>>>
>>
>> Sure I will add some of my projects in the proposal. 
>>
>>>
>>> You don't necessarily need to have ideas for the final code, but what 
>>> does e.g. the usage look like with your idea (i.e. adding the request 
>>> parameter)? 
>>> (So the formset gets the request and this is available where...? and so 
>>> on: can you SHOW in your proposal that this WILL address the issues?)
>>>
>>
>> I'm a little bit confused here, What you mean by "SHOW that this works"? 
>>
>>- Do you just write some pseudo code, and say this will work?
>>- Or I have to prove in some way that this will work??
>>
>>
>>> HTH.
>>>
>>> Kind Regards,
>>>
>>> Carlton
>>>
>>>
>>> On Monday, 1 April 2019 21:29:33 UTC+2, PARTH PATIL wrote:
>>>>
>>>> Here is a link to my GSoC proposal
>>>> Its a first draft so you are open to comment and suggest changes
>>>>
>>>>
>>>> https://docs.google.com/document/d/1JuoVOU5xMwXY7JrHJshezIyuIpFfoEM49rO3e0rfNhE/edit?usp=sharing
>>>>
>>>>
>>>> Best Regards,
>>>>
>>>> PARTH PATIL
>>>>
>>>> SOFTWARE DEVELOPER, AUV-IITB
>>>>
>>>> CONVENOR, ELECTRONICS & ROBOTICS CLUB IIT BOMBAY.
>>>>
>>>> [image: Image result for FACEBOOK ROUND ICON] 
>>>> <https://www.facebook.com/parth.patil.77> [image: Image result for 
>>>> instagram ROUND ICON] <https://www.instagram.com/code_blooded18/> [image: 
>>>> Image result for linkedin ROUND ICON] 
>>>> <https://www.linkedin.com/in/parth-patil-256291117/>
>>>>
>>>>

-- 
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/a3957e91-da52-481f-90c2-49f3f5f8e22d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GSoC Proposal (FormSet Improvement)

[PARTH PATIL]

On Thursday, April 4, 2019 at 10:02:01 AM UTC+5:30, Asif Saif Uddin wrote:
>
> I checked your contribution Parth, really good one!
>

Thank you :)
 

> once you improve your proposal, try to focus more on 
> form/formfield/formset/widget/admin/ related issues so that you have a 
> better insight into what your proposal going to improve in those areas. And 
> popular and useful extensions could be benefited from x features to be 
> implemented in that way etc. triaging the related area based tickets and 
> fixing some more related issues not only improve your chance to get 
> selected but help you understand the related areas much better. good luck 
> for GSoC this year.
>

Thanks again for the advice, I'm trying to compile a list for tickets that 
can be directly or indirectly fixed by my project. Also trying to find 12 
weeks worth of work in the formsets.
My main focus right now is:-

   - Making the request variable available throughout the formset
   - Handling relation fields in ModelFormSet  (* new)
   - declarative syntax for formset (#10403 
   <https://code.djangoproject.com/ticket/10403>)
   - adding pagination option / pretty print 

*Feel free if you would like to add something to this.*
 

> On Wednesday, April 3, 2019 at 10:06:26 PM UTC+6, PARTH PATIL wrote:
>>
>> Yes sure I will try to update my proposal by tomorrow (4th April) night 
>> (IST +5:30), So  please have a look at it once again, and suggest changes.
>>
>>
>> Best Regards,
>> PARTH PATIL
>>
>> On Wed, 3 Apr 2019, 9:23 pm Carlton Gibson,  wrote:
>>
>>> Yes, just pseudo code — so when reviewing your proposal next week it's 
>>> easy to see that it'll be the right approach. 🙂
>>>
>>> On Wednesday, 3 April 2019 17:51:18 UTC+2, PARTH PATIL wrote:
>>>>
>>>>
>>>>
>>>> On Wednesday, April 3, 2019 at 8:58:26 PM UTC+5:30, Carlton Gibson 
>>>> wrote:
>>>>>
>>>>> Hey Parth. 
>>>>>
>>>>> Right. So, thanks for making the effort so far. Good. 
>>>>>
>>>>> Can you add more detail about yourself. You've not contributed to 
>>>>> Django right? So the concern at this point would be whether you're able 
>>>>> to 
>>>>> fulfil the project. 
>>>>>
>>>>
>>>> I have contributed to Django (see #30189 
>>>> <https://code.djangoproject.com/ticket/30189>), I have mentioned it at 
>>>> the end of my proposal, I would try to highlight that. 
>>>>
>>>>  
>>>>
>>>>> What's your experience with Django? (and if you want to implement a 
>>>>> declarative formset syntax, Python more generally?)
>>>>> (Perhaps you said this, but it needs to be in the proposal.) 
>>>>>
>>>>
>>>> Sure I will add some of my projects in the proposal. 
>>>>
>>>>>
>>>>> You don't necessarily need to have ideas for the final code, but what 
>>>>> does e.g. the usage look like with your idea (i.e. adding the request 
>>>>> parameter)? 
>>>>> (So the formset gets the request and this is available where...? and 
>>>>> so on: can you SHOW in your proposal that this WILL address the issues?)
>>>>>
>>>>
>>>> I'm a little bit confused here, What you mean by "SHOW that this 
>>>> works"? 
>>>>
>>>>- Do you just write some pseudo code, and say this will work?
>>>>- Or I have to prove in some way that this will work??
>>>>
>>>>
>>>>> HTH.
>>>>>
>>>>> Kind Regards,
>>>>>
>>>>> Carlton
>>>>>
>>>>>
>>>>> On Monday, 1 April 2019 21:29:33 UTC+2, PARTH PATIL wrote:
>>>>>>
>>>>>> Here is a link to my GSoC proposal
>>>>>> Its a first draft so you are open to comment and suggest changes
>>>>>>
>>>>>>
>>>>>> https://docs.google.com/document/d/1JuoVOU5xMwXY7JrHJshezIyuIpFfoEM49rO3e0rfNhE/edit?usp=sharing
>>>>>>
>>>>>>
>>>>>> Best Regards,
>>>>>>
>>>>>> PARTH PATIL
>>>>>>
>>>>>> SOFTWARE DEVELOPER, AUV-IITB
>>>>>>
>>>>>> CONVENOR, ELECTRONICS & ROBOTICS CLUB IIT BOMBAY.
>>>>>>
>>>>>> [image: Image res

Re: GSoC Proposal (FormSet Improvement)

[PARTH PATIL]

Yes sure I will try to update my proposal by tomorrow (4th April) night
(IST +5:30), So  please have a look at it once again, and suggest changes.


Best Regards,
PARTH PATIL

On Wed, 3 Apr 2019, 9:23 pm Carlton Gibson, 
wrote:

> Yes, just pseudo code — so when reviewing your proposal next week it's
> easy to see that it'll be the right approach. 🙂
>
> On Wednesday, 3 April 2019 17:51:18 UTC+2, PARTH PATIL wrote:
>>
>>
>>
>> On Wednesday, April 3, 2019 at 8:58:26 PM UTC+5:30, Carlton Gibson wrote:
>>>
>>> Hey Parth.
>>>
>>> Right. So, thanks for making the effort so far. Good.
>>>
>>> Can you add more detail about yourself. You've not contributed to Django
>>> right? So the concern at this point would be whether you're able to fulfil
>>> the project.
>>>
>>
>> I have contributed to Django (see #30189
>> <https://code.djangoproject.com/ticket/30189>), I have mentioned it at
>> the end of my proposal, I would try to highlight that.
>>
>>
>>
>>> What's your experience with Django? (and if you want to implement a
>>> declarative formset syntax, Python more generally?)
>>> (Perhaps you said this, but it needs to be in the proposal.)
>>>
>>
>> Sure I will add some of my projects in the proposal.
>>
>>>
>>> You don't necessarily need to have ideas for the final code, but what
>>> does e.g. the usage look like with your idea (i.e. adding the request
>>> parameter)?
>>> (So the formset gets the request and this is available where...? and so
>>> on: can you SHOW in your proposal that this WILL address the issues?)
>>>
>>
>> I'm a little bit confused here, What you mean by "SHOW that this works"?
>>
>>- Do you just write some pseudo code, and say this will work?
>>- Or I have to prove in some way that this will work??
>>
>>
>>> HTH.
>>>
>>> Kind Regards,
>>>
>>> Carlton
>>>
>>>
>>> On Monday, 1 April 2019 21:29:33 UTC+2, PARTH PATIL wrote:
>>>>
>>>> Here is a link to my GSoC proposal
>>>> Its a first draft so you are open to comment and suggest changes
>>>>
>>>>
>>>> https://docs.google.com/document/d/1JuoVOU5xMwXY7JrHJshezIyuIpFfoEM49rO3e0rfNhE/edit?usp=sharing
>>>>
>>>>
>>>> Best Regards,
>>>>
>>>> PARTH PATIL
>>>>
>>>> SOFTWARE DEVELOPER, AUV-IITB
>>>>
>>>> CONVENOR, ELECTRONICS & ROBOTICS CLUB IIT BOMBAY.
>>>>
>>>> [image: Image result for FACEBOOK ROUND ICON]
>>>> <https://www.facebook.com/parth.patil.77> [image: Image result for
>>>> instagram ROUND ICON] <https://www.instagram.com/code_blooded18/> [image:
>>>> Image result for linkedin ROUND ICON]
>>>> <https://www.linkedin.com/in/parth-patil-256291117/>
>>>>
>>>> --
> 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/deae8484-5a5c-4158-b5ef-f262f30eb6eb%40googlegroups.com
> <https://groups.google.com/d/msgid/django-developers/deae8484-5a5c-4158-b5ef-f262f30eb6eb%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAJSC-if9H2qtU3cMx0puRbJFRuH0O7Jq3VomXH3sPaMRbtBB2w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: GSoC Proposal (FormSet Improvement)

[PARTH PATIL]

On Wednesday, April 3, 2019 at 8:58:26 PM UTC+5:30, Carlton Gibson wrote:
>
> Hey Parth. 
>
> Right. So, thanks for making the effort so far. Good. 
>
> Can you add more detail about yourself. You've not contributed to Django 
> right? So the concern at this point would be whether you're able to fulfil 
> the project. 
>

I have contributed to Django (see #30189 
<https://code.djangoproject.com/ticket/30189>), I have mentioned it at the 
end of my proposal, I would try to highlight that. 

 

> What's your experience with Django? (and if you want to implement a 
> declarative formset syntax, Python more generally?)
> (Perhaps you said this, but it needs to be in the proposal.) 
>

Sure I will add some of my projects in the proposal. 

>
> You don't necessarily need to have ideas for the final code, but what does 
> e.g. the usage look like with your idea (i.e. adding the request 
> parameter)? 
> (So the formset gets the request and this is available where...? and so 
> on: can you SHOW in your proposal that this WILL address the issues?)
>

I'm a little bit confused here, What you mean by "SHOW that this works"? 

   - Do you just write some pseudo code, and say this will work?
   - Or I have to prove in some way that this will work??


> HTH.
>
> Kind Regards,
>
> Carlton
>
>
> On Monday, 1 April 2019 21:29:33 UTC+2, PARTH PATIL wrote:
>>
>> Here is a link to my GSoC proposal
>> Its a first draft so you are open to comment and suggest changes
>>
>>
>> https://docs.google.com/document/d/1JuoVOU5xMwXY7JrHJshezIyuIpFfoEM49rO3e0rfNhE/edit?usp=sharing
>>
>>
>> Best Regards,
>>
>> PARTH PATIL
>>
>> SOFTWARE DEVELOPER, AUV-IITB
>>
>> CONVENOR, ELECTRONICS & ROBOTICS CLUB IIT BOMBAY.
>>
>> [image: Image result for FACEBOOK ROUND ICON] 
>> <https://www.facebook.com/parth.patil.77> [image: Image result for 
>> instagram ROUND ICON] <https://www.instagram.com/code_blooded18/> [image: 
>> Image result for linkedin ROUND ICON] 
>> <https://www.linkedin.com/in/parth-patil-256291117/>
>>
>>

-- 
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/a3c56a4b-76df-4ac8-9a0e-3e9de01047ae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GSoC Proposal (FormSet Improvement)

[PARTH PATIL]

Best Regards,
PARTH PATIL

On Tue, 2 Apr 2019, 10:04 am Asif Saif Uddin,  wrote:
>
> It would be great if you could find out 12 weeks of work with formset
> improvement.
>
>
> Yes I'm searching for it and will update the proposal accordingly. If you
have any suggestions please let me know.

>
> please try to include for improvements and add more technical aspects you
> are going to fix or include.
>
> Regarding technical aspect, I'm confused about how much detail is needed,
because I can decide the architecture only after discussion with mentors
(right?)

> --
> 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/15115e46-435b-4513-aff9-71db589ba61f%40googlegroups.com
> <https://groups.google.com/d/msgid/django-developers/15115e46-435b-4513-aff9-71db589ba61f%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
>
>

-- 
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/CAJSC-id092_hUc6yTSvtqytzArd3qokoXarnN1fVyxVW7K0oAA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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.

Help for GSoC proposal (Formset improvements)

[PARTH PATIL]

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/09458146-224c-44c5-8bb3-2560f47350e5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GSoC 2019 Project Idea

[PARTH PATIL]

Hey Carlton,

Thanks for your feedback.
I would try to think of something which is more inclined towards core 
functionality of Django :)

On Monday, March 4, 2019 at 1:52:39 AM UTC+5:30, Carlton Gibson wrote:
>
> Hi Parth. 
>
> I'm guessing this would be out of scope for Django: it's sounds like the 
> sort of functionality that we prefer to live in third-party apps, rather 
> than in Django itself. 
> (It sounds like a good enough idea — there are plenty of Jekyll, or other 
> static, sites out there, but just not something for core.) 
>
> As I just posted elsewhere, I'm looking to work on the GSoC stuff over the 
> next couple of weeks. 
>
> Kind Regards,
>
> Carlton
>
>
> On Sunday, 3 February 2019 11:04:07 UTC+1, PARTH PATIL wrote:
>>
>> Hey, I had a project idea for GSoC.
>> I wanted to make a tool which will help to port static projects like 
>> Jekyll to Django directly.
>> I am still thinking about the details of the idea.
>>
>> But I want to know:
>>
>>- is this idea feasible/useful?
>>- Does there already exist a similar tool for this?
>>- Is this a good idea for GSoC?
>>
>> I got this idea last year when I was working on my club website which was 
>> written using Jekyll and I had to port it to Django framework since it was 
>> going to be hosted on our college server which had Django backend.
>> The problem was we constantly had to update the website with post, so I 
>> was just left with the option to rewrite all the code natively in Django. 
>> That's why I thought of making a tool which will take a Jekyll project and 
>> convert it to Django app, with proper views and models etc.
>>
>>  
>>
>

-- 
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/92087e41-680b-4662-b600-db9528e9ae13%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Google Summer of Code 2019

[PARTH PATIL]

Hey its been quite a while, I have posted my idea for gsoc here 
. 
Can someone please review it so that i can decide whether to move with this 
or think of something else.

-- 
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/ba977bab-0c54-4fcf-a4be-39b1918a79b4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Google Summer of Code 2019

[PARTH PATIL]

Hey, I am really enthusiastic for doing GSoC with Django, I had been 
working for a few months to get myself familiar with the code base. I have 
quite a few unpolished ideas in my mind for projects like the one posted 
here 

.

Though I'm unable to understand why Django is not ready to participate in 
GSoC this year?

Also, I would like to point out what *Carlton* said in his post 

.

   - I don't think it is justified to expect mind-blowing project proposal 
   this early. As per the GSoC's timeline, the application deadline is April 9 
   which is like two months for now.
   - Even the discussions of ideas according to Google begins from 20 days 
   from now.
   - There is also no ideas page for Django for 2019, to which students can 
   refer.
   - More importantly, as a student, I think many students will be 
   genuinely interested to take up a few good projects with Django.



On Monday, February 4, 2019 at 2:41:11 AM UTC+5:30, Carlton Gibson wrote:
>
> Yes. GSoC wasn't at all on my radar before your post here Tim. 
>
> We've had a few "hello" posts but no even semi-concrete proposals from 
> students. (Equally we don't have a list ready to go.) 
>
> I had a look at the process. It seems a moderate commitment, so, for me, I 
> think I'd want to be familiar with applicants before we took that on. i.e. 
> We need say to students to get involved months before. 
> I'll think about messaging for that for next year because GSoC seems good 
> overall. 
>
> SO unless someone is going to blow us away with an outline of a proposal 
> TOMORROW, we'll have to pass this year. (Deadline being Tuesday.)
>
> On Friday, 1 February 2019 22:32:43 UTC+1, Tim Graham wrote:
>>
>> As of now, I haven't seen any existing Django contributors who are 
>> planning to propose a project, therefore I don't think it's worthwhile for 
>> the DSF to apply for this summer. The decision to apply on behalf of the 
>> DSF is up to Carlton, Mariusz, or another potential mentor.
>>
>> On Thursday, January 31, 2019 at 6:24:36 AM UTC-5, gaurav jain wrote:
>>>
>>> One Idea i have a one command django project maker to instead having 1+n 
>>> commands(n number of apps) and linking them in setting we can have command 
>>> take the number of apps and app_names in ine do and then later we can add 
>>> functionality for heroku ,docker etc
>>>
>>> On Wednesday, January 16, 2019 at 8:03:55 PM UTC+5:30, Tim Graham wrote:

 Org applications for Google's Summer of Code are now open (deadline 
 February 6). Do you think the Django Software Foundation should 
 participate?

 We haven't had any high quality student applications that we could 
 accept for the past two years.

 Perhaps it's partly a function of a poor ideas page (
 https://code.djangoproject.com/wiki/SummerOfCode2018). Perhaps we 
 don't do a great job of publicizing our involvement and attracting high 
 quality students. Perhaps it's because the student payment isn't all that 
 much (+/-$6000 USD, depending on student's country)* for the amount of 
 work 
 involved (also, students have to put in a lot of work up front in their 
 application, with no guarantee of being accepted into the program).

 If you have any ideas about mentoring or suggesting a project, or if 
 you're serious about being a student (you should start contributing to 
 Django now if you don't already), please share.

 * https://developers.google.com/open-source/gsoc/help/student-stipends

>>>

-- 
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/65c300ab-16b0-4a4f-8de7-3f86d1dd29d1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

GSoC 2019 Project Idea

[PARTH PATIL]

Hey, I had a project idea for GSoC.
I wanted to make a tool which will help to port static projects like Jekyll 
to Django directly.
I am still thinking about the details of the idea.

But I want to know:

   - is this idea feasible/useful?
   - Does there already exist a similar tool for this?
   - Is this a good idea for GSoC?

I got this idea last year when I was working on my club website which was 
written using Jekyll and I had to port it to Django framework since it was 
going to be hosted on our college server which had Django backend.
The problem was we constantly had to update the website with post, so I was 
just left with the option to rewrite all the code natively in Django. 
That's why I thought of making a tool which will take a Jekyll project and 
convert it to Django app, with proper views and models etc.

 

-- 
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/92a5f672-4ab3-41a9-a93c-38422a121794%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GSoC Idea

[PARTH PATIL]

Hey, can you elaborate on what your idea is?

On Thursday, January 31, 2019 at 4:54:36 PM UTC+5:30, gaurav jain wrote:
>
> from django.db import models
> from django.contrib.auth.models import User
>
> class CommenInfo(models.Model):
> archived = models.BooleanField(default=False)
> created_at = models.DateTimeField(auto_now_add=True)
> updated_at = models.DateTimeField(auto_now=True)
>
> def delete(self):
> self.archived = True
> super().save()
>
> class Meta:
> abstract = True
> class Team(CommenInfo):
> pass
>
>
>

-- 
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/02ed1aa7-c22a-4588-8b3e-5815f59a5e74%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Google Summer of Code 2019

[PARTH PATIL]

Hey Parth here. I am genuinely interested in doing a project with django as 
student in gsoc 2019. I have been working hard since past few months to get 
myself familiar with the famework. I had few project ideas in mind, but I'm 
confused about the intricacies and needed some help. Also i haven't contributed 
much yet, it would be very helpful if anyone can give me proper channel from 
where i can seek help or discuss with other people. Also where can i find the 
contact of people who have already done a gsoc project with django.

P.S.:- I have tried posting on groups and messaging few people, but haven't 
gone far with that

-- 
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/87532f2a-a44d-4417-ab0e-a13b0fad58d2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.