Python Scripting Extension 1.0.1rc1 Released

Python Scripting Extension 1.0.1rc1 has been released on July 23rd, 2010.

This release is the first release candidate for 1.0.1. This release is marked as "not for production". The current plan is to allow one week for the community to validate this release. If you find any major issues please report them to our bug and issue tracker. If no major issues have been identified by July 30th, then creation of 1.0.1 will proceed. Currently, 1.0.1 is scheduled to be available on August 10th and it will be a production release and can be used to create production products. Please download and validate this release to help ensure 1.0.1 is a great release!

View complete list of new features and fixed bugs.

Download Python Scripting Extension

New Features

• The Python Scripting Extension no longer bundles a copy of the Python interpreter runtime. This makes the downloads of the extension significantly smaller (under 300 KB). However, it does add the requirement that you must download and install a copy of the Python interpreter (either Python 2.4.X, Python 2.5.X or Python 2.6.X) on your system before using this extension. The rationale for this change was that users may have their own install of Python configured with other useful Python libraries (NumPy, Matplotlib, PyQt) and forcing them to use a bundled Python interpreter was confusing. (EXTRAS-75).
• The Python Scripting Extension now works with the Windows 64-bit release of Opticks, in addition to the existing support for Windows 32-bit release of Opticks. This is only supported with Python 2.6, not Python 2.5 or Python 2.4. Those earlier versions of Python do not have adequate 64-bit support. (EXTRAS-72)
• The user can now configure which install of Python to use with a new option in the "Tools\Options..." dialog under "Scripting\Python". (EXTRAS-69)
• The opticks.data.raster.RasterElement class has a new property, "info" that is used to access the dimensions instead of needing to construct a opticks.data.types.DataInfo object. (EXTRAS-68)
• The opticks.view.layer.RasterLayer class has the following additions (EXTRAS-55):
  • Properties:
    • rgbdisplayed
  • Methods:
    • getdisplayedband(channel)
    • setdisplayedband(channel, band, rasterElement)
    • getstatistics(channel, component)
    • setrgbbands(red=None,green=None,blue=None)
    • setgraybands(gray)
• The opticks.data.types.DataElement and all subclasses have a new property, "metadata" that can be used to access the metadata instead of needing to construct an opticks.metadata.DynamicObject() instance. (EXTRAS-52)
• A new Python module, opticks_q, has been added. This is a collapsed version of the modules and sub-modules in the opticks module. For example, you can now use opticks_q.RasterLayer instead of or in addition to opticks.view.layer.RasterLayer, or opticks_q.RasterElement instead of or in addition to opticks.data.raster.RasterElement. This was done to reduce the typing required when using the Scripting Window. (EXTRAS-50)

Bug Fixes

• The "Python User Configuration File" set in "Tools\Options..." can now contain more than one line of Python code. (EXTRAS-70)
• You can now set a opticks.metadata.DynamicObject() as the value for a given key in another opticks.metadata.DynamicObject() instance. (EXTRAS-54)
• The opticks.data.raster.RasterElement.getDataPointerArray() would always return a NumPy array with a shape of BIP interleave or (rows, columns, bands) even if the data was not stored in that interleave. This function now returns a NumPy array with a shape that matches the layout of the data returned. (EXTRAS-53)
• There was a problem typing nested blocks into the Scripting Window. The Python code in the nested block would be executed when it should not have been, resulting in very counter-intuitive behavior. (EXTRAS-46)
• Printing to sys.stderr will now work properly. Previously any code printing to sys.stderr including other installed Python libraries would cause the output to be lost. (EXTRAS-45)

Supported Opticks Versions

• This extension is supported in any version of Opticks 4.3.X that is Opticks 4.3.3 or later.