And because there's no way to just _get the source_ (ie. a tarball with source files in it) there's no way to download it without screwing with Apache.
Once you've got bzr 1.16.1 or later you can do bzr branch lp:launchpad to get the Launchpad code. That's pretty easy. Then, if you find yourself fixing a bug, you have a working tree in which to commit your changes. A tarball is a static lump with no history and no future, and if you want tomorrow's code, you'll have another big tarball to download.
It's as if they don't want anyone to download it.
...
And because there's no way to just _get the source_ (ie. a tarball with source files in it) there's no way to download it without screwing with Apache.
Once you've got bzr 1.16.1 or later you can do bzr branch lp:launchpad to get the Launchpad code. That's pretty easy. Then, if you find yourself fixing a bug, you have a working tree in which to commit your changes. A tarball is a static lump with no history and no future, and if you want tomorrow's code, you'll have another big tarball to download.
How about a way to browse it online?
http://bazaar.launchpad.net/~launchpad-pqm/launchpad/db-devel/changes