Hi,
just a note, the bitbucket link had a typo:
http://bitbucket.org/aalex/pyportmidi/wiki/Home
Thinking about it a tiny bit more... we should keep the name as
'pyportmidi'. So it is the same on pypi, as the python module, and as the
name of the package. The debian/ubuntu package would be called
'python-pyportmidi'.
Probably sensible to keep the name the same across all the different places.
/setup.py
/README.txt
/pyportmidi/_pyportmidi.so # the old pypm.so module name. It's convention
to use an underscore module name for the C part.
/pyportmidi/_pyportmidi.pyx
/pyportmidi/_pyportmidi.c
/pyportmidi/pyportmidi.py
/pyportmidi/__iniit__.py # includes everything from pyportmidi.py
/pyportmidi/examples/...
/pyportmidi/tests/...
On Mon, Jun 7, 2010 at 4:26 AM, Alexandre Quessy <[email protected]>wrote:
> Hello René!
> I removed the debian file from the main branch. I called it "0.0", for
> the version number. I tend to call the branches with the major.minor
> version number.
>
> 2010/6/6 René Dudfield <[email protected]>:
> > Hey,
> >
> > username on bit bucket is illume.
> >
>
> I also added you on the toonloop1 project too, in case you want to
> improve the packaging for version 1.2, which is in Python with Pygame.
> I am moving to C++ though, for version 2.0.
>
> > Once you've added my name, I'll see how I go changing the files around.
> > Should be pretty easy to do.
> >
>
> I put a very short quick card on Mercurial at
> http://wiki.dataflow.ws/Mercurial
> I prefer distributed version control systems, especially when on a
> plane! :) Seems like Git is quite powerful, though a lot harder to
> learn than Mercurial, which is quite easy and has a lot of completion
> features.
>
> > cu, and thanks for driving this along!
> >
>
> Yes, let's follow this up and sprint on this.
> Later,
> Alex
>
_______________________________________________
media_api mailing list
[email protected]
http://lists.create.ucsb.edu/mailman/listinfo/media_api
