[soc2008-general] Patching bugs from bugs.python.org as a project.

["Martin v. Löwis"]

> Do you mean adding some functionality that I would like to see in python?
> If so, no, in this particular project I would just like to work on the bugs and
> feature requests reported in Bug Tracker. But if you mean people's wishful
> dreaming like this:
> http://bugs.python.org/issue1396825
> then yes, at least as long as the request is reasonable ;)

I would indeed suggest that you focus on a few larger-sized bugs/issues
if you can envision a solution; the bigger the problem, the less the
chance somebody comes up with a solution tomorrow.

> There is also lots of almost-done things like this:
> http://bugs.python.org/issue1085861
> or this:
> http://bugs.python.org/issue1053365
> (continued here: http://bugs.python.org/issue1926)
> or this:
> http://bugs.python.org/issue1492704
> and I think I can help closing them for good.

It would certainly help for the project, but I'm not so sure
it would make a good SoC project. If you can do most of it on
your own, it's good for your project. If you have to rely that
others do stuff, it's another risk. Your mentor may help with
that, though.

> More precisely:
>  - socket module (both Modules/socketmodule.c and Lib/socket.py)
>  - networking related modules (urllib*, nntplib, etc.)
>  - shutil, os and other operating system interfaces
> 
> I can think of a few more, but as I browse the tracker, it seems like
> socket module alone is an all-summer task. Be back with more.

Ok, that sounds like a good project.

Regards,
Martin