3Oct/083
Stopping Maintenance
Gary and I are stopping maintenance and support on various developer libraries we've created over the years. If anyone is actually using these libraries and wants take over their maintenance, please let one of us know:
- Audio Enriched Links
- PMIDI
- pyAA
- pyFMOD
- pyIFC
- pyOpenAL
- pyHook
- pySonic
- pySonicEx
The code and builds for these projects currently posted at http://sf.net/projects/uncassist and http://sf.net/projects/pysonic will remain in place, but we will no longer update them.
Two fellows have already contacted me about maintaining pyHook, but haven't set up shop yet. I'll provide a link to the new pyHook home page when they're ready.
We will continue maintaining pyTTS.
October 7th, 2008 - 06:44
Hi Peter, Well would you believe I just started using pyHook last week for a disambiguating keyboard project http://www.assembla.com/wiki/show/DKey
It works for me while we’re windows only and saved me messing around with ctypes etc. though I would like a platform agnostic version but haven’t spotted anything in GTK yet.
So I guess i’m happy to help keep an eye on it if anyone else is interested in it. Haven’t look at the code or the others though.
(please email me to repond)
March 2nd, 2009 - 21:05
Hi — I’ve been trying to use pyAA and I might be willing to maintain it. I noticed that the pyAAc.i on the sourceforge CVS is not in sync with the binary distribution. In particular it seems to be for Python 2.3 and there are a couple of methods that don’t exist. I’m guessing it is several months out of date.
So a. Are you still interested in a maintainer and b. Do you have the most recent pyAAc.i .
Good stuff.
You can send me an e-mail.
– Larry
March 14th, 2009 - 14:16
I think pyAA is a module that needs to be rewritten using something like comtypes or ditched completely in favor of a similar module from another project (e.g., http://monotonous.org/2008/07/01/introducing-pyia/, http://www.nvda-project.org/browser/trunk). If you’re still interested in maintaining it, however, that’s fine. Grab the source out of cvs, move it to its own project space, and let me know when I can take it down from the uncassist project on SourceForge.
Whatever version pyAAc.i is in cvs is the latest that I have. I think the newest binaries were contributed by someone years ago. If he/she made changes to the .i file, I do not have them.