[lang]

Present Perfect

Personal
Projects
Packages
Patches
Presents
Linux

Picture Gallery
Present Perfect

Moules Frites

Filed under: Conference,Fluendo,Flumotion,Python,Twisted,Work — Thomas @ 17:49

2009-02-06
17:49

It went a little something like this.

I wrote a mail to our internal mailing list saying 'if anyone's coming to FOSDEM, I invite you to my place and I'll make moules frites for you.'

I was expecting, oh, I don't know, maybe four or five people.

After that, Pierre, our development manager started negotiating with our CEO to invite all the developers to FOSDEM. And he succeeded. And then the support team wanted to come too.

The result is now there are 14 people coming over for mussels and fries tonight.

This is what 14 kilos of mussels and 7.5 kilos of potatoes look like before preparing.

By the way, if you like mussels, you like programming (especially Python), and you like Barcelona, we are hiring again. (Actually, we also hire people that don't like mussels). You can also come talk to anyone on our team if you happen to be at FOSDEM so you don't have to take my word for how awesome working at Flumotion is. You should be able to recognize them by their shirts.

I get such a kick…

Filed under: Flumotion,Python — Thomas @ 18:21

2009-01-20
18:21

... out of watching Flumotion's interface for the streamer components when a big event is going on. The platform's launching streamers all over, and as soon as a new one starts, you just see the numbers flying up. Look, another one just started, and in its first minute it went up to 280 connections, and still climbing. For a 500 kbit/sec stream that means it goes from 0 to 140 Mbit/sec on that machine just for this stream.

We jumped up in a few hours to a good 14 Gbit/sec, which is still climbing.

The event in question, of course, is one of hope for the future - Obama's inauguration - streamed with Python, Twisted, and GStreamer.

Amsterdamned

Filed under: Conference,Flumotion,Work — Thomas @ 14:52

2008-09-11
14:52

Arrived last night, IBC starts on Friday and I'm setting the booth up with Pedro today.

Every time I have a hotel reservation for work for some reason the hotel always thinks the room's not paid for yet and ask me for payment. It's a curse.

On the plane I had a craving to go to the cinema later tonight, and as fate would have it the hotel is right across the street from a cinema. So the choice between a movie and a visit to the Red Light District was easy - I went to see Wanted. Mindless action fun, nicely shot, and ultimately forgettable.

Today, waiting for our cases of stuff to arrive. I'm sure they'll show up around 17.00, an hour before the IBC convention center closes.

In a cruel twist of fate, we have the sewer pipe of Akamai's booth that ends up in our booth and goes in a hole in the floor, so we have one floor tile sticking out. That's where we were planning to put our servers. So it goes.

At IBC we'll be demoing our freshly available commercial version of our Flumotion streaming server (we also have our new website online). A big thanks to Johan Dahlin, who is the only person in the world to have been hired by our company twice, and to Murray Cumming, who wrote our new Flumotion manual, which will be available online for the free version soon.

Maybe we should show some Dirac streaming too, since the BBC, David and Christian seem to be here.

GTK question

Filed under: Flumotion,GNOME,Hacking — Thomas @ 17:23

2008-07-24
17:23

We have a lot of text labels in Flumotion where we put mid-sentence newlines just so that once in a while the line gets broken and doesn't push the containing widget out wider than we want it to be.

Obviously this is a bogus way of doing things, but even our resident GTK+ wizard, Johan Dahlin, didn't have a ready answer for what the right way to do this is. So - how should we do it so that text gets flown correctly without mid-paragraph newlines and without ultra-wide widgets ?

The answer is probably superobvious.

pychecker and modules with the same name

Filed under: Flumotion,Hacking,Python — Thomas @ 00:09

2008-07-14
00:09

It took a lot more work than I expected, but I finally integrated the last of my pychecker patches into CVS just now.

This was a rather embarassing bug where pychecker would 'forget' about all warnings for A/C.py and B/C.py just because both files pretend to be a module called 'C' and pychecker was using sys.modules as a base for tracking stuff. Since pychecker imports all file arguments as a toplevel module, this clashes.

I created a unittest-based testsuite for pychecker, added a test for this particular case, then integrated my previous patch. I ran into an annoying problem though - some other tests now failed from the old testsuite.

Turns out that the code that checks if subclasses call up to superclass __init__ methods was using sys.modules to get to the code object and see if it was called. Since my patch now cleans up sys.modules from all these ad-hoc modules for the file arguments, this wasn't working anymore.

So I created a new module in pychecker to track all PyCheckerModule objects, and use that instead. They're tracked by module name and directory that module name can be loaded from.

It took a while originally before I realized pychecker had this bug - in Flumotion we have a lot of similarly-named files for different components, for example admin_gtk.py

PyChecker never caught any bug in these until I figured this bug out and created a patch.

So, I think I have now integrated all my 2 year old patches for pychecker, just in time for Neal's tentative code freeze. Yes, pychecker is actually going to get a release very soon! No more building custom packages for our contributors.

I'll leave the final testing for tomorrow.

« Previous PageNext Page »
picture