libsupport.get_launchpad doesn't automatically create LP credentials on first use
Bug #689100 reported by
Stefano Rivera
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-dev-tools (Ubuntu) |
Fix Released
|
Wishlist
|
Unassigned |
Bug Description
Do we really need manage-credentials?
In fact, can the lp api mode of requestsync become the default (once it automatically handles application authorization)?
First issue get_launchpad.
Also, launchpadlib credentials management is changing. LP: #686690
Changed in ubuntu-dev-tools (Ubuntu): | |
importance: | Undecided → Wishlist |
summary: |
- [requestsync] Unnecessarily complicated to use LP API + libsupport.get_launchpad doesn't automatically create LP credentials on + first use |
description: | updated |
To post a comment you must log in.
I agree that we should get rid of manage-credentials (see also bug 387297) and that we could make the LP API default if there is a consensus for it.
But what you mean with "homegrown launchpad api wrapper"? ubuntutools/ lp/lpapicache. py? That's relatively new to speed up requestsync. It caches objects fetched through the LP API to not refetch them (which is slow) on every use throughout the script.
Other scripts can use it too but as most are less complex there is no strong benefit from it.