Hi,
I think I've overestimated my abilities to writing that kind of proposal.
I've tried being warned that it's "superhard" to find and analyse problem
in that way. I've tried to analyse many issues related to django admin but
without any general conclusions. Actually it demands to find some de
*
Hi again.
Let’s try analyse the topic Improved error handling a little deeper.
I’ve found dozen opened issues related to bad error handling (these are
rather *not* from Better Error Messages list). In general most of the bugs
demand different approach for each one.
1. django admin
https:
Thanks for all the discussion!
You convinced me that focusing on particular project and being able to
detail it - not looking for the best one in meaning of usefulness is the
key here. Also I did not take into account variable number of slots.
However I'm going to review *all* projects again an
esday, April 16, 2013 1:04:12 AM UTC+2, Russell Keith-Magee wrote:
>
>
> Yes - I was referring to error reporting. Although the same would be true
> for 'best practices'.
>
> Yours,
> Russ Magee %-)
>
> On Mon, Apr 15, 2013 at 3:22 PM, Damian Skrodzki
On Mon, Apr 15, 2013 at 7:51 AM, Damian Skrodzki
>
> > wrote:
>
>> Hi,
>>
>> After looking through proposed ideas for the current GSoC i found 2
>> issues related close to the code quality which I'm interested in. These are:
>>
>>
>>
Hi,
After looking through proposed ideas for the current GSoC i found 2 issues
related close to the code quality which I'm interested in. These are:
1. Best practices Updates
2. Improved error reporting
Both tasks are a different but they are very closely related just to code
quality
