Asking for a specific autopilot stack backend should either succeed or raise an exception

Bug #1169355 reported by Thomi Richards
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Autopilot
Fix Released
High
Unassigned
autopilot (Ubuntu)
Fix Released
Undecided
Unassigned
Raring
Won't Fix
Undecided
Unassigned

Bug Description

Currently you can do this:

>>> from autopilot.input import Keyboard
>>> kbd = Keyboard.create("UInput")
>>> type(kbd)
autopilot.input._X11.Keyboard

So here autopilot has silently decided that it cannot give us the backend variant we asked for, and has decided that giving us anything is better than raising an exception.

However, I'm not sure that's a good idea.

Certainly creating a keyboard with:

kbd = Keyboard.create()

should return any keyboard. But if we ask for a specific type, we should either get that type, or fail.

Related branches

Changed in autopilot:
milestone: none → 1.3
Revision history for this message
PS Jenkins bot (ps-jenkins) wrote :

Fix committed into lp:autopilot at revision 159, scheduled for release in autopilot, milestone 1.3

Changed in autopilot:
status: In Progress → Fix Committed
Changed in autopilot:
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package autopilot - 1.3daily13.06.05-0ubuntu2

---------------
autopilot (1.3daily13.06.05-0ubuntu2) saucy; urgency=low

  * autopilot-touch only suggests python-ubuntu-platform-api for now.
    It's not in distro and we need that requirement to be fulfilled to
    have unity 7, 100 scopes and the touch stack to distro.
 -- Didier Roche <email address hidden> Fri, 07 Jun 2013 13:33:46 +0200

Changed in autopilot (Ubuntu):
status: New → Fix Released
Revision history for this message
Rolf Leggewie (r0lf) wrote :

raring has seen the end of its life and is no longer receiving any updates. Marking the raring task for this ticket as "Won't Fix".

Changed in autopilot (Ubuntu Raring):
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.