Comment 4 for bug 670013

OK, I've verified that the versions of launchpadlib in Karmic, Lucid and Maverick all use staging by default. However, that's just a default. It's possible that applications like ground control use edge by default, or are hard-coded to use edge. To say nothing of individuals' scripts. I don't think "we don't use edge by default" short-circuits the need to see what happens to launchpadlib if edge goes away.

I experimented with setting up redirects on my personal website, and pointing launchpadlib at my personal website. The first thing launchpadlib tried to do was POST to +request-token on my personal website. My redirect caused launchpadlib to raise an exception, because it's illegal for a POST that results in a redirect to be re-POSTed without user input. This means that if you don't already have a credential for edge.launchpad.net, and you use a script that tries to access edge, you will get an exception. launchpadlib won't re-POST given the redirect.

If you already have a credential, it *almost* works, but not quite. The GET for the WADL is redirected and the WADL is downloaded. But once you try to use some feature of the web service, launchpadlib notices that the base URL in the WADL is different from the "service root" URL. It gets confused and falls over.

So, redirects won't solve the problem for old versions of launchpad. But, people who use old versions of launchpad are not using edge by default.