Hello René and al! 2010/6/6 René Dudfield <ren...@gmail.com>: > Hey ya, > > yeah, 0.0.6 is fine :) >
Ok. We might upgrade it to 0.0.7 when we put your other files in the bucket. :) > We need to change the setup.py a bit probably. > Do you want to work with me on bitbucket? If so, just give me your bitbucket.org user name. I need to remove the debian-specific files from the project and put them on alioth.debian.org. Meanwhile, you can create a directory and work out the setup.py if you want. We can do an IRC sprint this week, if you're up to it. > these are where the files are in pygame: > lib/midi.py > src/pypm.pyx > src/pypm.c > > There are also some examples, and documentation... but they include pygame > code. The doc strings are in the midi.py, so that is fine. > Let's leave the pygame-specific code in Pygame. > > I think perhaps it should go into a package. Rather than putting pypm.so > and midi.py into the main site-packages/ dir. > > /setup.py > /README.txt > /portmidi/_portmidi.so # the old pypm.so module name. It's convention to > use an underscore module name for the C part. > /portmidi/_portmidi.pyx > /portmidi/_portmidi.c > /portmidi/portmidi.py > /portmidi/__iniit__.py # includes everything from portmidi.py > /portmidi/examples/... > /portmidi/tests/... > > This should probably be the first decision we make... try and put it into a > package, or keep the old module names? I vote for a clean modern python > package layout. > Let's go modern and clean. I love standards. Python standards a pretty high. (except for that old setup.py thing) -- Alexandre Quessy http://alexandre.quessy.net/ _______________________________________________ media_api mailing list media_api@create.ucsb.edu http://lists.create.ucsb.edu/mailman/listinfo/media_api
