[01:24] <carlos> SteveA: Which way is the best one (for you) to do python bindings for a C library
[01:24] <carlos> hmm, SteveA or any other of you :-)
[04:14] <SteveA> hello carlos
[04:14] <carlos> hi
[04:14] <SteveA> first, look at using pyrex
[04:16] <carlos> ok
[04:17] <SteveA> it allows you to write in a subset of python that gets compiled directly into C
[04:17] <SteveA> I think PEAK has various examples of using pyrex like this
[04:20] <carlos> I think I have seen it before when I was playing with python DBUS bindings
[04:22] <carlos> but I saw other ways to do it and didn't know which one is the more usual.
[04:22] <carlos> Thank you
[04:42] <SteveA> pyrex should be easier than writing a bunch of C
[04:42] <SteveA> I'd generally avoid swig
 the rosetta subdomain is still "move along" ?
[04:50] <carlos> SteveA: should we remove it?
[04:51] <carlos> rosetta.ubuntu.com
[05:17] <SteveA> yeah, I guess so.  or have it redirect to launchpad/rosetta
[05:19] <carlos> will ask to elmo/thom after holidays
[05:23] <SteveA> okay
[05:23] <SteveA> file a bug perhaps :-)
[05:24] <carlos> SteveA: do we have a product for that kind of bugs?
[05:28] <SteveA> we should probably have one called "launchpad deployment"
[05:31] <lamont> question: how does baz branch differ from tla tag?  Answer: why, it changes your default version to the branch, so that you suddenly work there instead of where you thought you were.
[05:32] <lamont> I _was_ tagging over to a releases branch, but that was before I last released the source.
[05:33] <bob2> it only does that if you use the one argument version
[05:33] <bob2> on the assumeption that you want magic
[05:34] <lamont> that's what I get for asking for help and typing exactly what I'm told, eh?
[05:34] <bob2> the long help mentions it
[05:34] <bob2> should it be in te short help, too?
[05:35] <lamont> so, what's the magic command to bring all my changes from my release branch back onto my mainline branch?
[05:35] <bob2> in your mainline branch tree, run 'baz merge lamont@.../blah--release--0'
[05:36] <lamont> baz: unrecognized command (merge)
[05:36] <bob2> oh, star-merge in hoary, I guess
[05:36] <lamont> or is this what I get for using the current supported version of baz (1.0.1)?
[05:36] <lamont> baz star-merge lamont.jones@canonical.com--2004-work/buildd-config--versions-0.1
[05:36] <lamont> star-merge: invalid FROM revision spec (lamont.jones@canonical.com--2004-work/buildd-config--versions-0.1)
[05:37] <lamont> ah, that means 'missing -'
[05:37] <bob2> ah
[05:37] <bob2> that error is shite, too
[05:38] <SteveA> it needs more of a sense of PANIC perhaps
[05:47] <lamont> bob2: thanks
[05:47] <bob2> you're welcome
[05:48] <bob2> if things annoy you, please file bugs so we can fix it
[05:48] <lamont> I'm just waiting to be told that I need to install 1.1 so that I can complain that you don't support your releases... :-)
[05:48] <bob2> haha
[05:48] <lamont> I've already been told several times that 1.1 is better.  But it just doesn't exist yet for us distro folks...
[05:49] <bob2> hey, we support it, we just don't remember it ;)
[05:49] <bob2> there's an auto-built apt source on bazaar.canonical.com for it
[05:50] <lamont> right - but I just pull from hoary - if it's not uploaded, then obviously it's not ready :-)
[05:50] <bob2> haha
[05:50] <lamont> anyway, christmas stuff to do today, back later.
[05:50] <bob2> fair enough, 1.1 should be out in a bit, then in hoary
[05:50] <bob2> sure, adios
[06:19] <jblack> Merry christmas bob2
[06:19] <jblack> And all you other wallaby-hugger types. :) 
[11:37] !lilo:*! added group contact: No-Sources, a Linux kernel source patch set for workstations or desktop machines (http://no.oldos.org/files/); category: informal/FOSS