#ABOUT DEVELOPMENT

IMDbPY uses Mercurial repository. Actually the repository is hosted on Bitbucket and mirrored hourly on Sourceforge.

If you need help getting started with Mercurial, you can read the Mercurial help page on sourceforge or the Bitbucket help.

To clone the Mercurial repository (on Bitbucket):

hg clone https://bitbucket.org/alberanid/<project>/

To clone the Mercurial repository (on Sourceforge):

hg clone http://imdbpy.hg.sourceforge.net:8000/hgroot/imdbpy/<project>/

<project> must be replaced with a project name. IMDbPY projects are:

imdbpy

bitbucket: overview, browse source, download (zip, gz, bz2), changelog
sourceforge: browse source

imdbpykit

bitbucket: overview, browse source, download (zip, gz, bz2)
sourceforge: browse source

vdbpy

bitbucket: overview, browse source, download (zip, gz, bz2)
sourceforge: browse source

imdbpygw

bitbucket: overview, browse source, download (zip, gz, bz2)
sourceforge: browse source

imdbpyweb

bitbucket: overview, browse source, download (zip, gz, bz2)
sourceforge: browse source

imdbpyople

bitbucket: overview, browse source, download (zip, gz, bz2)
sourceforge: browse source

imdbpy-testsuite

bitbucket: overview, browse source, download (zip, gz, bz2)
sourceforge: browse source

Bug Track

Before filing any new bug track, take a look if it hasn't been already signaled.

Please report every information needed to reproduce the error. Remember to include error messages, stack tracebacks and, if available, the URL (or name or title) of the movie/person page that generates the error.

Patch Track

You can also submit patches directly to the mailing list.

Translate

Our account on Transifex can be used to coordinate the translation effort.
More on how to contribute to IMDbPY.

#MAILING LISTS

Both mailing lists are open also to non-subscribers (anyone can send emails) but they are moderated by default: your first message needs to be approved; if it's on-topic, the succeeding ones will be automatically accepted.

DEVELOPMENT

for developers (bug reports, new features requests, ...)

Archives:

gmane (gmane.comp.python.imdbpy group; via web, nntp, blog, and RSS feed)
Google groups (If possible, please subscribe it)

Looking for help mailing list?

They gives users support (questions, help, ...)

#DEVELOPMENT STATUS

Fix some core functions

Planned for: ASAP
Status:
Some of the core functionalities have become slightly bloated with legacy code. The imdb.utils.analyze_title, imdb.utils.analyze_name, imdb.parser.http.utils.build_movie and imdb.parser.http.utils.build_person need extra care and - for the last two - maybe a complete rewrite.

Update the SQL database using the plain text diff files

Planned for: long term
Status:
It would be really useful, but it sounds like a very complex task; for some thoughts about this, see this short thread. Timo Schulz worked a lot on this, coming to the conclusion that it's not feasible (at least with the current layout of the database) and that right now it's easier and faster to download the diff files, apply them and rebuild the database from scratch. I mostly agree.

Search for things like "keyword" and "plot"

Planned for: mid-term
Status:
Done, for keywords, in 4.0.

Improve stability, introduce logging a facility

Planned for: mid-term
Status:
Must be done ASAP. Help wanted.

Develop the Symbian/mobile interface

Planned for: mid-long term
Status:
We're searching for a developer for the mobile interface.

SQL generic queries

Planned for: mid-long term
Status:
A way to do free queries on the SQL database would be very cool. Nobody is working on this.

Fix the web site and the documentation, checking for syntax and grammar errors

Planned for: as soon as possible
Status:
Nobody is working on this; the author of the web site and the documentation is a non-native English speaker, and there are a lot of errors.

Improve the test suite

Planned for: as soon as possible
Status:
Nobody is seriously working on this; the current test suite is somewhat a mess, and doesn't cover every aspect of the IMDbPY package.