Category archives: Snaking

Discussions of programming, particularly of programming Python

RSS feed of Snaking

Finally got the baby (PyOpenGL) out the door (No empty-nest syndrome here...)


Just finishing up the 2.0.1.09 release of PyOpenGL. Rather annoying number of little details cropped up during the process of doing the release (missing files, bdist_wininst API not actually matching the API I'd suggested, (so requiring rewriting the function (after all the testing was done, of course, so blah if it breaks something)), files ...

Continue reading

UI Tweaks all day (Mostly making the topological graphics easier to use)


Crossed off three todo items, though looking back at them, they probably weren't the most important ones, they were just the ones that were annoying the heck out of me. All of them relate to the topological overview graphs.

Until today, you could only identify the root of these graphs by knowing what elements are ...

Continue reading

Stupid shallow bugs (Almost makes you want a statically-compiled language (well, not really))


Bryan found a bug in Cinemon this evening. It didn't pick up a modem migration event (modems changing channels). Turns out this was a trivial error; I'd mis-spelled a function name in a callback that only gets called 20 minutes into a run (and thus I was never around when it got called). The result ...

Continue reading

Sometimes a day evaporates with nothing to show for it (Oh, and Cinemon seems to be leaking *faster* now)


Spent much of the day staring at PySNMP code looking for something (anything!) that would make it faster without necessitating a bulk rewrite in C. Then gave in and started looking at what would be necessary to use net-snmp as an encoder/decoder for TwistedSNMP.

A few hours of tracking down and copying the various structures ...

Continue reading

PyOpenGL is just about ready for a release (Two or three bugs fixed, as well as a setup fix for Linux machines)


As I promised various users, spent much of the free time on the weekend on PyOpenGL, basically just working through the list of outstanding bugs. Nothing spectacular or new, just making things work the way they should.

Anyway, it's ready for a new release, but I don't want to be doing the release this late ...

Continue reading

New release of PyDispatcher available (Fixes 2 memory leaks)


While testing some memory-leak bug-fixes for PyOpenGL I discovered a memory leak in OpenGLContext. With a lot of tracking I found out that the leak was from Dispatcher.

Now, you may not care about that (I'm speaking to Bryan and Tim here), but Dispatcher is also used in Cinemon (which you will recall is currently ...

Continue reading

Don't seem to be firing on all cylinders (Can't seem to figure out how to make the statistics fast enough to be usable...)


For each group (say 50 groups), for each field (6 fields), for each modem in each group (2500 down to 4 or 5), collect the min, max, mean, and total. Problem is, even summarising 1 field for a 500 modem group is taking a long time (i.e. a second or more).

I'm obviously just doing ...

Continue reading

No panacea in max repetitions (But difficult to really tell what with the CMTS's changing)


Gather Bryan's been reconfiguring the demo instance to run against the larger CMTS (now scanning 2500 modems), so I don't know if there was any change in processing load between the limited and unlimited queries. Going to leave the changes in-place because it seems very likely that they will have a positive effect and no ...

Continue reading

Cleanliness is next to leak-less-ness (Or rather much-slower-leakish-ness...)


Well, the memory leak (whatever it is) is down to about 50MB/day. That's still not going to work in a production environment, but it's slow enough that the demo can run for about 11 days (well, make it 10, it needs some ram available for actually interacting with users). It's also slow enough that the ...

Continue reading