Hey ya,
yeah, 0.0.6 is fine :)
We need to change the setup.py a bit probably.
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.
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.
cu!
On Sun, Jun 6, 2010 at 8:33 PM, Alexandre Quessy <[email protected]>wrote:
> Hello everyone,
> Let's continue this thread about the near future of PyPortMidi!
>
> So, I am now part of the Debian Python Modules Packaging Team. I want
> to package python-portmidi this week, so it's time to take some
> decisions. :) That means it should be part on the next release of
> Ubuntu. (Maverick in fall 2010)
>
> First, we need to figure out a repository to use. I suggest that we
> use my current Mercurial for now, and move it to the portmedia SVN if
> René and me have a write access. Roger, do you want do give René and
> me a write access in this SVN repository? If not, we will simply
> continue the development on Mercurial or in Pygame's SVN. Since we
> need a setup.py and all that, it would be better if the project was
> kept outside of Pygame, for an easier packaging. I would stay in sync
> with the changes made by René, if he tells me when he makes some
> changes. Does that make sense?
>
> John, could you mention http://bibucket.org/aalex/pyportmidi and
> Pygame on your PyPortMidi page? Pointing to the current version will
> help people to get it to work on Debian and Ubuntu.
>
> René, how can I include your nice Python wrapper? Which files do I
> have to copy? Do you know what we have to change in the setup.py file?
>
> Can anyone help making the newest version work on Mac and Windows?
> Probably the Pygame developers. That can be left for later, before we
> upload it to PYPI.
>
> René: we should agree on a version number to use... I set mine to
> 0.0.6, but I could pretty well lower it down. I am not cheap on
> incrementing micro version numbers, though. We could merge all
> changes, fix everything and call it 0.1!
>
> Thanks a lot!
> Alex
>
> 2010/5/4 Roger Dannenberg <[email protected]>:
> > What I'm hearing is that PortMidi should adopt Rene's pygame version with
> > Alexandre's tweaks for Debian and Ubuntu. Some potential issues are:
> >
> > - I don't know how many platforms and Python versions are supported, but
> I
> > suppose I can try to fill in any gaps.
> > - It sounds like the API is a bit different, but it's possible most
> > Python/PortMidi users are using the pygame API anyway.
> > - PortMidi would have to release pyportmidi with the PortMidi license. It
> > sounds like this is not a problem, but please let me know if there are
> > objections, other contributors, etc. that might make this an issue.
> >
> > If I don't hear any negative replies, I'll work on this soon.
> >
> > -Roger
> >
> > Hi,
> >
> > just to be clear with regards to the LGPL thing... I wasn't suggesting
> the
> > LGPL be used, just that I emailed John about using pyportmidi in
> > pygame(which is LGPL) and that changes and fixes in the pygame version
> would
> > be contributed back to pyportmidi. Definitely makes sense to use the
> > portmidi licence. I'd also like to contribute my python API version from
> > pygame, which has complete documentation, tries to keep error handling
> > consistent, and also has a pep 8 API(the main code style for python). It
> > sits on top of the pyportmidi API.
> >
> >
> > cheers!
> >
> >
> >
> > ________________________________
> > _______________________________________________
> > media_api mailing list
> > [email protected]
> > http://lists.create.ucsb.edu/mailman/listinfo/media_api
> >
>
> --
> Alexandre Quessy
> http://alexandre.quessy.net/
>
_______________________________________________
media_api mailing list
[email protected]
http://lists.create.ucsb.edu/mailman/listinfo/media_api
