Using api.launchpad.net is arguably slightly cleaner because it's what our official Python bindings use, but it's basically just a coincidence that api.l.n happens not to be affected by this issue right now so I don't think you should frame it as a bug-fix. The only reason that api.l.n isn't currently affected is that I haven't switched it over to the new frontend stack yet - I'm deliberately holding off on that until we've got this bug fixed properly.
Using api.launchpad.net is arguably slightly cleaner because it's what our official Python bindings use, but it's basically just a coincidence that api.l.n happens not to be affected by this issue right now so I don't think you should frame it as a bug-fix. The only reason that api.l.n isn't currently affected is that I haven't switched it over to the new frontend stack yet - I'm deliberately holding off on that until we've got this bug fixed properly.