Differences between revisions 79 and 82 (spanning 3 versions)
Revision 79 as of 2006-05-03 19:23:00
Size: 6586
Editor: h14
Comment: Removed Wax entry; it's not available for SoC 2006
Revision 82 as of 2006-05-23 14:07:00
Size: 5266
Comment: Move stdlib-related things to sub-page.
Deletions are marked like this. Additions are marked like this.
Line 19: Line 19:
 * CleanupUrlLibProject
 * Cleanup/modernize a module(s) in the stdlib.
 * The modules which deal with both str and unicode sometimes treat them differently -- which is usually a bug.
 * Clean up the porting ifdefs, including os and posixmodule
 * CompleteSslSupport
 * Add a MemoryUsageProfiler to python
      Currently it is almost impossible to figure out where memory is going in a large python program, especially if you have C extensions loaded. It'd be nice to know where the memory is going, if there are circular references, or if objects are being held too long.
 * math speedups or IO speedups (I think the string-in-base-10 to an int was recently sped up, but there may be other similar locations)
 * ./PythonCore
 * ./StandardLibrary
Line 31: Line 25:
 * Unify and extend Python's import mechanisms, possibly by prototyping it with PyPy (much easier than messing with CPython's import.c).
Line 35: Line 28:
 * UnicodeonWindowsExtensions
Line 37: Line 29:
 * SpeedUpInterpreterStartup
 * SandboxedPython
 * ./PythonGarbageCollected
 * ./RegisterVirtualMachine
Line 48: Line 36:
 * A better way to create (singlefile) executeables by bringing the advantages of py2exe and McMillans compiler together.  * A better way to create (singlefile) executables by bringing the advantages of py2exe and McMillans compiler together.
Line 52: Line 40:
 * [http://www.python.org/peps/pep-0337.html PEP 337]: Logging Support for Standard Library
Line 69: Line 56:
 * ProfileReplacementProject
 * ./EnhancedIterTools
 * ./ExploreFunctionalProgramming
 * MakeXmlrpclibAsynchronous
Line 79: Line 62:


 * Better introspection support for C functions: ability to expose arguments through inspect. Might require retrofitting existing extensions.

This page is aimed to be the starting point of collection for ideas for projects which could benefit the Python community, either projects that help the Python core, develop the standard library, third party packages, or more. The list below is in no way comprehensive or the only projects ideas that are acceptable! If you have an idea that is not listed that is fine; please submit a proposal for your idea!

This page was created to foster collaboration on ideas regarding projects that could be done as part of the [http://code.google.com/summerofcode.html Google Summer of Code].

There is a related page to discuss the ./MentorshipCoordination side of the project.

We've created a [http://mail.python.org/mailman/listinfo/soc2006 new mailing list] to discuss the Google Summer of Code from a Python POV. It is strongly encouraged people interested in discussing possible projects, people who'd be willing to help students this summer as mentors, and any students considering applying for the program to join and start discussions on that list.

Ideally, each project below should be expanded into a more full-featured description, so that people can judge the value, the effort involved, the size of the project (takes a week, takes a month, etc.), who knows enough about the project to help out, etc.

(Formatting:

  • Topics with a paragraph or so of thought, start new a page with a . in front of the wiki word, i.e.  ./CleanupUrlLibProject to scope the new pages a bit

  • for topics not fleshed out beyond a sentence or two, indent the sentence six spaces on a newline below the topic title/summary; this is to make sure that the description does not overpower the title/summary

)


Less fleshed-out ideas:

CodingProjectIdeas (last edited 2009-04-03 20:38:42 by 200-163-26-52)

Unable to edit the page? See the FrontPage for instructions.