sorry about that... that bug is fixed in master (and thus in 1.4.0.dev20+), but will continue to exist in the 1.3.x series