setup.py: Claim compatibility through 3.5 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
igor.script: Replace ArgumentParser(version=...) with a version argument 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
Fix DynamicLabelsField parsing algorithm. 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'], [], []]
Clear up copyright ambiguity by changing to LGPLv3+. 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?