Hi,
sorry, I haven't done anything on it since. However, the pygame branch of
the bindings does keep up to date with new compilers (eg gcc 4.4 on windows,
new python versions etc) since. I don't have my midi hardware anymore(I'm
traveling), and I seem to have very little time for FOSS work... just doing
work to pay the rent at the moment.
I'm pretty sure Alexandre moved onto C++ from python.
If you give me to the end of the week, I can finish the previous plan of
separating out the code into the portmidi repository. My sourceforge id and
username are:
User ID: 2042
Login Name (User Name): illume
cheers,
On Tue, Sep 21, 2010 at 4:02 AM, John Harrison <[email protected]>wrote:
> Alexandre I'm assuming you are running with this and taking over as the
> maintainer? I saw you describe your work as a "friendly fork" but I don't
> really understand the point of a fork, especially as the changes I've seen
> are mostly trivial, and were added to make stuff work with the latest Python
> 2.x (unless I missed something.) I think you forked it because I was
> dropping the ball on the maintenance. So instead of forking let's perhaps
> instead just decide on a maintainer? For me it might be better if somebody
> else maintained pyPortMidi, if somebody has the enthusiasm to do so.
>
> Let me know.
>
> -John
>
>
> On 09/20/2010 02:43 PM, Roger Dannenberg wrote:
>
> Could someone advise me on the state of Python bindings for PortMidi and
> what if anything should go in the PortMidi repository on SourceForge?
>
> Thanks,
> Roger
>
>
> On 6/7/2010 8:51 AM, René Dudfield wrote:
>
> Hi, yeah that's the way.
>
>
> People using the new interface can do:
> try:
> import pyportmidi
> except ImportError:
> from pygame import midi as pyportmidi
>
>
> People using pypm C module directly for backwards compatibility can do:
> try:
> from pyportmidi import _pyportmidi as pypm
> except ImportError:
> try:
> import pypm
> except ImportError:
> from pygame import pypm as pypm
>
>
> ... or just remove the pygame fallbacks if wanted.
>
>
>
> On Mon, Jun 7, 2010 at 1:44 PM, Alexandre Quessy <[email protected]>wrote:
>
>> Hello René,
>> Ok. That makes sense for me.
>> That means the users will still be able to import directly pypm, by doing
>> this:
>>
>> from pyportmidi import _pyportmidi as pypm
>>
>> ?
>>
>> Alex
>>
>> 2010/6/7 René Dudfield <[email protected]>:
>> > 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/...
>> >
>>
>> --
>> Alexandre Quessy
>> http://alexandre.quessy.net/
>>
>
>
>
_______________________________________________
media_api mailing list
[email protected]
http://lists.create.ucsb.edu/mailman/listinfo/media_api
