Authorization message uses stdout instead of stderr

[Agathe Porte]

When using the library, on first login, the authorization message will be displayed on stdout for the user to allow the application to access Launchpad by opening the link.

This pollutes stdout and prevents shell scripts from parsing the output of programs using launchpadlib, because stdout may get polluted on first use:

# On first run, this may return the whole authorization message before the actual value
myvar=$(myprogram-that-uses-launchpadlib)

# On second run, only the value we are interested in will be returned
myvar=$(myprogram-that-uses-launchpadlib)

Proposed solution is to use stderr instead, which will prevent this kind of failure.

[Jürgen Gmach (jugmac00)]

Thanks for the report.

Could you please paste the redacted output so it is easier to reason about your request?

launchpadlib is heavily used and integrated into many applications. I am worried that this kind of change might break other applications - for the better or worse.

[Launchpad Janitor (janitor)]

[Expired for launchpadlib because there has been no activity for 60 days.]