|
Size: 1907
Comment:
|
Size: 1813
Comment: Semi-randomly rearrange the projects
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| * Cleanup/modernize a module(s) in the stdlib. * Work on unit test suite. This includes not only developing support code (such as decorators to flag tests that are implementation-specific, known to fail, etc.), but also to have more code coverage in the unit tests. * Implement the [http://www.unicode.org/reports/tr6/ SCSU] codec. * ../FileSystemVirtualization * ../EnhancedIterTools * ../ExploreFunctionalProgramming * ../TestingImprovements |
|
| Line 2: | Line 9: |
| * Cleanup/modernize a module(s) in the stdlib. | |
| Line 6: | Line 12: |
| * [http://www.python.org/peps/pep-0337.html PEP 337]: Logging Support for Standard Library * ProfileReplacementProject * ../FileSystemVirtualization * ../EnhancedIterTools * ../ExploreFunctionalProgramming |
|
| Line 12: | Line 14: |
* asyncore: There are still people using asyncore, even though Twisted has taken most of the asynchronous-socket mindshare. There's a small test suite for asyncore, but it's far from exercising every method and branch. A good first step would be to improve the test suite. That would let us fix bugs with less worry about breaking the module. * curses: The largest outstanding issue for curses is support for Unicode, or wide characters, or however you write I18N applications with curses. |
|
| Line 13: | Line 18: |
| * Work on unit test suite. This includes not only developing support code (such as decorators to flag tests that are implementation-specific, known to fail, etc.), but also to have more code coverage in the unit tests. * Improve Python Debugger(PDB).Some of general ideas are here: ["PdbImprovments"].If you have any sugesstions related to pdb add them there. * Write an RPC mechanism, or prepare an existing RPC mechanism, for the standard library. * Implement the [http://www.unicode.org/reports/tr6/ SCSU] codec. |
* Improve Python Debugger(PDB).Some general ideas are here: ["PdbImprovments"]. If you have any suggestions related to pdb, add them there. * Write an RPC mechanism, or prepare an existing RPC mechanism, for the standard library (note: http://rpyc.wikispaces.com). |
| Line 18: | Line 21: |
| * ./RestructuredStandardLibrary * asyncore: There are still people using asyncore, even though Twisted has taken most of the asynchronous-socket mindshare. There's a small test suite for asyncore , but it's far from exercising every method and branch. A good first step would be to improve the test suite. That would let us fix bugs with less worry about breaking the module. * curses: The largest outstanding issue for curses is support for Unicode, or wide characters, or however you write I18N applications with curses. |
- Cleanup/modernize a module(s) in the stdlib.
- Work on unit test suite. This includes not only developing support code (such as decorators to flag tests that are implementation-specific, known to fail, etc.), but also to have more code coverage in the unit tests.
Implement the [http://www.unicode.org/reports/tr6/ SCSU] codec.
- The modules which deal with both str and unicode sometimes treat them differently -- which is usually a bug.
- asyncore: There are still people using asyncore, even though Twisted has taken most of the asynchronous-socket mindshare. There's a small test suite for asyncore, but it's far from exercising every method and branch. A good first step would be to improve the test suite. That would let us fix bugs with less worry about breaking the module.
- curses: The largest outstanding issue for curses is support for Unicode, or wide characters, or however you write I18N applications with curses.
- Add cross compiling support in distutils (and otherwise improve distutils).
Improve Python Debugger(PDB).Some general ideas are here: ["PdbImprovments"]. If you have any suggestions related to pdb, add them there.
Write an RPC mechanism, or prepare an existing RPC mechanism, for the standard library (note: http://rpyc.wikispaces.com).
- Write a library around pickle that allows developers to version their pickles such that old pickles can still be read even though the code that created them has been refactored, attributes renamed, and other such changes. (Perhaps not of great interest to the community. --amk)