Sorry it's been so quiet on the BEEPy front lately. The silly season,=20
actual paid work, other projects and a MOTOS have all contributed to
the slowdown in BEEPy updates. However...
Rejoice! For I have actually done something today. I've gone and added
a distutils setup.py script to CVS in preparation for release 0.3. I
don't think I'll be doing much in the way of functionality as I'd
previously indicated, but that's more a result of the hassles I've
encountered in finding a decent SSL implementation/OpenSSL interface for
Python. I _will_ get onto this sometime soon, because I want it.
That said, considering how easy it was to get the distutils script up and
running, I wish I'd done it earlier. Now that I have seen the light, I'm
keen to get an easy-to-install package up on the sourceforge site so that
people can get a hold of some usable code nice and easily. Hopefully that
will encourage greater BEEPy use, which will encourage me to get better
code implemented. Who knows, someone might even send me patches one day. ;)
Oh, one last thing: I did a directory re-shuffle with beep/test moving up
to the top level along with beep and doc. I've also packaged things up
to install as beepy.* for namespace reasons and this has broken a few
references, which I'm fixing one at a time. I'll probably release 0.3
once I get test/testall.py completing successfully again.
Anyhow, more detail on http://beepy.eigenmagic.com/ as usual.
Justin Warren - Senior Consulting Engineer, Unicity Pty Ltd
Get latest updates about Open Source Projects, Conferences and News.