ANN: MediaLocker – A wxPython App to Track Your Media


This is the first release of a real project that I’ve been involved in. I had written an article last month that inspired Werner Bruhin to want to take it and make it into a demonstration program for new wxPython programmers in how to do MVC and CRUD while interfacing with a database. Thus, MediaLocker was born. We hope you like it.


A wxPython database application that can help you keep track of your media. Currently, it only tracks your Book library. You can read more about the project’s development in the following two articles:


– Python 2.6+
– wxPython 2.8.11+ with the new pubsub (download here) or wxPython 2.9.3
SQLAlchemy 0.7.3+
ObjectListView 1.2


After you have downloaded the source, run “python develop” in the main folder before you try to run “”. If you are on wxPython 2.8, download the pubsub path (above) and extract it to “C:\Python27\Lib\site-packages\wx-2.9.2-msw\wx\lib” (or wherever your wxPython is installed).


You can download the source from Github:

You can also just download a snapshot of the current files here (uploaded 2011.12.09 @ 1138 hrs CST):

How you can help

Download the software and report bugs on Github. We also happily accept feature requests, especially if they include patches or code.

Note: This has only been tested on Windows XP and 7

3 thoughts on “ANN: MediaLocker – A wxPython App to Track Your Media”

  1. Pingback: » MediaLocker’s First Beta MediaLocker

  2. Tested on Ubuntu 10.04 when wxPython is updated to 2.8.12 through the ppa and SQLA is updated through pip or easy_install.  Everything works fine, so it should work on any linux system once you meet the minimum requirements.  Though you need to clone the repository.  The tar doesn’t work for me on either windows or linux.

    Thanks for the app.  I’ve been looking for something more than the simple tutorial apps that combines wxPython and SQLA.  This fits the bill perfectly!

    If you need any help with linux testing, let me know.  I’ll be working through the code over the next week or two as time permits.

  3. Thanks for the feedback. Just out of curiosity, what happened when you tried to run the tarred code? Did you get an error?

Comments are closed.