python-musicbrainz3: Difference between revisions
From MusicBrainz Wiki
Jump to navigationJump to search
(Removed <pre>s) |
(→Links) |
||
| Line 15: | Line 15: | ||
== Links == |
== Links == |
||
Links with documentation and other relevant information. |
|||
* [http://unmaintainable.wordpress.com/2010/03/13/future-of-python-musicbrainz2/ Matt's original blog announcement] |
* [http://unmaintainable.wordpress.com/2010/03/13/future-of-python-musicbrainz2/ Matt's original blog announcement] |
||
* [[NextGenerationSchema|Next Generation Schema Overview]] |
|||
* TODO: relevant documentation |
|||
* [[Next_Generation_Schema/SearchServerXML|Web Service Interface]] |
|||
* [[Next_Generation_Schema/XML|Web Service XML Format]] |
|||
== Project Infrastructure == |
== Project Infrastructure == |
||
Revision as of 10:40, 14 March 2010
The python-musicbrainz3 package is the successor of python-musicbrainz2.
NGS is coming, so a rewrite is in order to keep up with MB development. This wiki page collects information, plans, and ideas for this project.
Feel free to edit!
Goals
- Fully support the NGS data model and web service
- Require Python 2.6 and aim to be as close to Python 3 as possible
- Make it more pythonic where possible (naming conventions?)
- Remove rarely used cruft (what would that be?)
- Keep the amount and quality of documentation
- Write more test cases
Links
Links with documentation and other relevant information.
- Matt's original blog announcement
- Next Generation Schema Overview
- Web Service Interface
- Web Service XML Format
Project Infrastructure
- Soon: git repository
- TODO: Review board?
- TODO: Jira?
Ideas
- Use an XML mapping package (xml.etree?)
