Tom Insam

I have a lot of different python projects in a lot of different directories, and like them all to have their own virtualenv. Because I can’t even be bothered to type a single line of code to activate them, I’ve ended up with this (slightly insane) setup:

Every project folder has a ./venv/ which is where I keep the virtualenv. Then, in my .bash_profile, I have the following snippet:

__activate_venv() {
  if [ -f ./venv/bin/activate ]
    . ./venv/bin/activate
    hash -r
    if (type deactivate >/dev/null 2>&1)
      hash -r
export PROMPT_COMMAND="__activate_venv"

In short - if the current directory has a venv/bin/activate script, then run it. Otherwise, if there’s something called deactivate that I can call, then do so.

So whenever I cd into a folder that has a ./venv/, it activates, and whenever I leave, it deactivates. This is probably insane.

[..] after the June 1 deadline, Apple issued non-bug-fix updates such as iPhoto 9.3 and Aperture 3.3, yet they remain unsandboxed. Meanwhile, I’ve heard from at least one developer that Apple deemed a third-party 0.0.1 bug-fix update to not be a bug-fix, and so rejected it for not being sandboxed

Apple have an interesting problem with their app stores. On iOS, they’re (very) gradually relaxing conditions towards a hypothetical glorious future state where everyone is both happy and secure. There are still random annoying rejections, but for the most part it feels better now than it ever did.

On MacOS, though, they’re going in the opposite direction. It appears that Apple’s vision of the glorious future of MacOS apps is a lot more restricted than the current state, so every time the conditions change, they change to be more restrictive, not less. Sandboxing is just the latest instance of this.

Every time Apple relax the iOS restrictions a little, or makes the platform more powerful, they enable better apps. The platform’s backwards-compatibility is superb, and apps I bought on day 1 of the store being open still work.

But every time they squeeze the MacOS restrictions tighter, more apps that used to be permitted can now no longer fit. This isn’t a situation that gives me great faith that things I buy from the Mac App Store will continue to work in the future, or get bug fixes.

Of course, in practice, I’m going to keep buying from the store. It’s far more convenient than anything else.

Michael Tsai - Blog - Dogfooding the Sandbox

There’s free wireless on bits of the London Underground now - so far available at a few of the central London Victoria line stations. It’s operated by Virgin Media, which is convenient because I use them for internet acces at home as well, so it’ll going to stay free for me after the Olympics. But like all public wifi, it acts in a slightly weird way that I’ve been trying to figure out.

Specifically, the first (few?) HTTP request(s) that my phone makes on the connection get intercepted and redirected (I’m doing this on a phone, so I don’t have a lot in the way of fine-grained header debugging) to an advert / splash screen for the Virgin Media service provider. Non-HTTP stuff seems to be unaffected, specifically HTTPS isn’t touched - I can use my Twitter client as soon as the wireless has connected, but the first attempt at browsing gets hijacked.

This behaviour is playing havok with the Lanyrd iPhone app (which I wrote, so have a special interest in) - it’s got a lot of views that are built from HTML in UIWebViews, and though all the API calls it makes go over HTTPS, I have made the mistake of fetching the templates over plain HTTP, so half the in-app views are suddenly adverts for central London attractions. Weirdly, I get different pages in the Lanyrd app than I can persuade the web browser to serve. I need to spend some quality time just sitting on an underground platform with a laptop debugging things. Which probably won’t get me arrested..

In the past I’ve also had problems with some mobile phone HTTP gateways stripping out / optimizing HTML, stripping out comments, for instance. But this is more disruptive than most connections I have easy access to.

We immediately began to investigate the issue and found that there was a cascading bug in one of our infrastructure components. [..] A “cascading bug” is a bug with an effect that isn’t confined to a particular software element, but rather its effect “cascades” into other elements as well. One of the characteristics of such a bug is that it can have a significant impact on all users, worldwide, which was the case today,

Twitter Blog: Today’s turbulence explained

This is some usage of the word “explained” that I am not familiar with.



Tumblr for iPhone 3.0: Now available on the App Store

iPhone users rejoice! We’ve redesigned and rewritten the app from the ground up, so get ready for an even better Tumblr experience:

  • Sleeker Dashboard: High-res images, Spotify support, improved photosets, and more.
  • New post forms: Faster uploads and handy shortcuts (swipe the compose button up for camera, swipe left for text)!
  • Offline support: Post, like, reply, and reblog even when you’re not connected!
  • Speed: Faster, super-responsive interface.
  • Tag search and Radar!

Enjoy all these amazing features and much more! Download the app now.

My goodness, this is a nice-looking app.