Changes since 0.2:

* Add igor.packed.walk for traversing a packed experiment filesystem.
* Add igorpackedexperiment.py to setup.py script list.
* Add -p/--plot option so scripts will plot waves.
* Adjust copyright to LGPLv3+
* Assorted bugfixes

I haven't actually tested all of these, but I doubt I did anything so
magical that support has been dropped in the meantime ;).  It would be
nice to drop the doctests [1], but until then testing Python 3 is
going to be difficult.

[1]: https://github.com/wking/igor/pull/1#issuecomment-190309065

ArgumentParser lost its undocumented version argument in 3.3.0
[1,2,3].  The version action is the documented way to do this [4].

[1]: http://bugs.python.org/issue13248
[2]: https://hg.python.org/cpython/rev/5393382c1b1d
[3]: https://hg.python.org/cpython/file/374f501f4567/Misc/HISTORY#l477
[4]: https://docs.python.org/3/library/argparse.html#action

Catch up with 551d9bca (Fix DynamicLabelsField parsing algorithm.,
2012-08-20).

The old algorithm collapsed null bytes early on.  The new algorithm
keeps the null bytes until the 32-byte chunks have been read.

Parsing hooke/test/data/vclamp_mfp3d/Line0004Point0001.ibw with the
old algorithm gave labels as

  [[], ['RawDeflLVDT'], [], []]

The new algorithm gives

  [[], ['', 'Raw', 'Defl', 'LVDT'], [], []]

On Thu, Jul 26, 2012 at 09:25:20AM -0700, Paul Kienzle wrote:
> Your .py files are licensed as LGPL but the overall project is
> listed as GPL.  Much of the python numerics world is BSD licensed,
> so LGPL is a closer match to the community.  Do you mind changing
> the project to LGPL?

This improves on the old method of assuming they were scalar if
.item_count was 1.

The tests pass on Python 2.7, and all the failures on Python 3.2 are
string/bytes display issues.

I don't know if encoding information is embedded in the IGOR files or
not.  Currently the stock parser just leaves everything it reads in in
bytes.  For compatibility, the igorpy module attempts to convert those
byte strings to Unicode, but it just assumes that the encoding used in
the file matches the locale or default encoding used by your system.
This could be a portability issue.  Until commit

  commit fe7006e3
  Author: W. Trevor King <wking@tremily.us>
  Date:   Sat Jul 21 07:50:09 2012 -0400

    Replace igor.igorpy parsing with translations from igor.packed.load.

The igorpy parser used sys.getfilesystemencoding() to guess the
encoding, but that encoding is actually used to encode file names, not
file contents.  locale.getpreferredencoding is a better guess, but
it's still just a guess.

Python 3 exceptions no longer have a .message attribute.

In Python 3, the floating point division lead to:

    Traceback (most recent call last):
      ...
      File ".../igor/struct.py", line 255, in unpack_data
        items = [next(iterator) for i in range(self.arg_count)]
    TypeError: 'numpy.float64' object cannot be interpreted as an integer

This breaks Python 2 Unicode handling, but it allows igorpy to be used
in its raw form by Python 3.

To avoid conflicts with the build-in `-v` `--version` argument, the
short form of `--verbose` is now `-V`.

If we're not going to be printing the formatted data in the log, don't
bother calculating it.  On my system, this speeds up the loading of
polar-graphs-demo.pxp by a factor of 10.