=== stub [~stub@dsl-246.248.240.220.dsl.comindico.com.au] has joined #launchpad === jordi [~jordi@115.Red-213-96-69.pooles.rima-tde.net] has joined #launchpad === SteveA [~steve@adsl-213-190-44-43.takas.lt] has joined #launchpad === carlos [~carlos@69.Red-80-33-181.pooles.rima-tde.net] has joined #launchpad [01:24] SteveA: Which way is the best one (for you) to do python bindings for a C library [01:24] hmm, SteveA or any other of you :-) [04:14] hello carlos [04:14] hi [04:14] first, look at using pyrex [04:16] ok [04:17] it allows you to write in a subset of python that gets compiled directly into C [04:17] I think PEAK has various examples of using pyrex like this [04:20] I think I have seen it before when I was playing with python DBUS bindings [04:22] but I saw other ways to do it and didn't know which one is the more usual. [04:22] Thank you [04:42] pyrex should be easier than writing a bunch of C [04:42] I'd generally avoid swig [04:50] the rosetta subdomain is still "move along" ? [04:50] SteveA: should we remove it? [04:51] rosetta.ubuntu.com [05:17] yeah, I guess so. or have it redirect to launchpad/rosetta [05:19] will ask to elmo/thom after holidays [05:23] okay [05:23] file a bug perhaps :-) [05:24] SteveA: do we have a product for that kind of bugs? [05:28] we should probably have one called "launchpad deployment" === lamont [~lamont@mix.mmjgroup.com] has joined #launchpad === lamont looks around for someone to hurt === carlos hides [05:31] 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] I _was_ tagging over to a releases branch, but that was before I last released the source. [05:33] it only does that if you use the one argument version [05:33] on the assumeption that you want magic [05:34] that's what I get for asking for help and typing exactly what I'm told, eh? [05:34] the long help mentions it [05:34] should it be in te short help, too? [05:35] so, what's the magic command to bring all my changes from my release branch back onto my mainline branch? [05:35] in your mainline branch tree, run 'baz merge lamont@.../blah--release--0' [05:36] baz: unrecognized command (merge) [05:36] oh, star-merge in hoary, I guess [05:36] or is this what I get for using the current supported version of baz (1.0.1)? [05:36] baz star-merge lamont.jones@canonical.com--2004-work/buildd-config--versions-0.1 [05:36] star-merge: invalid FROM revision spec (lamont.jones@canonical.com--2004-work/buildd-config--versions-0.1) [05:37] ah, that means 'missing -' [05:37] ah [05:37] that error is shite, too [05:38] it needs more of a sense of PANIC perhaps === carlos -> out [05:47] bob2: thanks [05:47] you're welcome [05:48] if things annoy you, please file bugs so we can fix it [05:48] 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] haha [05:48] 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] hey, we support it, we just don't remember it ;) [05:49] there's an auto-built apt source on bazaar.canonical.com for it [05:50] right - but I just pull from hoary - if it's not uploaded, then obviously it's not ready :-) [05:50] haha [05:50] anyway, christmas stuff to do today, back later. [05:50] fair enough, 1.1 should be out in a bit, then in hoary [05:50] sure, adios [06:19] Merry christmas bob2 [06:19] And all you other wallaby-hugger types. :) === SteveA [~steve@adsl-213-190-44-43.takas.lt] has joined #launchpad === SteveA [~steve@adsl-213-190-44-43.takas.lt] has joined #launchpad [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