Category archives: Snaking
Discussions of programming, particularly of programming Python
String-schlepping for fun and profit (Well... not really much fun... and I don't make any money on this...)
Written by
on
in
Snaking.
Still working on getting the OpenGL extensions to compile. The bulk of the extensions compile fine, but there are new pointer-types being defined that are causing problems. I would guess I could just manually copy the appropriate definitions into the swig files, I just want to avoid too much manual maintenance of these files.
183 ...!-->!-->
PyOpenGL 2.0.2.01 nears release... (Could likely finish it if I wasn't writing this blog entry.)
Written by
on
in
Snaking.
Finished moving the (successful subset of the) PyOpenGL 2.1 dev branch into the 2.0.x maintenance branch. It's a considerable number of internal changes, hence bumping to 2.0.2 instead of just 2.0.1.10.
Biggest change is using the new SWIG, which causes ripple effects throughout the codebase. Not a lot of user-visible changes, really, but oh well. ...!-->!-->
PyTable starts growing PySQLite support (Embedded database for contract work...)
Written by
on
in
Snaking.
Decided this afternoon to make PySQLite one of the supported databases for PyTable. Got much of the base work done (mostly just tracking down the proper queries for the various schema-extraction elements), but haven't really tried to use the result for anything.
I'm undertaking this little project largely because of the problems installing PostgreSQL for ...!-->!-->
Merging PyOpenGL's branches (Doesn't go too well...)
Written by
on
in
Snaking.
For the past few months I've had two active branches for PyOpenGL development. The 2.0.1.x branch and the 2.1.x branch. Problem is, 2.1 has basically not moved for 2 months, while 2.0.1 has had quite a few bug-fixes in that time.
So, spent the evening trying to merge the compatible changes into the 2.0.x branch ...!-->!-->
Somehow it went well (Or so I'm told...)
Written by
on
in
Snaking.
Turns out the SIP demo went well (or that's the message that got passed to me). Who'da thunk it.
Spent the rest of the day fixing a few bugs (and adding a minor feature) for Cinemon... come to think of it, I forgot to put part of the time (that before dinner) implementing the feature ...!-->!-->
Does anyone else look at cool database hacks and shudder? (RDBMSs are tools of the devil I tells ya!)
Written by
on
in
Snaking.
On Sunday D'Arcy had me review some of his code. Then at the UU meeting last night I was reminded of it by some of the comments by the "database weenies" (actually nice guys, I'm just using it for dramatic effect) when a fairly green programmer mentioned that he knew MySQL and half the room ...
Stupid bug/feature in Cygwin trashes the SIP demo (Blah and double-blah...)
Written by
on
in
Snaking.
So today something like 2.5 or 3 hours was spent on the SIP demo (specifically getting it installed on a laptop, and then figuring out why that didn't work). Problem is, while the demo itself is a simple set of executables with its support files all zipped up in a nice package, it still requires ...
What I would do if I wasn't doing contract work only... (Speculative learning for the short term...)
Written by
on
in
Snaking.
Seems as though VoIP is becoming a hot topic. I should probably sit down for a week and master Shtoom so that we could offer custom VoIP work using it. Dave seems very up on the codebase, and my review of it for the SIP pager project certainly seemed to suggest that it's worth investigation ...
Have to figure out a better billing scheme ($2025 for 1.5 weeks of work just isn't functional...)
Written by
on
in
Snaking.
The root of the problem, of course, is discounting the time spent on learning, the time spent working through problems with libraries, etceteras. The "debugging is free" stuff is probably not a great idea either.
When I look at it over the last week-and-a-half, I've spent more than 60 hours on various aspects of the ...!-->!-->
Oh happy day (maybe) (A pox on relational databases...)
Written by
on
in
Snaking.
I seem to have worked around the big nasty evil database bug. And how, you may ask? By adding a completely extraneous commit into the middle of the hierarchy parsing code. ARGH. There's no reason for it to help, there's no way it should change anything. It's just some silly locking artefact where a SELECT ...