Region.type() conflict with builtin type() function --- workaround
Bug #794880 reported by
anatoly techtonik
This bug report is a duplicate of:
Bug #906343: X-1.0rc3: Sikuli's "type" command collides with Jython's type command --- workarounds.
Edit
Remove
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
SikuliX |
New
|
Undecided
|
Unassigned |
Bug Description
*** workaround
the builtin type function can be called using __builtin__.type().
(You would also need to import __builtin__)
... and you could use isinstance()
-------
I've just realized that Region.type() is imported in global scope and shadows builtin type() function, which makes debugging harder.
To post a comment you must log in.
Yes, that is really an API design mistake.
I would suggest to deprecate type() and implement a new typing feature that eliminates the keyboard layout and special character problems of type().