Hi Seth, I just wanted to comment on the python side of things.
I'm the author of the binding and sadly it's now used by some of the very well used bits of LXC (lxc-ls and lxc-start-ephemeral to list the most populars), so I don't think building without this is really an option for us. However I'm very very interested in having those issues resolved. To be clear, this binding is probably the first bit of C code that I actually wrote from scratch and released and so I certainly expected the memory management to be mostly crap. We've fixed a bunch of issues already but your comments are really useful to fix the rest of those. I'll try to set aside some time tomorrow to poke at those and will provide a patch here for Serge and you (if you're interested) to review. The trick with those bindings and the way LXC work is that it's almost impossible to run those through valgrind to detect leaks so we almost entirely depend on the eyes of our reviewers and even though we're pretty strict on code reviews nowadays, there's only so much you can find on thousands of line long diffs ;) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/509647 Title: [MIR] lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/509647/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
