Re: [GSoC] Update of my work

I have created a gist which summarizes the work done during my GSoC project with links to the commits. For those interested may have a look: *goo.gl/qGGhok *Regards Anubhav -- You received this message because you are subscribed to the Google Groups "Django developers"

[GSoC] Update of my work

t'd be good to share it here. GSoC Work <https://gist.github.com/coder9042/366766db260d4b6f157a> The work done in 10 weeks is listed out in the gist. I still have few more issues left to be worked upon in the remainder of the time. Regards, Anubhav Joshi -- You received this messag

Re: Decision for ticket #14787

On Thursday, July 10, 2014 9:39:09 PM UTC+5:30, Tim Graham wrote: > > It could be useful, however, I think many projects would also want to have > some way of configuring the max file upload size without having to specify > it on every FileField. One way to achieve this might be if a a custom fil

Re: Decision for ticket #14787

Do we have a decision here whether or not to include an option `max_size` on FileField in core? -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-deve

Re: Decision for ticket #14787

As per the suggestion on the ticket, I would like to tell my ideas in a better way. - Add a new attribute *max_size* to FileField and add a check in *to_python()* like the others. Reasons: Easy way to limit the size of file-uploads. No need to search for third party implementations o

Decision for ticket #14787

#14787 The ticket says to handle more errors on *FileField*. The idea it suggests is by propagating errors from uploadhandler to forms. Recently I took to solving the issue. If we look in files/uploadhandler.py

Re: #22383 Add the HTML5 required tag to the input fields which are required for database entry

On Friday, April 11, 2014 4:57:33 AM UTC+5:30, Gregor Müllegger wrote: > > I think adding the `required` attribute but ignoring the other possible > html form validations (like `min` and `max` [1] for that are used > by the forms.IntegerField) seems a bit half-hearted. > > My opinion is that h

Re: #22383 Add the HTML5 required tag to the input fields which are required for database entry

On Thursday, April 10, 2014 11:19:18 PM UTC+5:30, anubhav joshi wrote: > > A ticket has been opened asking to add HTML5 required tag in forms for the > fields which are required for database entry. > > Better wording: "required for database entry" --> fields have *

#22383 Add the HTML5 required tag to the input fields which are required for database entry

A ticket has been opened asking to add HTML5 required tag in forms for the fields which are required for database entry. There have been several issues: 1. Is this new option going to stay or is it just transitional. 2. Is it going to be an optional feature or default behaviour. 3. Shou

Re: #22268 - values_list() on a ManyToManyField returns

> values() and values_list() are both intended as optimisations for a > specific use case - retrieval of subsets of data without the overhead of > creating a model instance. This metaphor completely falls apart when > dealing with m2m relations, because the the "one row, one object" metaphor

Re: [GSoC 2014 Proposal] Improving Error and Fixing up related issues.

Ok. Thanks Anubhav -- You received this message because you are subscribed to the Google Groups "Django developers" 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 dja

Re: [GSoC 2014 Proposal] Improving Error and Fixing up related issues.

I read on google melange: "mentoring organizations may request further proposal detail from the student applicant." My tests are about to start so I want to know if and when should I be expecting this. Regards, Anubhav -- You received this message because you are subscribed to the Google Grou

#22268 - values_list() on a ManyToManyField returns

There has been quite a discussion on the ticket regarding this Refs. : https://code.djangoproject.com/ticket/22268 I think we must discuss and decide what should be the solution we should be working towards. Until now there have been two strategies: 1.) The query generated is correct therefore, W

Re: [GSoC'14] Proposal: Improve annotation and aggregation

As far as I am aware already the tasks that are listed out in the GSoC idea page have been completed by someone and there is a PR for that purpose also. https://github.com/django/django/pull/2184 -- You received this message because you are subscribed to the Google Groups "Django developers" gr

Re: [GSoC 2014 Proposal] Improving Error and Fixing up related issues.

report of misleading messages popping up, whatever the reason may be. I did keep in mind this thing while doing my background research of issues on Trac or IRC. Regards, Anubhav Joshi -- You received this message because you are subscribed to the Google Groups "Django developers"

Re: [GSoC 2014 Proposal] Improving Error and Fixing up related issues.

the questions. Waiting to hear more from you. Regards, Anubhav Joshi IIT Patna -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developer

Re: [GSoC 2014 Proposal] Improving Error and Fixing up related issues.

7;. Further I extended the idea to fixing related issues. As you would have seen there are many things that are proposed to be taken up like 'refactoring handlers', 'uri_to_iri', etc. which are important and they in their help in raising wrong types of error.

Re: [GSoC 2014 Proposal] Improving Error and Fixing up related issues.

I do keep updating gist upon getting feedback/reviews on IRC as well. Please keep a track. https://gist.github.com/coder9042/c505dfba9514a6e52fdc Regards, Anubhav Joshi IIT Patna -- You received this message because you are subscribed to the Google Groups "Django developers"

Re: [GSoC 2014 Proposal] Improving Error and Fixing up related issues.

Done the required. https://gist.github.com/coder9042/c505dfba9514a6e52fdc Regards, Anubhav Joshi IIT Patna -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an

Re: [GSoC 2014 Proposal] Improving Error and Fixing up related issues.

Just realized that the proposal name is : Improving error reporting and fixing up related issues. Missed 'reporting' in the thread topic. Anubhav Joshi -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe

Re: [GSoC 2014 Proposal] Improving Error and Fixing up related issues.

OK, will do. Anubhav Joshi -- You received this message because you are subscribed to the Google Groups "Django developers" 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 g

Re: [GSoC 2014 Proposal] Improving Error and Fixing up related issues.

posal and leave your reviews and comments. I am posting this using a friend's computer, I will be back as soon as I fix up my laptop. Probably not more than a day. Regards, Anubhav Joshi IIT Patna -- You received this message because you are subscribed to the Google Groups "Django de

[GSoC 2014 Proposal] Improving Error and Fixing up related issues.

. My proposal is available as a gist : https://gist.github.com/coder9042/c505dfba9514a6e52fdc . Please have a look and help me in improving it. If there are any questions, I will be happy to answer. Regards, Anubhav Joshi IIT Patna -- You received this message because you are subscribed to the

Re: requiring login to perform Trac actions?

e people have anonymously posted replies and never replied. Regards, Anubhav Joshi -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-deve

Re: index_together should also have the same convinience as unique_together

This is now fixed in bb2ca9f<https://github.com/django/django/commit/bb2ca9fe6cdd490526b44b30f207c8f743bfaa84> . PR : #2381 <https://github.com/django/django/pull/2381> Regards, Anubhav Joshi IIT Patna -- You received this message because you are subscribed to the Google Gro

index_together should also have the same convinience as unique_together

"For convenience, unique_together can be a single tuple when dealing with a single set of fields" This convinience is missing in index_together: I have opened a PR, please see: https://github.com/django/django/pull/2381 Regards, Anubhav Joshi IIT Patna -- You received this messa

Re: index_together should also have the same convinience as unique_together

Related : https://code.djangoproject.com/ticket/22172 -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To pos

Re: GSoC 2014 proposal [Improving error reporting]

, it is my humble request to please go through the issues here as well once for the above mentioned reasons. Regards, Anubhav Joshi IIT Patna -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop

Re: GSoC 2014 proposal [Improving error reporting]

As suggested by Tim Graham, I am going to put my analysis on respective tickets. Also it is possible that some issues are directly mentioned on wiki page(there is no ticket for them), so its a humble request to please go through it once here. Regards, Anubhav Joshi IIT Patna -- You received

Re: GSoC 2014 proposal [Improving error reporting]

On Friday, February 28, 2014 2:03:10 AM UTC+5:30, Tim Graham wrote: > > I think it'll be better to put your analysis of each ticket on the ticket > itself. Then when you're finished with that, put together a more high level > overview of the analysis you've done. I think it will be easier to gi

Re: GSoC 2014 proposal [Improving error reporting]

at #18959 is there, but as far as I have understood it worksforme or else if someone can help me reproduce the problem/error if I am wrong, then it would be very helpful. Regards, Anubhav Joshi IIT Patna -- You received this message because you are subscribed to the Google Groups "Dja

Re: GSoC 2014 proposal [Improving error reporting]

pings in 6 hours isn't especially helpful. There will be people > who have been asleep for that entire period. > > Yours, > Russ Magee %-) > > Apologies for being over eager. Regards, Anubhav Joshi IIT Patna -- You received this message because you are subscribed to the Googl

Re: GSoC 2014 proposal [Improving error reporting]

Please give me any reviews and suggestions regarding the issues, as and when I am posting about them. So that when I my studying and analysis of the issues is done, then I can chalk out a proper timeline for the required work as well. Regards, Anubhav Joshi IIT Patna -- You received this

Re: GSoC 2014 proposal [Improving error reporting]

Please have a look at all the issues mentioned, correct me where I am wrong and there are places where I need help(I have mentioned in those places.) I need feedback and reviews. Will be posting back again very soon with further analysis of other issues. Regards, Anubhav Joshi IIT Patna

Re: GSoC 2014 proposal [Improving error reporting]

Here is some more analysis: django.db 1.) There is a problem with ForeignKey, which when given only blank=True causes ValidationError as they do not allow null values. If blank=True, null=True is specified then, there is no problem. The operation of ModelForms is such so as to construct insta

Re: GSoC 2014 proposal [Improving error reporting]

seNotFound. Feedback Needed. Working on other issues, will be posting soon. Regards, Anubhav Joshi IIT Patna -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send

Re: GSoC 2014 proposal [Improving error reporting]

'improving error reporting' but are worth fixing and AAMOF they interest me as well. Regards, Anubhav Joshi -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails fro

Re: GSoC 2014 proposal [Improving error reporting]

umably if your proposal > were accepted, you could assign them to yourself at that time. > Ok will keep that in mind Regards, Anubhav Joshi IIT Patna -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this gro

Re: GSoC 2014 proposal [Improving error reporting]

can be masked under certain circumstances." > If I could get a better explanation of this, it would be very helpful. > Also If I could get an answer to the above. Regards, Anubhav Joshi IIT Patna -- You received this message because you are subscribed to the Google Groups "Django devel

Re: GSoC 2014 proposal [Improving error reporting]

ps://code.djangoproject.com/ticket/10811 https://code.djangoproject.com/ticket/7074 django.forms https://code.djangoproject.com/ticket/15069 https://code.djangoproject.com/ticket/13091 django.template https://code.djangoproject.com/ticket/16383 Now I would like to know whether it would be suitabl

GSoC 2014 proposal [Improving error reporting]

lanation of this, it would be very helpful. 3.) There are some tickets marked as 'wontfix' so I want to know whether I am being expected to somehow fix those if possible. Thanks, Anubhav Joshi IIT Patna Github: https://github.com/coder9042 -- You received this message because yo

Re: GSoC Project Idea

On Monday, February 24, 2014 4:21:15 PM UTC+5:30, Josh Smeaton wrote: > > As I mentioned in the last thread, I've already made some progress on > improving aggregates and annotations. I've submitted this PR for review > https://github.com/django/django/pull/2184 and discussion here: > https://

Re: GSoC Project Idea

I want to know whether this will make up a good GSoC project as I am also interested in 'improving the error messages part', therefore I want to make a final choice between the two topics. Awaiting replies and suggestions. Anubhav Joshi -- You received this message because you are

GSoC Project Idea

on to f() or q() objects. I have yet to work on the remaining issues which I surely will. I want to know whether this will make up a good GSoC project. Anubhav Joshi -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubs

Re: GSoC query

implementing arithmetic operations on aggregation.. I have found few ways: 1.)Adding it directly. 2.)Changing the complete implementation to f() or q() objects. I have yet to work on the remaining issues which I surely will. I want to know whether this will make up a good GSoC project. Anubhav

Re: GSoC query

Ok, actually my college exams are going on, as soon as they get over I will definitely take some action towards drafting the proposal and posting it here for review. Thanks Anubhav -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsub

Re: GSoC query

I need some suggestions related to improving the error message. I have gone through some tickets but I would like to know the existing issues that need to be resolved first than others, I mean those issues which need more attention. Thanking You Anubhav -- You received this message because yo

Re: GSoC query

On Sunday, February 16, 2014 4:35:05 AM UTC+5:30, Florian Apolloner wrote: > > On Saturday, February 15, 2014 5:01:09 PM UTC+1, anubhav joshi wrote: >> >> Well I will see what I put in my proposal..it will be based on >> aggregation/annotation as well as improving t

Re: GSoC query

I am not trying to say that I can solve all the issues myself, that is no way possible. But I had wanted to base my work on aggregation part but I think quite has been done so I just said that I would now explore other areas as well. I have no intention of telling that I could do all, I merely

Re: GSoC query

Well I will see what I put in my proposal..it will be based on aggregation/annotation as well as improving the error message part as before...I might now look to other things as well like improving tests as well. -- You received this message because you are subscribed to the Google Gro

Re: GSoC query

se,if something new has occurred to anyone. Anubhav Joshi -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.

GSoC query

Well I am thinking to work on aggregates and annotation, and improving the error messages part. I just want to know if these are still open. And what is the procedure if more than one student submit similar proposals or what if one submits it before then whether it remains open for another? Can w

GSoC Project Ideas

Well I am thinking to work on aggregates and annotation, and improving the error messages part. I just want to know if these are still open. And what is the procedure if more than one student submit similar proposals or what if one submits it before then whether it remains open for another? --

Fixing #10811 Prevet assigning of unsaved model to Foreign Key

I have tried fixiing #10811 https://code.djangoproject.com/ticket/10811 Earlier there were several errors popping up while running the test suite, but now I have fixed most of them. Although there are 2 errors which I am unable to fix some of them as I am unable to understand what the code is d