sikuli-driver team mailing list archive

[David Michael Pennington <906343@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

The issue is simple, long-time Jython users have no intuitive way to use
Jython's traditional 'type()' command to introspect data types [Ref 1].

This is a serious problem for anyone who is used to Jython.  When we get
any kind of data, it is normal to look at it to ensure that you got what
you expected (particularly since Jython uses duck typing) [Ref 2].

References:
[1]: http://www.jython.org/jythonbook/en/1.0/DataTypes.html
[2]: http://www.jython.org/jythonbook/en/1.0/ObjectOrientedJython.html

** Affects: sikuli
     Importance: Undecided
         Status: New


** Tags: jython type

-- 
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/906343

Title:
  Sikuli's "type" command collides with Jython's type command

Status in Sikuli:
  New

Bug description:
  The issue is simple, long-time Jython users have no intuitive way to
  use Jython's traditional 'type()' command to introspect data types
  [Ref 1].

  This is a serious problem for anyone who is used to Jython.  When we
  get any kind of data, it is normal to look at it to ensure that you
  got what you expected (particularly since Jython uses duck typing)
  [Ref 2].

  References:
  [1]: http://www.jython.org/jythonbook/en/1.0/DataTypes.html
  [2]: http://www.jython.org/jythonbook/en/1.0/ObjectOrientedJython.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/906343/+subscriptions