Hello all,
I did some work on Python bindings for PortMidi in November, but I
don't use them and I've forgotten exactly what state things are in.
Based on the pm_python/README files, the PortMidi distribution has
working code for Python 2.6 and Python 3.1.1 on Linux, OS X., and
Windows, with the exception of the (Python 3.1/OS X) combination. If
there are patches I should know about, or there's anything I can help
with, please let me know. I think LGPL is more restrictive than
PortMidi's license, so I don't think I can just incorporate or release
an LGPL version in the PortMidi SourceForge distribution, so that might
account for some differences.
It would help me to hear more specific information about
differences. E.g. "the pygame version is better because..." or
"portmidi's release is good except for ...". My recollection is that
there are a number of minor problems in PyPortMidi in areas like error
handling and reporting, but I didn't want to make big changes to the API
that would break exsiting code, so I left things as they were.
-Roger
Alexandre Quessy wrote:
Hello René,
Thanks for your quick answer! We have not done anything more than in
the Pygame version. That means that you have everything in your hands
to push it upstream, if it has not been done already. We only needed a
working Debian package, that's it.
So, right now, what is the right way to get PyPortMidi under
Debian/Ubuntu GNU/Linux? I think it should be shipped with the
libportmidi0 package, no?
a
2010/5/3 René Dudfield <[email protected]>:
Hi,
as far as I know, I've been the only one distributing binaries and making
patches for a while. Tim Thompson also made some changes before that, and
before that I don't think there was anything since 2005.
I asked to redistribute those bindings under the LGPL - like how pygame is
licenced. Usually it's good form to ask permission to re-licence
something. I also told John that all changes we made could go back into
pyportmidi. It's nice to contribute back to projects you use :)
You might want to consider using the python wrappers as well. Since that
provides an API that follows python style (pep8), and a lot more
documentation comments.
Is there anything different in your version from what the pygame version
has? Would be nice to track any changes.
We did a lot of cross platform work, on osx/windows/linux etc. You should
be able to take the portmidi specific stuff from the pygame
config(link/include flags etc). As well, you may want to use the same build
environment we use on windows to make binaries. Another option, might be to
just use the pyportmidi.pyd from pygame on windows, if you don't mind
copying in the binary manually.
Another thing to note, is to use cython on the pyx file if you want python 3
support.
hope that helps.
On Mon, May 3, 2010 at 7:50 PM, Alexandre Quessy <[email protected]>
wrote:
Hello everyone,
My name is Alexandre Quessy, and I am a free audio-video software
developer from Montreal. I have put together the changes in pyportmidi
that the Pygame developers and some people from an other project had
done. I needed a Debian/Ubuntu package for the Scenic on which I work.
(from the SAT - Society for Arts and Technology) I put the resulting
code in a repository online at http://bitbucket.org/aalex/pyportmidi
The original author of pyportmidi - John Harrison - told me that it
would be best if the Python bindings for portmidi were distributed
with PortMidi. He has updated the license text to something that would
make it using the same license as PortMidi.
http://alumni.media.mit.edu/~harrison/images/license.txt
It seems like the version in the portmidi SVN is less recent. It
doesn't contain the fixes I had put together. Let's compare them:
http://portmedia.svn.sourceforge.net/viewvc/portmedia/portmidi/trunk/pm_python/pypm.pyx?view=markup
http://bitbucket.org/aalex/pyportmidi/src/f84ec7fa21ad/pypm.pyx
It seems, though, that my version doesn't build well on Windows. I
don't have access to any Windows computer, so maybe someone could try
it and tell me if it works or not. I am not the guy that has done the
changes to the Pyrex code itself, though, I have just done a merge of
several versions, and packaged it for Debian, together with my
collegue Simon Piette.
Attached to this wiki page, there is a patch that fixes the most major
bug we had on Ubuntu with pyPortMidi:
https://svn.sat.qc.ca/trac/scenic/wiki/pyPortMidi
Here is a direct link to the patch:
https://svn.sat.qc.ca/trac/scenic/raw-attachment/wiki/pyPortMidi/pypm-pmnoerror.diff
That bugfix was applied iin the mercurial repository on Bitbucket,
plus the changes that were made in Pygame.
http://svn.seul.org/viewcvs/viewvc.cgi/trunk/src/pypm.pyx?view=markup&root=PyGame
So, who is responsible for managing the Python bindings in PortMidi?
What can I do to help speeding up the process of pushing that bug fix
upstream?
Thanks!
--
Alexandre Quessy
http://alexandre.quessy.net/
_______________________________________________
media_api mailing list
[email protected]
http://lists.create.ucsb.edu/mailman/listinfo/media_api
_______________________________________________
media_api mailing list
[email protected]
http://lists.create.ucsb.edu/mailman/listinfo/media_api
