python-musicbrainz3: Difference between revisions
From MusicBrainz Wiki
Jump to navigationJump to search
(New page: A planning page for python-musicbrainz3) |
No edit summary |
||
| Line 1: | Line 1: | ||
A planning page for python-musicbrainz3 |
A planning page for python-musicbrainz3 |
||
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! |
|||
The goal for the rewrite: |
|||
* 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 hat be?) |
|||
* Keep the amount and quality of documentation |
|||
* Write more test cases |
|||
== Links == |
|||
* [http://unmaintainable.wordpress.com/2010/03/13/future-of-python-musicbrainz2/ Matt's original blog announcement] |
|||
* TODO: relevant documentation |
|||
== Project Infrastructure == |
|||
* Soon: git repository |
|||
* TODO: Review board? |
|||
* TODO: Jira? |
|||
== Ideas == |
|||
* Use an XML mapping package (xml.etree?) |
|||
Revision as of 09:42, 14 March 2010
A planning page for python-musicbrainz3
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!
The goal for the rewrite:
* 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 hat be?) * Keep the amount and quality of documentation * Write more test cases
Links
* Matt's original blog announcement * TODO: relevant documentation
Project Infrastructure
* Soon: git repository * TODO: Review board? * TODO: Jira?
Ideas
* Use an XML mapping package (xml.etree?)
