Powerdns autoserial patch #64
Comments
mamash
pushed a commit
that referenced
this issue
Aug 12, 2013
Changes since 1.1.0 (from git log):
issue #70: boolean flags may have true default
Merge pull request #69 from Tieske/master
general updates, mainly added CONTRIBUTING.md
Merge pull request #1 from mark-otaris/patch-1
Caught red handed, after a shameless copy 😄. Thx for the fix
This is Penlight, not Busted
added - a shameless copy of busted - CONTRIBUTING.md file
renamed docs to doc, to fix luarocks warning
updated readme to md format
changed .txt to .md files
added rockspec, fixed typo in filename
Merge pull request #67 from Tieske/add_executeex
added utils.executeex, which also returns output of stdout and stderr
updated, using readfile now, remove obsolete os.remove commands
Merge pull request #66 from Tieske/fix_temp
windows environment variable TMP is deprecated, use TEMP
mode binary mode optional (binary would require platform specific line endings to be converted which is not very portable, and mostly just text will do)
update: read files in binary mode
added utils.executeex, which also returns output of stdout and stderr
windows environment variable TMP is deprecated, use TEMP
HTML mode skips DOCTYPE; no globals harmed outside pl.utils
Merge pull request #64 from Tieske/fix_dir
fixed makepath creation, added/updated some documentation
fixed dirpath creation, added/updated some documentation
basic parser handles comments, and HTML mode is working nicely with real-world HTML
use LOM ordered attributes when stringifying if present (Danny).
manual merge of John Schember's readonly table support
Merge pull request #61 from user-none/isempty
Thanks, John!
Merge pull request #62 from CoolisTheName007/patch-2
Transform using values as keys.
missing locals
Set.issempty mispelling; default ctor borked; more tests
Transform using values as keys.
Merge remote-tracking branch 'upstream/master' into empty
Add function to check if an object is empty.
Merge pull request #53 from pkazmier/master
Added iterators to allow traversing tables in a sorted manner
Merge pull request #60 from theypsilon/master
base class methods invocation possible not only in method constructor _init
Adding new class method 'base' which can be used for calling base class methods easily
pl.class broke with classes that redefined __newindex; OrderedMap can now use normal indexing to assign keys in order
Merge pull request #54 from CoolisTheName007/patch-1
Typo fixed, libarary->library
Typo fixed.
Added tablex.sort and tablex.sortv to iterate over sorted elements
There are times when it would be convenient to iterate over a table
either by sorted keys or values. There is an example of this in the
PIL book. I added the two functions to tablex module, added two test
cases, and updated the PL manual.
Merge pull request #51 from pkazmier/master
Thanks!
lapp.add_type was broken due to uninitialized table variable.
The variable `types` was not initialized preventing `add_type` from
appending custom types to the variable. I also added a new test to
cover this test case in the future.
jperkin
pushed a commit
that referenced
this issue
Dec 9, 2013
Changes since 1.1.0 (from git log):
issue #70: boolean flags may have true default
Merge pull request #69 from Tieske/master
general updates, mainly added CONTRIBUTING.md
Merge pull request #1 from mark-otaris/patch-1
Caught red handed, after a shameless copy 😄. Thx for the fix
This is Penlight, not Busted
added - a shameless copy of busted - CONTRIBUTING.md file
renamed docs to doc, to fix luarocks warning
updated readme to md format
changed .txt to .md files
added rockspec, fixed typo in filename
Merge pull request #67 from Tieske/add_executeex
added utils.executeex, which also returns output of stdout and stderr
updated, using readfile now, remove obsolete os.remove commands
Merge pull request #66 from Tieske/fix_temp
windows environment variable TMP is deprecated, use TEMP
mode binary mode optional (binary would require platform specific line endings to be converted which is not very portable, and mostly just text will do)
update: read files in binary mode
added utils.executeex, which also returns output of stdout and stderr
windows environment variable TMP is deprecated, use TEMP
HTML mode skips DOCTYPE; no globals harmed outside pl.utils
Merge pull request #64 from Tieske/fix_dir
fixed makepath creation, added/updated some documentation
fixed dirpath creation, added/updated some documentation
basic parser handles comments, and HTML mode is working nicely with real-world HTML
use LOM ordered attributes when stringifying if present (Danny).
manual merge of John Schember's readonly table support
Merge pull request #61 from user-none/isempty
Thanks, John!
Merge pull request #62 from CoolisTheName007/patch-2
Transform using values as keys.
missing locals
Set.issempty mispelling; default ctor borked; more tests
Transform using values as keys.
Merge remote-tracking branch 'upstream/master' into empty
Add function to check if an object is empty.
Merge pull request #53 from pkazmier/master
Added iterators to allow traversing tables in a sorted manner
Merge pull request #60 from theypsilon/master
base class methods invocation possible not only in method constructor _init
Adding new class method 'base' which can be used for calling base class methods easily
pl.class broke with classes that redefined __newindex; OrderedMap can now use normal indexing to assign keys in order
Merge pull request #54 from CoolisTheName007/patch-1
Typo fixed, libarary->library
Typo fixed.
Added tablex.sort and tablex.sortv to iterate over sorted elements
There are times when it would be convenient to iterate over a table
either by sorted keys or values. There is an example of this in the
PIL book. I added the two functions to tablex module, added two test
cases, and updated the PL manual.
Merge pull request #51 from pkazmier/master
Thanks!
lapp.add_type was broken due to uninitialized table variable.
The variable `types` was not initialized preventing `add_type` from
appending custom types to the variable. I also added a new test to
cover this test case in the future.
jperkin
pushed a commit
that referenced
this issue
Jan 21, 2014
Changes since 1.1.0 (from git log):
issue #70: boolean flags may have true default
Merge pull request #69 from Tieske/master
general updates, mainly added CONTRIBUTING.md
Merge pull request #1 from mark-otaris/patch-1
Caught red handed, after a shameless copy 😄. Thx for the fix
This is Penlight, not Busted
added - a shameless copy of busted - CONTRIBUTING.md file
renamed docs to doc, to fix luarocks warning
updated readme to md format
changed .txt to .md files
added rockspec, fixed typo in filename
Merge pull request #67 from Tieske/add_executeex
added utils.executeex, which also returns output of stdout and stderr
updated, using readfile now, remove obsolete os.remove commands
Merge pull request #66 from Tieske/fix_temp
windows environment variable TMP is deprecated, use TEMP
mode binary mode optional (binary would require platform specific line endings to be converted which is not very portable, and mostly just text will do)
update: read files in binary mode
added utils.executeex, which also returns output of stdout and stderr
windows environment variable TMP is deprecated, use TEMP
HTML mode skips DOCTYPE; no globals harmed outside pl.utils
Merge pull request #64 from Tieske/fix_dir
fixed makepath creation, added/updated some documentation
fixed dirpath creation, added/updated some documentation
basic parser handles comments, and HTML mode is working nicely with real-world HTML
use LOM ordered attributes when stringifying if present (Danny).
manual merge of John Schember's readonly table support
Merge pull request #61 from user-none/isempty
Thanks, John!
Merge pull request #62 from CoolisTheName007/patch-2
Transform using values as keys.
missing locals
Set.issempty mispelling; default ctor borked; more tests
Transform using values as keys.
Merge remote-tracking branch 'upstream/master' into empty
Add function to check if an object is empty.
Merge pull request #53 from pkazmier/master
Added iterators to allow traversing tables in a sorted manner
Merge pull request #60 from theypsilon/master
base class methods invocation possible not only in method constructor _init
Adding new class method 'base' which can be used for calling base class methods easily
pl.class broke with classes that redefined __newindex; OrderedMap can now use normal indexing to assign keys in order
Merge pull request #54 from CoolisTheName007/patch-1
Typo fixed, libarary->library
Typo fixed.
Added tablex.sort and tablex.sortv to iterate over sorted elements
There are times when it would be convenient to iterate over a table
either by sorted keys or values. There is an example of this in the
PIL book. I added the two functions to tablex module, added two test
cases, and updated the PL manual.
Merge pull request #51 from pkazmier/master
Thanks!
lapp.add_type was broken due to uninitialized table variable.
The variable `types` was not initialized preventing `add_type` from
appending custom types to the variable. I also added a new test to
cover this test case in the future.
jperkin
pushed a commit
that referenced
this issue
Jan 21, 2014
FITS (Flexible Image Transport System) is a data format most used in astronomy.
PyFITS is a Python module for reading, writing, and manipulating FITS files.
The module uses Python's object-oriented features to provide quick, easy, and
efficient access to FITS files. The use of Python's array syntax enables
immediate access to any FITS extension, header cards, or data items.
Changes to 2.4.0 (in py-pyfits):
Changelog
===========
3.2 (2013-11-26)
----------------
Highlights
^^^^^^^^^^
- Rewrote CFITSIO-based backend for handling tile compression of FITS files.
It now uses a standard CFITSIO instead of heavily modified pieces of CFITSIO
as before. PyFITS ships with its own copy of CFITSIO v3.35 which supports
the latest version of the Tiled Image Convention (v2.3), but system
packagers may choose instead to strip this out in favor of a
system-installed version of CFITSIO. Earlier versions may work, but nothing
earlier than 3.28 has been tested yet. (#169)
- Added support for reading and writing tables using the Q format for columns.
The Q format is identical to the P format (variable-length arrays) except
that it uses 64-bit integers for the data descriptors, allowing more than
4 GB of variable-length array data in a single table. (#160)
- Added initial support for table columns containing pseudo-unsigned integers.
This is currently enabled by using the ``uint=True`` option when opening
files; any table columns with the correct BZERO value will be interpreted
and returned as arrays of unsigned integers.
- Some refactoring of the table and ``FITS_rec`` modules in order to better
separate the details of the FITS binary and ASCII table data structures from
the HDU data structures that encapsulate them. Most of these changes should
not be apparent to users (but see API Changes below).
API Changes
^^^^^^^^^^^
- Assigning to values in ``ColDefs.names``, ``ColDefs.formats``,
``ColDefs.nulls`` and other attributes of ``ColDefs`` instances that return
lists of column properties is no longer supported. Assigning to those lists
will no longer update the corresponding columns. Instead, please just
modify the ``Column`` instances directly (``Column.name``, ``Column.null``,
etc.)
- The ``pyfits.new_table`` function is marked "pending deprecation". This
does not mean it will be removed outright or that its functionality has
changed. It will likely be replaced in the future for a function with
similar, if not subtly different functionality. A better, if not slightly
more verbose approach is to use ``pyfits.FITS_rec.from_columns`` to create
a new ``FITS_rec`` table--this has the same interface as
``pyfits.new_table``. The difference is that it returns a plan ``FITS_rec``
array, and not an HDU instance. This ``FITS_rec`` object can then be used
as the data argument in the constructors for ``BinTableHDU`` (for binary
tables) or ``TableHDU`` (for ASCII tables). This is analogous to creating
an ``ImageHDU`` by passing in an image array.
``pyfits.FITS_rec.from_columns`` is just a simpler way of creating a
FITS-compatible recarray from a FITS column specification.
- The ``updateHeader``, ``updateHeaderData``, and ``updateCompressedData``
methods of the ``CompDataHDU`` class are pending deprecation and moved to
internal methods. The operation of these methods depended too much on
internal state to be used safely by users; instead they are invoked
automatically in the appropriate places when reading/writing compressed image
HDUs.
- The ``CompDataHDU.compData`` attribute is pending deprecation in favor of
the clearer and more PEP-8 compatible ``CompDataHDU.compressed_data``.
- The constructor for ``CompDataHDU`` has been changed to accept new keyword
arguments. The new keyword arguments are essentially the same, but are in
underscore_separated format rather than camelCase format. The old arguments
are still pending deprecation.
- The internal attributes of HDU classes ``_hdrLoc``, ``_datLoc``, and
``_datSpan`` have been replaced with ``_header_offset``, ``_data_offset``,
and ``_data_size`` respectively. The old attribute names are still pending
deprecation. This should only be of interest to advanced users who have
created their own HDU subclasses.
- The following previously deprecated functions and methods have been removed
entirely: ``createCard``, ``createCardFromString``, ``upperKey``,
``ColDefs.data``, ``setExtensionNameCaseSensitive``, ``_File.getfile``,
``_TableBaseHDU.get_coldefs``, ``Header.has_key``, ``Header.ascardlist``.
If you run your code with a previous version of PyFITS (>= 3.0, < 3.2) with
the ``python -Wd`` argument, warnings for all deprecated interfaces still in
use will be displayed.
- Interfaces that were pending deprecation are now fully deprecated. These
include: ``create_card``, ``create_card_from_string``, ``upper_key``,
``Header.get_history``, and ``Header.get_comment``.
- The ``.name`` attribute on HDUs is now directly tied to the HDU's header, so
that if ``.header['EXTNAME']`` changes so does ``.name`` and vice-versa.
- The ``pyfits.file.PYTHON_MODES`` constant dict was renamed to
``pyfits.file.PYFITS_MODES`` which better reflects its purpose. This is
rarely used by client code, however. Support for the old name will be
removed by PyFITS 3.4.
Other Changes and Additions
^^^^^^^^^^^^^^^^^^^^^^^^^^^
- The new compression code also adds support for the ZQUANTIZ and ZDITHER0
keywords added in more recent versions of this FITS Tile Compression spec.
This includes support for lossless compression with GZIP. (#198) By default
no dithering is used, but the ``SUBTRACTIVE_DITHER_1`` and
``SUBTRACTIVE_DITHER_2`` methods can be enabled by passing the correct
constants to the ``quantize_method`` argument to the ``CompImageHDU``
constuctor. A seed can be manually specified, or automatically generated
using either the system clock or checksum-based methods via the
``dither_seed`` argument. See the documentation for ``CompImageHDU`` for
more details. (#198) (spacetelescope/PYFITS#32)
- Images compressed with the Tile Compression standard can now be larger than
4 GB through support of the Q format. (#159)
- All HDUs now have a ``.ver`` ``.level`` attribute that returns the value of
the EXTVAL and EXTLEVEL keywords from that HDU's header, if the exist. This
was added for consistency with the ``.name`` attribute which returns the
EXTNAME value from the header.
- Then ``Column`` and ``ColDefs`` classes have new ``.dtype`` attributes
which give the Numpy dtype for the column data in the first case, and the
full Numpy compound dtype for each table row in the latter case.
- There was an issue where new tables created defaulted the values in all
string columns to '0.0'. Now string columns are filled with empty strings
by default--this seems a less surprising default, but it may cause
differences with tables created with older versions of PyFITS.
- Improved round-tripping and preservation of manually assigned column
attributes (``TNULLn``, ``TSCALn``, etc.) in table HDU headers.
(astropy/astropy#996)
Bug Fixes
^^^^^^^^^
- Binary tables containing compressed images may, optionally, contain other
columns unrelated to the tile compression convention. Although this is an
uncommon use case, it is permitted by the standard. (#159)
- Reworked some of the file I/O routines to allow simpler, more consistent
mapping between OS-level file modes ('rb', 'wb', 'ab', etc.) and the more
"PyFITS-specific" modes used by PyFITS like "readonly" and "update".
That is, if reading a FITS file from an open file object, it doesn't matter
as much what "mode" it was opened in so long as it has the right
capabilities (read/write/etc.) Also works around bugs in the Python io
module in 2.6+ with regard to file modes. (spacetelescope/PyFITS#33)
- Fixed an obscure issue that can occur on systems that don't have flush to
memory-mapped files implemented (namely GNU Hurd). (astropy/astropy#968)
3.1.3 (2013-11-26)
------------------
- Disallowed assigning NaN and Inf floating point values as header values,
since the FITS standard does not define a way to represent them in. Because
this is undefined, the previous behavior did not make sense and produced
invalid FITS files. (spacetelescope/PyFITS#11)
- Added a workaround for a bug in 64-bit OSX that could cause truncation when
writing files greater than 2^32 bytes in size. (spacetelescope/PyFITS#28)
- Fixed a long-standing issue where writing binary tables did not correctly
write the TFORMn keywords for variable-length array columns (they ommitted
the max array length parameter of the format). This was thought fixed in
v3.1.2, but it was only fixed there for compressed image HDUs and not for
binary tables in general.
- Fixed an obscure issue that can occur on systems that don't have flush to
memory-mapped files implemented (namely GNU Hurd). (Backported from 3.2)
3.0.12 (2013-11-26)
-------------------
- Disallowed assigning NaN and Inf floating point values as header values,
since the FITS standard does not define a way to represent them in. Because
this is undefined, the previous behavior did not make sense and produced
invalid FITS files. (Backported from 3.1.3)
- Added a workaround for a bug in 64-bit OSX that could cause truncation when
writing files greater than 2^32 bytes in size. (Backported from 3.1.3)
- Fixed a long-standing issue where writing binary tables did not correctly
write the TFORMn keywords for variable-length array columns (they ommitted
the max array length parameter of the format). This was thought fixed in
v3.1.2, but it was only fixed there for compressed image HDUs and not for
binary tables in general. (Backported from 3.1.3)
- Fixed an obscure issue that can occur on systems that don't have flush to
memory-mapped files implemented (namely GNU Hurd). (Backported from 3.2)
3.1.2 (2013-04-22)
------------------
- When an error occurs opening a file in fitsdiff the exception message will
now at least mention which file had the error. (#168)
- Fixed support for opening gzipped FITS files by filename in a writeable mode
(PyFITS has supported writing to gzip files for some time now, but only
enabled it when GzipFile objects were passed to ``pyfits.open()`` due to
some legacy code preventing full gzip support. (#195)
- Added a more helpful error message in the case of malformatted FITS files
that contain non-float NULL values in an ASCII table but are missing the
required TNULLn keywords in the header. (#197)
- Fixed an (apparently long-standing) issue where writing compressed images
did not correctly write the TFORMn keywords for variable-length array
columns (they ommitted the max array length parameter of the format). (#199)
- Slightly refactored how tables containing variable-length array columns are
handled to add two improvements: Fixes an issue where accessing the data
after a call to the `pyfits.getdata` convenience function caused an
exception, and allows the VLA data to be read from an existing mmap of the
FITS file. (#200)
- Fixed a bug that could occur when opening a table containing
multi-dimensional columns (i.e. via the TDIMn keyword) and then writing it
out to a new file. (#201)
- Added use of the console_scripts entry point to install the fitsdiff and
fitscheck scripts, which if nothing else provides better Windows support.
The generated scripts now override the ones explicitly defined in the
scripts/ directory (which were just trivial stubs to begin with). (#202)
- Fixed a bug on Python 3 where attempting to open a non-existent file on
Python 3 caused a seemingly unrelated traceback. (#203)
- Fixed a bug in fitsdiff that reported two header keywords containing NaN
as value as different. (#204)
- Fixed an issue in the tests that caused some tests to fail if pyfits is
installed with read-only permissions. (#208)
- Fixed a bug where instantiating a ``BinTableHDU`` from a numpy array
containing boolean fields converted all the values to ``False``. (#215)
- Fixed an issue where passing an array of integers into the constructor of
``Column()`` when the column type is floats of the same byte width caused the
column array to become garbled. (#218)
- Fixed inconsistent behavior in creating CONTINUE cards from byte strings
versus unicode strings in Python 2--CONTINUE cards can now be created
properly from unicode strings (so long as they are convertable to ASCII).
(spacetelescope/PyFITS#1)
- Fixed a couple cases where creating a new table using TDIMn in some of the
columns could caused a crash. (spacetelescope/PyFITS#3)
- Fixed a bug in parsing HIERARCH keywords that do not have a space after
the first equals sign (before the value). (spacetelescope/PyFITS#5)
- Prevented extra leading whitespace on HIERARCH keywords from being treated
as part of the keyword. (spacetelescope/PyFITS#6)
- Fixed a bug where HIERARCH keywords containing lower-case letters was
mistakenly marked as invalid during header validation.
(spacetelescope/PyFITS#7)
- Fixed an issue that was ancillary to (spacetelescope/PyFITS#7) where the
``Header.index()`` method did not work correctly with HIERARCH keywords
containing lower-case letters.
3.0.11 (2013-04-17)
-------------------
- Fixed support for opening gzipped FITS files by filename in a writeable mode
(PyFITS has supported writing to gzip files for some time now, but only
enabled it when GzipFile objects were passed to ``pyfits.open()`` due to
some legacy code preventing full gzip support. Backported from 3.1.2. (#195)
- Added a more helpful error message in the case of malformatted FITS files
that contain non-float NULL values in an ASCII table but are missing the
required TNULLn keywords in the header. Backported from 3.1.2. (#197)
- Fixed an (apparently long-standing) issue where writing compressed images did
not correctly write the TFORMn keywords for variable-length array columns
(they ommitted the max array length parameter of the format). Backported from
3.1.2. (#199)
- Slightly refactored how tables containing variable-length array columns are
handled to add two improvements: Fixes an issue where accessing the data
after a call to the `pyfits.getdata` convenience function caused an
exception, and allows the VLA data to be read from an existing mmap of the
FITS file. Backported from 3.1.2. (#200)
- Fixed a bug that could occur when opening a table containing
multi-dimensional columns (i.e. via the TDIMn keyword) and then writing it
out to a new file. Backported from 3.1.2. (#201)
- Fixed a bug on Python 3 where attempting to open a non-existent file on
Python 3 caused a seemingly unrelated traceback. Backported from 3.1.2.
(#203)
- Fixed a bug in fitsdiff that reported two header keywords containing NaN
as value as different. Backported from 3.1.2. (#204)
- Fixed an issue in the tests that caused some tests to fail if pyfits is
installed with read-only permissions. Backported from 3.1.2. (#208)
- Fixed a bug where instantiating a ``BinTableHDU`` from a numpy array
containing boolean fields converted all the values to ``False``. Backported
from 3.1.2. (#215)
- Fixed an issue where passing an array of integers into the constructor of
``Column()`` when the column type is floats of the same byte width caused the
column array to become garbled. Backported from 3.1.2. (#218)
- Fixed a couple cases where creating a new table using TDIMn in some of the
columns could caused a crash. Backported from 3.1.2.
(spacetelescope/PyFITS#3)
3.1.1 (2013-01-02)
------------------
This is a bug fix release for the 3.1.x series.
Bug Fixes
^^^^^^^^^
- Improved handling of scaled images and pseudo-unsigned integer images in
compressed image HDUs. They now work more transparently like normal image
HDUs with support for the ``do_not_scale_image_data`` and ``uint`` options,
as well as ``scale_back`` and ``save_backup``. The ``.scale()`` method
works better too. (#88)
- Permits non-string values for the EXTNAME keyword when reading in a file,
rather than throwing an exception due to the malformatting. Added
verification for the format of the EXTNAME keyword when writing. (#96)
- Added support for EXTNAME and EXTVER in PRIMARY HDUs. That is, if EXTNAME
is specified in the header, it will also be reflected in the ``.name``
attribute and in ``pyfits.info()``. These keywords used to be verboten in
PRIMARY HDUs, but the latest version of the FITS standard allows them.
(#151)
- HCOMPRESS can again be used to compress data cubes (and higher-dimensional
arrays) so long as the tile size is effectively 2-dimensional. In fact,
PyFITS will automatically use compatible tile sizes even if they're not
explicitly specified. (#171)
- Added support for the optional ``endcard`` parameter in the
``Header.fromtextfile()`` and ``Header.totextfile()`` methods. Although
``endcard=False`` was a reasonable default assumption, there are still text
dumps of FITS headers that include the END card, so this should have been
more flexible. (#176)
- Fixed a crash when running fitsdiff on two empty (that is, zero row) tables.
(#178)
- Fixed an issue where opening files containing random groups HDUs in update
mode could cause an unnecessary rewrite of the file even if none of the
data is modified. (#179)
- Fixed a bug that could caused a deadlock in the filesystem on OSX if PyFITS
is used with Numpy 1.7 in some cases. (#180)
- Fixed a crash when generating diff reports from diffs using the
``ignore_comments`` options. (#181)
- Fixed some bugs with WCS Paper IV record-valued keyword cards:
- Cards that looked kind of like RVKCs but were not intended to be were
over-permissively treated as such--commentary keywords like COMMENT and
HISTORY were particularly affected. (#183)
- Looking up a card in a header by its standard FITS keyword only should
always return the raw value of that card. That way cards containing
values that happen to valid RVKCs but were not intended to be will still
be treated like normal cards. (#184)
- Looking up a RVKC in a header with only part of the field-specifier (for
example "DP1.AXIS" instead of "DP1.AXIS.1") was implicitly treated as a
wildcard lookup. (#184)
- Fixed a crash when diffing two FITS files where at least one contains a
compressed image HDU which was not recognized as an image instead of a
table. (#187)
- Fixed bugs in the backwards compatibility layer for the ``CardList.index``
and ``CardList.count`` methods. (#190)
- Improved ``__repr__`` and text file representation of cards with long values
that are split into CONTINUE cards. (#193)
- Fixed a crash when trying to assign a long (> 72 character) value to blank
('') keywords. This also changed how blank keywords are represented--there
are still exactly 8 spaces before any commentary content can begin; this
*may* affect the exact display of header cards that assumed there could be
fewer spaces in a blank keyword card before the content begins. However, the
current approach is more in line with the requirements of the FITS standard.
(#194)
3.0.10 (2013-01-02)
-------------------
- Improved handling of scaled images and pseudo-unsigned integer images in
compressed image HDUs. They now work more transparently like normal image
HDUs with support for the ``do_not_scale_image_data`` and ``uint`` options,
as well as ``scale_back`` and ``save_backup``. The ``.scale()`` method
works better too. Backported from 3.1.1. (#88)
- Permits non-string values for the EXTNAME keyword when reading in a file,
rather than throwing an exception due to the malformatting. Added
verification for the format of the EXTNAME keyword when writing. Backported
from 3.1.1. (#96)
- Added support for EXTNAME and EXTVER in PRIMARY HDUs. That is, if EXTNAME
is specified in the header, it will also be reflected in the ``.name``
attribute and in ``pyfits.info()``. These keywords used to be verbotten in
PRIMARY HDUs, but the latest version of the FITS standard allows them.
Backported from 3.1.1. (#151)
- HCOMPRESS can again be used to compress data cubes (and higher-dimensional
arrays) so long as the tile size is effectively 2-dimensional. In fact,
PyFITS will not automatically use compatible tile sizes even if they're not
explicitly specified. Backported from 3.1.1. (#171)
- Fixed a bug when writing out files containing zero-width table columns,
where the TFIELDS keyword would be updated incorrectly, leaving the table
largely unreadable. Backported from 3.1.0. (#174)
- Fixed an issue where opening files containing random groups HDUs in update
mode could cause an unnecessary rewrite of the file even if none of the
data is modified. Backported from 3.1.1. (#179)
- Fixed a bug that could caused a deadlock in the filesystem on OSX if PyFITS
is used with Numpy 1.7 in some cases. Backported from 3.1.1. (#180)
3.1 (2012-08-08)
----------------
Highlights
^^^^^^^^^^
- The ``Header`` object has been significantly reworked, and ``CardList``
objects are now deprecated (their functionality folded into the ``Header``
class). See API Changes below for more details.
- Memory maps are now used by default to access HDU data. See API Changes
below for more details.
- Now includes a new version of the ``fitsdiff`` program for comparing two
FITS files, and a new FITS comparison API used by ``fitsdiff``. See New
Features below.
API Changes
^^^^^^^^^^^
- The ``Header`` class has been rewritten, and the ``CardList`` class is
deprecated. Most of the basic details of working with FITS headers are
unchanged, and will not be noticed by most users. But there are differences
in some areas that will be of interest to advanced users, and to application
developers. For full details of the changes, see the "Header Interface
Transition Guide" section in the PyFITS documentation. See ticket #64 on
the PyFITS Trac for futher details and background. Some highlights are
listed below:
* The Header class now fully implements the Python dict interface, and can
be used interchangably with a dict, where the keys are header keywords.
* New keywords can be added to the header using normal keyword assignment
(previously it was necessary to use ``Header.update`` to add new
keywords). For example::
>>> header['NAXIS'] = 2
will update the existing 'FOO' keyword if it already exists, or add a new
one if it doesn't exist, just like a dict.
* It is possible to assign both a value and a comment at the same time using
a tuple::
>>> header['NAXIS'] = (2, 'Number of axes')
* To add/update a new card and ensure it's added in a specific location, use
``Header.set()``::
>>> header.set('NAXIS', 2, 'Number of axes', after='BITPIX')
This works the same as the old ``Header.update()``. ``Header.update()``
still works in the old way too, but is deprecated.
* Although ``Card`` objects still exist, it generally is not necessary to
work with them directly. ``Header.ascardlist()``/``Header.ascard`` are
deprecated and should not be used. To directly access the ``Card``
objects in a header, use ``Header.cards``.
* To access card comments, it is still possible to either go through the
card itself, or through ``Header.comments``. For example::
>>> header.cards['NAXIS'].comment
Number of axes
>>> header.comments['NAXIS']
Number of axes
* ``Card`` objects can now be used interchangeably with
``(keyword, value, comment)`` 3-tuples. They still have ``.value`` and
``.comment`` attributes as well. The ``.key`` attribute has been renamed
to ``.keyword`` for consistency, though ``.key`` is still supported (but
deprecated).
- Memory mapping is now used by default to access HDU data. That is,
``pyfits.open()`` uses ``memmap=True`` as the default. This provides better
performance in the majority of use cases--there are only some I/O intensive
applications where it might not be desirable. Enabling mmap by default also
enabled finding and fixing a large number of bugs in PyFITS' handling of
memory-mapped data (most of these bug fixes were backported to PyFITS
3.0.5). (#85)
* A new ``pyfits.USE_MEMMAP`` global variable was added. Set
``pyfits.USE_MEMMAP = False`` to change the default memmap setting for
opening files. This is especially useful for controlling the behavior in
applications where pyfits is deeply embedded.
* Likewise, a new ``PYFITS_USE_MEMMAP`` environment variable is supported.
Set ``PYFITS_USE_MEMMAP = 0`` in your environment to change the default
behavior.
- The ``size()`` method on HDU objects is now a ``.size`` property--this
returns the size in bytes of the data portion of the HDU, and in most cases
is equivalent to ``hdu.data.nbytes`` (#83)
- ``BinTableHDU.tdump`` and ``BinTableHDU.tcreate`` are deprecated--use
``BinTableHDU.dump`` and ``BinTableHDU.load`` instead. The new methods
output the table data in a slightly different format from previous versions,
which places quotes around each value. This format is compatible with data
dumps from previous versions of PyFITS, but not vice-versa due to a parsing
bug in older versions.
- Likewise the ``pyfits.tdump`` and ``pyfits.tcreate`` convenience function
versions of these methods have been renamed ``pyfits.tabledump`` and
``pyfits.tableload``. The old deprecated, but currently retained for
backwards compatibility. (r1125)
- A new global variable ``pyfits.EXTENSION_NAME_CASE_SENSITIVE`` was added.
This serves as a replacement for ``pyfits.setExtensionNameCaseSensitive``
which is not deprecated and may be removed in a future version. To enable
case-sensitivity of extension names (i.e. treat 'sci' as distict from 'SCI')
set ``pyfits.EXTENSION_NAME_CASE_SENSITIVE = True``. The default is
``False``. (r1139)
- A new global configuration variable ``pyfits.STRIP_HEADER_WHITESPACE`` was
added. By default, if a string value in a header contains trailing
whitespace, that whitespace is automatically removed when the value is read.
Now if you set ``pyfits.STRIP_HEADER_WHITESPACE = False`` all whitespace is
preserved. (#146)
- The old ``classExtensions`` extension mechanism (which was deprecated in
PyFITS 3.0) is removed outright. To our knowledge it was no longer used
anywhere. (r1309)
- Warning messages from PyFITS issued through the Python warnings API are now
output to stderr instead of stdout, as is the default. PyFITS no longer
modifies the default behavior of the warnings module with respect to which
stream it outputs to. (r1319)
- The ``checksum`` argument to ``pyfits.open()`` now accepts a value of
'remove', which causes any existing CHECKSUM/DATASUM keywords to be ignored,
and removed when the file is saved.
New Features
^^^^^^^^^^^^
- Added support for the proposed "FITS" extension HDU type. See
http://listmgr.cv.nrao.edu/pipermail/fitsbits/2002-April/001094.html. FITS
HDUs contain an entire FITS file embedded in their data section. `FitsHDU`
objects work like other HDU types in PyFITS. Their ``.data`` attribute
returns the raw data array. However, they have a special ``.hdulist``
attribute which processes the data as a FITS file and returns it as an
in-memory HDUList object. FitsHDU objects also support a
``FitsHDU.fromhdulist()`` classmethod which returns a new `FitsHDU` object
that embeds the supplied HDUList. (#80)
- Added a new ``.is_image`` attribute on HDU objects, which is True if the HDU
data is an 'image' as opposed to a table or something else. Here the
meaning of 'image' is fairly loose, and mostly just means a Primary or Image
extension HDU, or possibly a compressed image HDU (#71)
- Added an ``HDUList.fromstring`` classmethod which can parse a FITS file
already in memory and instantiate and ``HDUList`` object from it. This
could be useful for integrating PyFITS with other libraries that work on
FITS file, such as CFITSIO. It may also be useful in streaming
applications. The name is a slight misnomer, in that it actually accepts
any Python object that implements the buffer interface, which includes
``bytes``, ``bytearray``, ``memoryview``, ``numpy.ndarray``, etc. (#90)
- Added a new ``pyfits.diff`` module which contains facilities for comparing
FITS files. One can use the ``pyfits.diff.FITSDiff`` class to compare two
FITS files in their entirety. There is also a ``pyfits.diff.HeaderDiff``
class for just comparing two FITS headers, and other similar interfaces.
See the PyFITS Documentation for more details on this interface. The
``pyfits.diff`` module powers the new ``fitsdiff`` program installed with
PyFITS. After installing PyFITS, run ``fitsdiff --help`` for usage details.
- ``pyfits.open()`` now accepts a ``scale_back`` argument. If set to
``True``, this automatically scales the data using the original BZERO and
BSCALE parameters the file had when it was first opened, if any, as well as
the original BITPIX. For example, if the original BITPIX were 16, this
would be equivalent to calling ``hdu.scale('int16', 'old')`` just before
calling ``flush()`` or ``close()`` on the file. This option applies to all
HDUs in the file. (#120)
- ``pyfits.open()`` now accepts a ``save_backup`` argument. If set to
``True``, this automatically saves a backup of the original file before
flushing any changes to it (this of course only applies to update and append
mode). This may be especially useful when working with scaled image data.
(#121)
Changes in Behavior
^^^^^^^^^^^^^^^^^^^
- Warnings from PyFITS are not output to stderr by default, instead of stdout
as it has been for some time. This is contrary to most users' expectations
and makes it more difficult for them to separate output from PyFITS from the
desired output for their scripts. (r1319)
Bug Fixes
^^^^^^^^^
- Fixed ``pyfits.tcreate()`` (now ``pyfits.tableload()``) to be more robust
when encountering blank lines in a column definition file (#14)
- Fixed a fairly rare crash that could occur in the handling of CONTINUE cards
when using Numpy 1.4 or lower (though 1.4 is the oldest version supported by
PyFITS). (r1330)
- Fixed ``_BaseHDU.fromstring`` to actually correctly instantiate an HDU
object from a string/buffer containing the header and data of that HDU.
This allowed for the implementation of ``HDUList.fromstring`` described
above. (#90)
- Fixed a rare corner case where, in some use cases, (mildly, recoverably)
malformatted float values in headers were not properly returned as floats.
(#137)
- Fixed a corollary to the previous bug where float values with a leading zero
before the decimal point had the leading zero unnecessarily removed when
saving changes to the file (eg. "0.001" would be written back as ".001" even
if no changes were otherwise made to the file). (#137)
- When opening a file containing CHECKSUM and/or DATASUM keywords in update
mode, the CHECKSUM/DATASUM are updated and preserved even if the file was
opened with checksum=False. This change in behavior prevents checksums from
being unintentionally removed. (#148)
- Fixed a bug where ``ImageHDU.scale(option='old')`` wasn't working at all--it
was not restoring the image to its original BSCALE and BZERO values. (#162)
- Fixed a bug when writing out files containing zero-width table columns,
where the TFIELDS keyword would be updated incorrectly, leaving the table
largely unreadable. This fix will be backported to the 3.0.x series in
version 3.0.10. (#174)
3.0.9 (2012-08-06)
------------------
This is a bug fix release for the 3.0.x series.
Bug Fixes
^^^^^^^^^
- Fixed ``Header.values()``/``Header.itervalues()`` and ``Header.items()``/
``Header.iteritems()`` to correctly return the different values for
duplicate keywords (particularly commentary keywords like HISTORY and
COMMENT). This makes the old Header implementation slightly more compatible
with the new implementation in PyFITS 3.1. (#127)
.. note::
This fix did not change the existing behavior from earlier PyFITS
versions where ``Header.keys()`` returns all keywords in the header with
duplicates removed. PyFITS 3.1 changes that behavior, so that
``Header.keys()`` includes duplicates.
- Fixed a bug where ``ImageHDU.scale(option='old')`` wasn't working at all--it
was not restoring the image to its original BSCALE and BZERO values. (#162)
- Fixed a bug where opening a file containing compressed image HDUs in
'update' mode and then immediately closing it without making any changes
caused the file to be rewritten unncessarily. (#167)
- Fixed two memory leaks that could occur when writing compressed image data,
or in some cases when opening files containing compressed image HDUs in
'update' mode. (#168)
3.0.8 (2012-06-04)
------------------
Changes in Behavior
^^^^^^^^^^^^^^^^^^^
- Prior to this release, image data sections did not work with scaled
data--that is, images with non-trivial BSCALE and/or BZERO values.
Previously, in order to read such images in sections, it was necessary to
manually apply the BSCALE+BZERO to each section. It's worth noting that
sections *did* support pseudo-unsigned ints (flakily). This change just
extends that support for general BSCALE+BZERO values.
Bug Fixes
^^^^^^^^^
- Fixed a bug that prevented updates to values in boolean table columns from
being saved. This turned out to be a symptom of a deeper problem that could
prevent other table updates from being saved as well. (#139)
- Fixed a corner case in which a keyword comment ending with the string "END"
could, in some circumstances, cause headers (and the rest of the file after
that point) to be misread. (#142)
- Fixed support for scaled image data and psuedo-unsigned ints in image data
sections (``hdu.section``). Previously this was not supported at all. At
some point support was supposedly added, but it was buggy and incomplete.
Now the feature seems to work much better. (#143)
- Fixed the documentation to point out that image data sections *do* support
non-contiguous slices (and have for a long time). The documentation was
never updated to reflect this, and misinformed users that only contiguous
slices were supported, leading to some confusion. (#144)
- Fixed a bug where creating an ``HDUList`` object containing multiple PRIMARY
HDUs caused an infinite recursion when validating the object prior to
writing to a file. (#145)
- Fixed a rare but serious case where saving an update to a file that
previously had a CHECKSUM and/or DATASUM keyword, but removed the checksum
in saving, could cause the file to be slightly corrupted and unreadable.
(#147)
- Fixed problems with reading "non-standard" FITS files with primary headers
containing SIMPLE = F. PyFITS has never made many guarantees as to how such
files are handled. But it should at least be possible to read their
headers, and the data if possible. Saving changes to such a file should not
try to prepend an unwanted valid PRIMARY HDU. (#157)
- Fixed a bug where opening an image with ``disable_image_compression = True``
caused compression to be disabled for all subsequent ``pyfits.open()`` calls.
(r1651)
3.0.7 (2012-04-10)
------------------
Changes in Behavior
^^^^^^^^^^^^^^^^^^^
- Slices of GroupData objects now return new GroupData objects instead of
extended multi-row _Group objects. This is analogous to how PyFITS 3.0 fixed
FITS_rec slicing, and should have been fixed for GroupData at the same time.
The old behavior caused bugs where functions internal to Numpy expected that
slicing an ndarray would return a new ndarray. As this is a rare usecase
with a rare feature most users are unlikely to be affected by this change.
- The previously internal _Group object for representing individual group
records in a GroupData object are renamed Group and are now a public
interface. However, there's almost no good reason to create Group objects
directly, so it shouldn't be considered a "new feature".
- An annoyance from PyFITS 3.0.6 was fixed, where the value of the EXTEND
keyword was always being set to F if there are not actually any extension
HDUs. It was unnecessary to modify this value.
Bug Fixes
^^^^^^^^^
- Fixed GroupData objects to return new GroupData objects when sliced instead
of _Group record objects. See "Changes in behavior" above for more details.
- Fixed slicing of Group objects--previously it was not possible to slice
slice them at all.
- Made it possible to assign `np.bool_` objects as header values. (#123)
- Fixed overly strict handling of the EXTEND keyword; see "Changes in
behavior" above. (#124)
- Fixed many cases where an HDU's header would be marked as "modified" by
PyFITS and rewritten, even when no changes to the header are necessary.
(#125)
- Fixed a bug where the values of the PTYPEn keywords in a random groups HDU
were forced to be all lower-case when saving the file. (#130)
- Removed an unnecessary inline import in `ExtensionHDU.__setattr__` that was
causing some slowdown when opening files containing a large number of
extensions, plus a few other small (but not insignficant) performance
improvements thanks to Julian Taylor. (#133)
- Fixed a regression where header blocks containing invalid end-of-header
padding (i.e. null bytes instead of spaces) couldn't be parsed by PyFITS.
Such headers can be parsed again, but a warning is raised, as such headers
are not valid FITS. (#136)
- Fixed a memory leak where table data in random groups HDUs weren't being
garbage collected. (#138)
3.0.6 (2012-02-29)
------------------
Highlights
^^^^^^^^^^
The main reason for this release is to fix an issue that was introduced in
PyFITS 3.0.5 where merely opening a file containing scaled data (that is, with
non-trivial BSCALE and BZERO keywords) in 'update' mode would cause the data
to be automatically rescaled--possibly converting the data from ints to
floats--as soon as the file is closed, even if the application did not touch
the data. Now PyFITS will only rescale the data in an extension when the data
is actually accessed by the application. So opening a file in 'update' mode
in order to modify the header or append new extensions will not cause any
change to the data in existing extensions.
This release also fixes a few Windows-specific bugs found through more
extensive Windows testing, and other miscellaneous bugs.
Bug Fixes
^^^^^^^^^
- More accurate error messages when opening files containing invalid header
cards. (#109)
- Fixed a possible reference cycle/memory leak that was caught through more
extensive testing on Windows. (#112)
- Fixed 'ostream' mode to open the underlying file in 'wb' mode instead of 'w'
mode. (#112)
- Fixed a Windows-only issue where trying to save updates to a resized FITS
file could result in a crash due to there being open mmaps on that file.
(#112)
- Fixed a crash when trying to create a FITS table (i.e. with new_table())
from a Numpy array containing bool fields. (#113)
- Fixed a bug where manually initializing an ``HDUList`` with a list of of
HDUs wouldn't set the correct EXTEND keyword value on the primary HDU.
(#114)
- Fixed a crash that could occur when trying to deepcopy a Header in Python <
2.7. (#115)
- Fixed an issue where merely opening a scaled image in 'update' mode would
cause the data to be converted to floats when the file is closed. (#119)
3.0.5 (2012-01-30)
------------------
- Fixed a crash that could occur when accessing image sections of files
opened with memmap=True. (r1211)
- Fixed the inconsistency in the behavior of files opened in 'readonly' mode
when memmap=True vs. when memmap=False. In the latter case, although
changes to array data were not saved to disk, it was possible to update the
array data in memory. On the other hand with memmap=True, 'readonly' mode
prevented even in-memory modification to the data. This is what
'copyonwrite' mode was for, but difference in behavior was confusing. Now
'readonly' is equivalent to 'copyonwrite' when using memmap. If the old
behavior of denying changes to the array data is necessary, a new
'denywrite' mode may be used, though it is only applicable to files opened
with memmap. (r1275)
- Fixed an issue where files opened with memmap=True would return image data
as a raw numpy.memmap object, which can cause some unexpected
behaviors--instead memmap object is viewed as a numpy.ndarray. (r1285)
- Fixed an issue in Python 3 where a workaround for a bug in Numpy on Python 3
interacted badly with some other software, namely to vo.table package (and
possibly others). (r1320, r1337, and #110)
- Fixed buggy behavior in the handling of SIGINTs (i.e. Ctrl-C keyboard
interrupts) while flushing changes to a FITS file. PyFITS already prevented
SIGINTs from causing an incomplete flush, but did not clean up the signal
handlers properly afterwards, or reraise the keyboard interrupt once the
flush was complete. (r1321)
- Fixed a crash that could occur in Python 3 when opening files with checksum
checking enabled. (r1336)
- Fixed a small bug that could cause a crash in the `StreamingHDU` interface
when using Numpy below version 1.5.
- Fixed a crash that could occur when creating a new `CompImageHDU` from an
array of big-endian data. (#104)
- Fixed a crash when opening a file with extra zero padding at the end.
Though FITS files should not have such padding, it's not explictly forbidden
by the format either, and PyFITS shouldn't stumble over it. (#106)
- Fixed a major slowdown in opening tables containing large columns of string
values. (#111)
3.0.4 (2011-11-22)
------------------
- Fixed a crash when writing HCOMPRESS compressed images that could happen on
Python 2.5 and 2.6. (r1217)
- Fixed a crash when slicing an table in a file opened in 'readonly' mode with
memmap=True. (r1230)
- Writing changes to a file or writing to a new file verifies the output in
'fix' mode by default instead of 'exception'--that is, PyFITS will
automatically fix common FITS format errors rather than raising an
exception. (r1243)
- Fixed a bug where convenience functions such as getval() and getheader()
crashed when specifying just 'PRIMARY' as the extension to use (r1263).
- Fixed a bug that prevented passing keyword arguments (beyond the standard
data and header arguments) as positional arguments to the constructors of
extension HDU classes.
- Fixed some tests that were failing on Windows--in this case the tests
themselves failed to close some temp files and Windows refused to delete them
while there were still open handles on them. (r1295)
- Fixed an issue with floating point formatting in header values on Python 2.5
for Windows (and possibly other platforms). The exponent was zero-padded to
3 digits; although the FITS standard makes no specification on this, the
formatting is now normalized to always pad the exponent to two digits.
(r1295)
- Fixed a bug where long commentary cards (such as HISTORY and COMMENT) were
broken into multiple CONTINUE cards. However, commentary cards are not
expected to be found in CONTINUE cards. Instead these long cards are broken
into multiple commentary cards. (#97)
- GZIP/ZIP-compressed FITS files can be detected and opened regardless of
their filename extension. (#99)
- Fixed a serious bug where opening scaled images in 'update' mode and then
closing the file without touching the data would cause the file to be
corrupted. (#101)
3.0.3 (2011-10-05)
------------------
- Fixed several small bugs involving corner cases in record-valued keyword
cards (#70)
- In some cases HDU creation failed if the first keyword value in the header
was not a string value (#89)
- Fixed a crash when trying to compute the HDU checksum when the data array
contains an odd number of bytes (#91)
- Disabled an unnecessary warning that was displayed on opening compressed
HDUs with disable_image_compression = True (#92)
- Fixed a typo in code for handling HCOMPRESS compressed images.
3.0.2 (2011-09-23)
------------------
- The ``BinTableHDU.tcreate`` method and by extension the ``pyfits.tcreate``
function don't get tripped up by blank lines anymore (#14)
- The presence, value, and position of the EXTEND keyword in Primary HDUs is
verified when reading/writing a FITS file (#32)
- Improved documentation (in warning messages as well as in the handbook) that
PyFITS uses zero-based indexing (as one would expect for C/Python code, but
contrary to the PyFITS standard which was written with FORTRAN in mind)
(#68)
- Fixed a bug where updating a header card comment could cause the value to be
lost if it had not already been read from the card image string.
- Fixed a related bug where changes made directly to Card object in a header
(i.e. assigning directly to card.value or card.comment) would not propagate
when flushing changes to the file (#69) [Note: This and the bug above it
were originally reported as being fixed in version 3.0.1, but the fix was
never included in the release.]
- Improved file handling, particularly in Python 3 which had a few small file
I/O-related bugs (#76)
- Fixed a bug where updating a FITS file would sometimes cause it to lose its
original file permissions (#79)
- Fixed the handling of TDIMn keywords; 3.0 added support for them, but got
the axis order backards (they were treated as though they were row-major)
(#82)
- Fixed a crash when a FITS file containing scaled data is opened and
immediately written to a new file without explicitly viewing the data first
(#84)
- Fixed a bug where creating a table with columns named either 'names' or
'formats' resulted in an infinite recursion (#86)
3.0.1 (2011-09-12)
------------------
- Fixed a bug where updating a header card comment could cause the value to be
lost if it had not already been read from the card image string.
- Changed ``_TableBaseHDU.data`` so that if the data contain an empty table a
``FITS_rec`` object with zero rows is returned rather than ``None``.
- The ``.key`` attribute of ``RecordValuedKeywordCards`` now returns the full
keyword+field-specifier value, instead of just the plain keyword (#46)
- Fixed a related bug where changes made directly to Card object in a header
(i.e. assigning directly to card.value or card.comment) would not propagate
when flushing changes to the file (#69)
- Fixed a bug where writing a table with zero rows could fail in some cases
(#72)
- Miscellanous small bug fixes that were causing some tests to fail,
particularly on Python 3 (#74, #75)
- Fixed a bug where creating a table column from an array in non-native byte
order would not preserve the byte order, thus interpreting the column array
using the wrong byte order (#77)
3.0.0 (2011-08-23)
--------------------
- Contains major changes, bumping the version to 3.0
- Large amounts of refactoring and reorganization of the code; tried to
preserve public API backwards-compatibility with older versions (private API
has many changes and is not guaranteed to be backwards-compatible). There
are a few small public API changes to be aware of:
* The pyfits.rec module has been removed completely. If your version of
numpy does not have the numpy.core.records module it is too old to be used
with PyFITS.
* The ``Header.ascardlist()`` method is deprecated--use the ``.ascard``
attribute instead.
* ``Card`` instances have a new ``.cardimage`` attribute that should be used
rather than ``.ascardimage()``, which may become deprecated.
* The ``Card.fromstring()`` method is now a classmethod. It returns a new
``Card`` instance rather than modifying an existing instance.
* The ``req_cards()`` method on HDU instances has changed: The ``pos``
argument is not longer a string. It is either an integer value (meaning
the card's position must match that value) or it can be a function that
takes the card's position as it's argument, and returns True if the
position is valid. Likewise, the ``test`` argument no longer takes a
string, but instead a function that validates the card's value and returns
True or False.
* The ``get_coldefs()`` method of table HDUs is deprecated. Use the
``.columns`` attribute instead.
* The ``ColDefs.data`` attribute is deprecated--use ``ColDefs.columns``
instead (though in general you shouldn't mess with it directly--it might
become internal at some point).
* ``FITS_record`` objects take ``start`` and ``end`` as arguments instead of
``startColumn`` and ``endColumn`` (these are rarely created manually, so
it's unlikely that this change will affect anyone).
* ``BinTableHDU.tcreate()`` is now a classmethod, and returns a new
``BinTableHDU`` instance.
* Use ``ExtensionHDU`` and ``NonstandardExtHDU`` for making new extension HDU
classes. They are now public interfaces, wheres previously they were
private and prefixed with underscores.
* Possibly others--please report if you find any changes that cause
difficulties.
- Calls to deprecated functions will display a Deprecation warning. However,
in Python 2.7 and up Deprecation warnings are ignored by default, so run
Python with the `-Wd` option to see if you're using any deprecated
functions. If we get close to actually removing any functions, we might
make the Deprecation warnings display by default.
- Added basic Python 3 support
- Added support for multi-dimensional columns in tables as specified by the
TDIMn keywords (#47)
- Fixed a major memory leak that occurred when creating new tables with the
``new_table()`` function (#49)
be padded with zero-bytes) vs ASCII tables (where strings are padded with
spaces) (#15)
- Fixed a bug in which the case of Random Access Group parameters names was not
preserved when writing (#41)
- Added support for binary table fields with zero width (#42)
- Added support for wider integer types in ASCII tables; although this is non-
standard, some GEIS images require it (#45)
- Fixed a bug that caused the index_of() method of HDULists to crash when the
HDUList object is created from scratch (#48)
- Fixed the behavior of string padding in binary tables (where strings should
be padded with nulls instead of spaces)
- Fixed a rare issue that caused excessive memory usage when computing
checksums using a non-standard block size (see r818)
- Add support for forced uint data in image sections (#53)
- Fixed an issue where variable-length array columns were not extended when
creating a new table with more rows than the original (#54)
- Fixed tuple and list-based indexing of FITS_rec objects (#55)
- Fixed an issue where BZERO and BSCALE keywords were appended to headers in
the wrong location (#56)
- ``FITS_record`` objects (table rows) have full slicing support, including
stepping, etc. (#59)
- Fixed a bug where updating multiple files simultaneously (such as when
running parallel processes) could lead to a race condition with mktemp()
(#61)
- Fixed a bug where compressed image headers were not in the order expected by
the funpack utility (#62)
jperkin
pushed a commit
that referenced
this issue
Mar 14, 2014
Changes since 1.1.0 (from git log):
issue #70: boolean flags may have true default
Merge pull request #69 from Tieske/master
general updates, mainly added CONTRIBUTING.md
Merge pull request #1 from mark-otaris/patch-1
Caught red handed, after a shameless copy 😄. Thx for the fix
This is Penlight, not Busted
added - a shameless copy of busted - CONTRIBUTING.md file
renamed docs to doc, to fix luarocks warning
updated readme to md format
changed .txt to .md files
added rockspec, fixed typo in filename
Merge pull request #67 from Tieske/add_executeex
added utils.executeex, which also returns output of stdout and stderr
updated, using readfile now, remove obsolete os.remove commands
Merge pull request #66 from Tieske/fix_temp
windows environment variable TMP is deprecated, use TEMP
mode binary mode optional (binary would require platform specific line endings to be converted which is not very portable, and mostly just text will do)
update: read files in binary mode
added utils.executeex, which also returns output of stdout and stderr
windows environment variable TMP is deprecated, use TEMP
HTML mode skips DOCTYPE; no globals harmed outside pl.utils
Merge pull request #64 from Tieske/fix_dir
fixed makepath creation, added/updated some documentation
fixed dirpath creation, added/updated some documentation
basic parser handles comments, and HTML mode is working nicely with real-world HTML
use LOM ordered attributes when stringifying if present (Danny).
manual merge of John Schember's readonly table support
Merge pull request #61 from user-none/isempty
Thanks, John!
Merge pull request #62 from CoolisTheName007/patch-2
Transform using values as keys.
missing locals
Set.issempty mispelling; default ctor borked; more tests
Transform using values as keys.
Merge remote-tracking branch 'upstream/master' into empty
Add function to check if an object is empty.
Merge pull request #53 from pkazmier/master
Added iterators to allow traversing tables in a sorted manner
Merge pull request #60 from theypsilon/master
base class methods invocation possible not only in method constructor _init
Adding new class method 'base' which can be used for calling base class methods easily
pl.class broke with classes that redefined __newindex; OrderedMap can now use normal indexing to assign keys in order
Merge pull request #54 from CoolisTheName007/patch-1
Typo fixed, libarary->library
Typo fixed.
Added tablex.sort and tablex.sortv to iterate over sorted elements
There are times when it would be convenient to iterate over a table
either by sorted keys or values. There is an example of this in the
PIL book. I added the two functions to tablex module, added two test
cases, and updated the PL manual.
Merge pull request #51 from pkazmier/master
Thanks!
lapp.add_type was broken due to uninitialized table variable.
The variable `types` was not initialized preventing `add_type` from
appending custom types to the variable. I also added a new test to
cover this test case in the future.
jperkin
pushed a commit
that referenced
this issue
Mar 14, 2014
FITS (Flexible Image Transport System) is a data format most used in astronomy.
PyFITS is a Python module for reading, writing, and manipulating FITS files.
The module uses Python's object-oriented features to provide quick, easy, and
efficient access to FITS files. The use of Python's array syntax enables
immediate access to any FITS extension, header cards, or data items.
Changes to 2.4.0 (in py-pyfits):
Changelog
===========
3.2 (2013-11-26)
----------------
Highlights
^^^^^^^^^^
- Rewrote CFITSIO-based backend for handling tile compression of FITS files.
It now uses a standard CFITSIO instead of heavily modified pieces of CFITSIO
as before. PyFITS ships with its own copy of CFITSIO v3.35 which supports
the latest version of the Tiled Image Convention (v2.3), but system
packagers may choose instead to strip this out in favor of a
system-installed version of CFITSIO. Earlier versions may work, but nothing
earlier than 3.28 has been tested yet. (#169)
- Added support for reading and writing tables using the Q format for columns.
The Q format is identical to the P format (variable-length arrays) except
that it uses 64-bit integers for the data descriptors, allowing more than
4 GB of variable-length array data in a single table. (#160)
- Added initial support for table columns containing pseudo-unsigned integers.
This is currently enabled by using the ``uint=True`` option when opening
files; any table columns with the correct BZERO value will be interpreted
and returned as arrays of unsigned integers.
- Some refactoring of the table and ``FITS_rec`` modules in order to better
separate the details of the FITS binary and ASCII table data structures from
the HDU data structures that encapsulate them. Most of these changes should
not be apparent to users (but see API Changes below).
API Changes
^^^^^^^^^^^
- Assigning to values in ``ColDefs.names``, ``ColDefs.formats``,
``ColDefs.nulls`` and other attributes of ``ColDefs`` instances that return
lists of column properties is no longer supported. Assigning to those lists
will no longer update the corresponding columns. Instead, please just
modify the ``Column`` instances directly (``Column.name``, ``Column.null``,
etc.)
- The ``pyfits.new_table`` function is marked "pending deprecation". This
does not mean it will be removed outright or that its functionality has
changed. It will likely be replaced in the future for a function with
similar, if not subtly different functionality. A better, if not slightly
more verbose approach is to use ``pyfits.FITS_rec.from_columns`` to create
a new ``FITS_rec`` table--this has the same interface as
``pyfits.new_table``. The difference is that it returns a plan ``FITS_rec``
array, and not an HDU instance. This ``FITS_rec`` object can then be used
as the data argument in the constructors for ``BinTableHDU`` (for binary
tables) or ``TableHDU`` (for ASCII tables). This is analogous to creating
an ``ImageHDU`` by passing in an image array.
``pyfits.FITS_rec.from_columns`` is just a simpler way of creating a
FITS-compatible recarray from a FITS column specification.
- The ``updateHeader``, ``updateHeaderData``, and ``updateCompressedData``
methods of the ``CompDataHDU`` class are pending deprecation and moved to
internal methods. The operation of these methods depended too much on
internal state to be used safely by users; instead they are invoked
automatically in the appropriate places when reading/writing compressed image
HDUs.
- The ``CompDataHDU.compData`` attribute is pending deprecation in favor of
the clearer and more PEP-8 compatible ``CompDataHDU.compressed_data``.
- The constructor for ``CompDataHDU`` has been changed to accept new keyword
arguments. The new keyword arguments are essentially the same, but are in
underscore_separated format rather than camelCase format. The old arguments
are still pending deprecation.
- The internal attributes of HDU classes ``_hdrLoc``, ``_datLoc``, and
``_datSpan`` have been replaced with ``_header_offset``, ``_data_offset``,
and ``_data_size`` respectively. The old attribute names are still pending
deprecation. This should only be of interest to advanced users who have
created their own HDU subclasses.
- The following previously deprecated functions and methods have been removed
entirely: ``createCard``, ``createCardFromString``, ``upperKey``,
``ColDefs.data``, ``setExtensionNameCaseSensitive``, ``_File.getfile``,
``_TableBaseHDU.get_coldefs``, ``Header.has_key``, ``Header.ascardlist``.
If you run your code with a previous version of PyFITS (>= 3.0, < 3.2) with
the ``python -Wd`` argument, warnings for all deprecated interfaces still in
use will be displayed.
- Interfaces that were pending deprecation are now fully deprecated. These
include: ``create_card``, ``create_card_from_string``, ``upper_key``,
``Header.get_history``, and ``Header.get_comment``.
- The ``.name`` attribute on HDUs is now directly tied to the HDU's header, so
that if ``.header['EXTNAME']`` changes so does ``.name`` and vice-versa.
- The ``pyfits.file.PYTHON_MODES`` constant dict was renamed to
``pyfits.file.PYFITS_MODES`` which better reflects its purpose. This is
rarely used by client code, however. Support for the old name will be
removed by PyFITS 3.4.
Other Changes and Additions
^^^^^^^^^^^^^^^^^^^^^^^^^^^
- The new compression code also adds support for the ZQUANTIZ and ZDITHER0
keywords added in more recent versions of this FITS Tile Compression spec.
This includes support for lossless compression with GZIP. (#198) By default
no dithering is used, but the ``SUBTRACTIVE_DITHER_1`` and
``SUBTRACTIVE_DITHER_2`` methods can be enabled by passing the correct
constants to the ``quantize_method`` argument to the ``CompImageHDU``
constuctor. A seed can be manually specified, or automatically generated
using either the system clock or checksum-based methods via the
``dither_seed`` argument. See the documentation for ``CompImageHDU`` for
more details. (#198) (spacetelescope/PYFITS#32)
- Images compressed with the Tile Compression standard can now be larger than
4 GB through support of the Q format. (#159)
- All HDUs now have a ``.ver`` ``.level`` attribute that returns the value of
the EXTVAL and EXTLEVEL keywords from that HDU's header, if the exist. This
was added for consistency with the ``.name`` attribute which returns the
EXTNAME value from the header.
- Then ``Column`` and ``ColDefs`` classes have new ``.dtype`` attributes
which give the Numpy dtype for the column data in the first case, and the
full Numpy compound dtype for each table row in the latter case.
- There was an issue where new tables created defaulted the values in all
string columns to '0.0'. Now string columns are filled with empty strings
by default--this seems a less surprising default, but it may cause
differences with tables created with older versions of PyFITS.
- Improved round-tripping and preservation of manually assigned column
attributes (``TNULLn``, ``TSCALn``, etc.) in table HDU headers.
(astropy/astropy#996)
Bug Fixes
^^^^^^^^^
- Binary tables containing compressed images may, optionally, contain other
columns unrelated to the tile compression convention. Although this is an
uncommon use case, it is permitted by the standard. (#159)
- Reworked some of the file I/O routines to allow simpler, more consistent
mapping between OS-level file modes ('rb', 'wb', 'ab', etc.) and the more
"PyFITS-specific" modes used by PyFITS like "readonly" and "update".
That is, if reading a FITS file from an open file object, it doesn't matter
as much what "mode" it was opened in so long as it has the right
capabilities (read/write/etc.) Also works around bugs in the Python io
module in 2.6+ with regard to file modes. (spacetelescope/PyFITS#33)
- Fixed an obscure issue that can occur on systems that don't have flush to
memory-mapped files implemented (namely GNU Hurd). (astropy/astropy#968)
3.1.3 (2013-11-26)
------------------
- Disallowed assigning NaN and Inf floating point values as header values,
since the FITS standard does not define a way to represent them in. Because
this is undefined, the previous behavior did not make sense and produced
invalid FITS files. (spacetelescope/PyFITS#11)
- Added a workaround for a bug in 64-bit OSX that could cause truncation when
writing files greater than 2^32 bytes in size. (spacetelescope/PyFITS#28)
- Fixed a long-standing issue where writing binary tables did not correctly
write the TFORMn keywords for variable-length array columns (they ommitted
the max array length parameter of the format). This was thought fixed in
v3.1.2, but it was only fixed there for compressed image HDUs and not for
binary tables in general.
- Fixed an obscure issue that can occur on systems that don't have flush to
memory-mapped files implemented (namely GNU Hurd). (Backported from 3.2)
3.0.12 (2013-11-26)
-------------------
- Disallowed assigning NaN and Inf floating point values as header values,
since the FITS standard does not define a way to represent them in. Because
this is undefined, the previous behavior did not make sense and produced
invalid FITS files. (Backported from 3.1.3)
- Added a workaround for a bug in 64-bit OSX that could cause truncation when
writing files greater than 2^32 bytes in size. (Backported from 3.1.3)
- Fixed a long-standing issue where writing binary tables did not correctly
write the TFORMn keywords for variable-length array columns (they ommitted
the max array length parameter of the format). This was thought fixed in
v3.1.2, but it was only fixed there for compressed image HDUs and not for
binary tables in general. (Backported from 3.1.3)
- Fixed an obscure issue that can occur on systems that don't have flush to
memory-mapped files implemented (namely GNU Hurd). (Backported from 3.2)
3.1.2 (2013-04-22)
------------------
- When an error occurs opening a file in fitsdiff the exception message will
now at least mention which file had the error. (#168)
- Fixed support for opening gzipped FITS files by filename in a writeable mode
(PyFITS has supported writing to gzip files for some time now, but only
enabled it when GzipFile objects were passed to ``pyfits.open()`` due to
some legacy code preventing full gzip support. (#195)
- Added a more helpful error message in the case of malformatted FITS files
that contain non-float NULL values in an ASCII table but are missing the
required TNULLn keywords in the header. (#197)
- Fixed an (apparently long-standing) issue where writing compressed images
did not correctly write the TFORMn keywords for variable-length array
columns (they ommitted the max array length parameter of the format). (#199)
- Slightly refactored how tables containing variable-length array columns are
handled to add two improvements: Fixes an issue where accessing the data
after a call to the `pyfits.getdata` convenience function caused an
exception, and allows the VLA data to be read from an existing mmap of the
FITS file. (#200)
- Fixed a bug that could occur when opening a table containing
multi-dimensional columns (i.e. via the TDIMn keyword) and then writing it
out to a new file. (#201)
- Added use of the console_scripts entry point to install the fitsdiff and
fitscheck scripts, which if nothing else provides better Windows support.
The generated scripts now override the ones explicitly defined in the
scripts/ directory (which were just trivial stubs to begin with). (#202)
- Fixed a bug on Python 3 where attempting to open a non-existent file on
Python 3 caused a seemingly unrelated traceback. (#203)
- Fixed a bug in fitsdiff that reported two header keywords containing NaN
as value as different. (#204)
- Fixed an issue in the tests that caused some tests to fail if pyfits is
installed with read-only permissions. (#208)
- Fixed a bug where instantiating a ``BinTableHDU`` from a numpy array
containing boolean fields converted all the values to ``False``. (#215)
- Fixed an issue where passing an array of integers into the constructor of
``Column()`` when the column type is floats of the same byte width caused the
column array to become garbled. (#218)
- Fixed inconsistent behavior in creating CONTINUE cards from byte strings
versus unicode strings in Python 2--CONTINUE cards can now be created
properly from unicode strings (so long as they are convertable to ASCII).
(spacetelescope/PyFITS#1)
- Fixed a couple cases where creating a new table using TDIMn in some of the
columns could caused a crash. (spacetelescope/PyFITS#3)
- Fixed a bug in parsing HIERARCH keywords that do not have a space after
the first equals sign (before the value). (spacetelescope/PyFITS#5)
- Prevented extra leading whitespace on HIERARCH keywords from being treated
as part of the keyword. (spacetelescope/PyFITS#6)
- Fixed a bug where HIERARCH keywords containing lower-case letters was
mistakenly marked as invalid during header validation.
(spacetelescope/PyFITS#7)
- Fixed an issue that was ancillary to (spacetelescope/PyFITS#7) where the
``Header.index()`` method did not work correctly with HIERARCH keywords
containing lower-case letters.
3.0.11 (2013-04-17)
-------------------
- Fixed support for opening gzipped FITS files by filename in a writeable mode
(PyFITS has supported writing to gzip files for some time now, but only
enabled it when GzipFile objects were passed to ``pyfits.open()`` due to
some legacy code preventing full gzip support. Backported from 3.1.2. (#195)
- Added a more helpful error message in the case of malformatted FITS files
that contain non-float NULL values in an ASCII table but are missing the
required TNULLn keywords in the header. Backported from 3.1.2. (#197)
- Fixed an (apparently long-standing) issue where writing compressed images did
not correctly write the TFORMn keywords for variable-length array columns
(they ommitted the max array length parameter of the format). Backported from
3.1.2. (#199)
- Slightly refactored how tables containing variable-length array columns are
handled to add two improvements: Fixes an issue where accessing the data
after a call to the `pyfits.getdata` convenience function caused an
exception, and allows the VLA data to be read from an existing mmap of the
FITS file. Backported from 3.1.2. (#200)
- Fixed a bug that could occur when opening a table containing
multi-dimensional columns (i.e. via the TDIMn keyword) and then writing it
out to a new file. Backported from 3.1.2. (#201)
- Fixed a bug on Python 3 where attempting to open a non-existent file on
Python 3 caused a seemingly unrelated traceback. Backported from 3.1.2.
(#203)
- Fixed a bug in fitsdiff that reported two header keywords containing NaN
as value as different. Backported from 3.1.2. (#204)
- Fixed an issue in the tests that caused some tests to fail if pyfits is
installed with read-only permissions. Backported from 3.1.2. (#208)
- Fixed a bug where instantiating a ``BinTableHDU`` from a numpy array
containing boolean fields converted all the values to ``False``. Backported
from 3.1.2. (#215)
- Fixed an issue where passing an array of integers into the constructor of
``Column()`` when the column type is floats of the same byte width caused the
column array to become garbled. Backported from 3.1.2. (#218)
- Fixed a couple cases where creating a new table using TDIMn in some of the
columns could caused a crash. Backported from 3.1.2.
(spacetelescope/PyFITS#3)
3.1.1 (2013-01-02)
------------------
This is a bug fix release for the 3.1.x series.
Bug Fixes
^^^^^^^^^
- Improved handling of scaled images and pseudo-unsigned integer images in
compressed image HDUs. They now work more transparently like normal image
HDUs with support for the ``do_not_scale_image_data`` and ``uint`` options,
as well as ``scale_back`` and ``save_backup``. The ``.scale()`` method
works better too. (#88)
- Permits non-string values for the EXTNAME keyword when reading in a file,
rather than throwing an exception due to the malformatting. Added
verification for the format of the EXTNAME keyword when writing. (#96)
- Added support for EXTNAME and EXTVER in PRIMARY HDUs. That is, if EXTNAME
is specified in the header, it will also be reflected in the ``.name``
attribute and in ``pyfits.info()``. These keywords used to be verboten in
PRIMARY HDUs, but the latest version of the FITS standard allows them.
(#151)
- HCOMPRESS can again be used to compress data cubes (and higher-dimensional
arrays) so long as the tile size is effectively 2-dimensional. In fact,
PyFITS will automatically use compatible tile sizes even if they're not
explicitly specified. (#171)
- Added support for the optional ``endcard`` parameter in the
``Header.fromtextfile()`` and ``Header.totextfile()`` methods. Although
``endcard=False`` was a reasonable default assumption, there are still text
dumps of FITS headers that include the END card, so this should have been
more flexible. (#176)
- Fixed a crash when running fitsdiff on two empty (that is, zero row) tables.
(#178)
- Fixed an issue where opening files containing random groups HDUs in update
mode could cause an unnecessary rewrite of the file even if none of the
data is modified. (#179)
- Fixed a bug that could caused a deadlock in the filesystem on OSX if PyFITS
is used with Numpy 1.7 in some cases. (#180)
- Fixed a crash when generating diff reports from diffs using the
``ignore_comments`` options. (#181)
- Fixed some bugs with WCS Paper IV record-valued keyword cards:
- Cards that looked kind of like RVKCs but were not intended to be were
over-permissively treated as such--commentary keywords like COMMENT and
HISTORY were particularly affected. (#183)
- Looking up a card in a header by its standard FITS keyword only should
always return the raw value of that card. That way cards containing
values that happen to valid RVKCs but were not intended to be will still
be treated like normal cards. (#184)
- Looking up a RVKC in a header with only part of the field-specifier (for
example "DP1.AXIS" instead of "DP1.AXIS.1") was implicitly treated as a
wildcard lookup. (#184)
- Fixed a crash when diffing two FITS files where at least one contains a
compressed image HDU which was not recognized as an image instead of a
table. (#187)
- Fixed bugs in the backwards compatibility layer for the ``CardList.index``
and ``CardList.count`` methods. (#190)
- Improved ``__repr__`` and text file representation of cards with long values
that are split into CONTINUE cards. (#193)
- Fixed a crash when trying to assign a long (> 72 character) value to blank
('') keywords. This also changed how blank keywords are represented--there
are still exactly 8 spaces before any commentary content can begin; this
*may* affect the exact display of header cards that assumed there could be
fewer spaces in a blank keyword card before the content begins. However, the
current approach is more in line with the requirements of the FITS standard.
(#194)
3.0.10 (2013-01-02)
-------------------
- Improved handling of scaled images and pseudo-unsigned integer images in
compressed image HDUs. They now work more transparently like normal image
HDUs with support for the ``do_not_scale_image_data`` and ``uint`` options,
as well as ``scale_back`` and ``save_backup``. The ``.scale()`` method
works better too. Backported from 3.1.1. (#88)
- Permits non-string values for the EXTNAME keyword when reading in a file,
rather than throwing an exception due to the malformatting. Added
verification for the format of the EXTNAME keyword when writing. Backported
from 3.1.1. (#96)
- Added support for EXTNAME and EXTVER in PRIMARY HDUs. That is, if EXTNAME
is specified in the header, it will also be reflected in the ``.name``
attribute and in ``pyfits.info()``. These keywords used to be verbotten in
PRIMARY HDUs, but the latest version of the FITS standard allows them.
Backported from 3.1.1. (#151)
- HCOMPRESS can again be used to compress data cubes (and higher-dimensional
arrays) so long as the tile size is effectively 2-dimensional. In fact,
PyFITS will not automatically use compatible tile sizes even if they're not
explicitly specified. Backported from 3.1.1. (#171)
- Fixed a bug when writing out files containing zero-width table columns,
where the TFIELDS keyword would be updated incorrectly, leaving the table
largely unreadable. Backported from 3.1.0. (#174)
- Fixed an issue where opening files containing random groups HDUs in update
mode could cause an unnecessary rewrite of the file even if none of the
data is modified. Backported from 3.1.1. (#179)
- Fixed a bug that could caused a deadlock in the filesystem on OSX if PyFITS
is used with Numpy 1.7 in some cases. Backported from 3.1.1. (#180)
3.1 (2012-08-08)
----------------
Highlights
^^^^^^^^^^
- The ``Header`` object has been significantly reworked, and ``CardList``
objects are now deprecated (their functionality folded into the ``Header``
class). See API Changes below for more details.
- Memory maps are now used by default to access HDU data. See API Changes
below for more details.
- Now includes a new version of the ``fitsdiff`` program for comparing two
FITS files, and a new FITS comparison API used by ``fitsdiff``. See New
Features below.
API Changes
^^^^^^^^^^^
- The ``Header`` class has been rewritten, and the ``CardList`` class is
deprecated. Most of the basic details of working with FITS headers are
unchanged, and will not be noticed by most users. But there are differences
in some areas that will be of interest to advanced users, and to application
developers. For full details of the changes, see the "Header Interface
Transition Guide" section in the PyFITS documentation. See ticket #64 on
the PyFITS Trac for futher details and background. Some highlights are
listed below:
* The Header class now fully implements the Python dict interface, and can
be used interchangably with a dict, where the keys are header keywords.
* New keywords can be added to the header using normal keyword assignment
(previously it was necessary to use ``Header.update`` to add new
keywords). For example::
>>> header['NAXIS'] = 2
will update the existing 'FOO' keyword if it already exists, or add a new
one if it doesn't exist, just like a dict.
* It is possible to assign both a value and a comment at the same time using
a tuple::
>>> header['NAXIS'] = (2, 'Number of axes')
* To add/update a new card and ensure it's added in a specific location, use
``Header.set()``::
>>> header.set('NAXIS', 2, 'Number of axes', after='BITPIX')
This works the same as the old ``Header.update()``. ``Header.update()``
still works in the old way too, but is deprecated.
* Although ``Card`` objects still exist, it generally is not necessary to
work with them directly. ``Header.ascardlist()``/``Header.ascard`` are
deprecated and should not be used. To directly access the ``Card``
objects in a header, use ``Header.cards``.
* To access card comments, it is still possible to either go through the
card itself, or through ``Header.comments``. For example::
>>> header.cards['NAXIS'].comment
Number of axes
>>> header.comments['NAXIS']
Number of axes
* ``Card`` objects can now be used interchangeably with
``(keyword, value, comment)`` 3-tuples. They still have ``.value`` and
``.comment`` attributes as well. The ``.key`` attribute has been renamed
to ``.keyword`` for consistency, though ``.key`` is still supported (but
deprecated).
- Memory mapping is now used by default to access HDU data. That is,
``pyfits.open()`` uses ``memmap=True`` as the default. This provides better
performance in the majority of use cases--there are only some I/O intensive
applications where it might not be desirable. Enabling mmap by default also
enabled finding and fixing a large number of bugs in PyFITS' handling of
memory-mapped data (most of these bug fixes were backported to PyFITS
3.0.5). (#85)
* A new ``pyfits.USE_MEMMAP`` global variable was added. Set
``pyfits.USE_MEMMAP = False`` to change the default memmap setting for
opening files. This is especially useful for controlling the behavior in
applications where pyfits is deeply embedded.
* Likewise, a new ``PYFITS_USE_MEMMAP`` environment variable is supported.
Set ``PYFITS_USE_MEMMAP = 0`` in your environment to change the default
behavior.
- The ``size()`` method on HDU objects is now a ``.size`` property--this
returns the size in bytes of the data portion of the HDU, and in most cases
is equivalent to ``hdu.data.nbytes`` (#83)
- ``BinTableHDU.tdump`` and ``BinTableHDU.tcreate`` are deprecated--use
``BinTableHDU.dump`` and ``BinTableHDU.load`` instead. The new methods
output the table data in a slightly different format from previous versions,
which places quotes around each value. This format is compatible with data
dumps from previous versions of PyFITS, but not vice-versa due to a parsing
bug in older versions.
- Likewise the ``pyfits.tdump`` and ``pyfits.tcreate`` convenience function
versions of these methods have been renamed ``pyfits.tabledump`` and
``pyfits.tableload``. The old deprecated, but currently retained for
backwards compatibility. (r1125)
- A new global variable ``pyfits.EXTENSION_NAME_CASE_SENSITIVE`` was added.
This serves as a replacement for ``pyfits.setExtensionNameCaseSensitive``
which is not deprecated and may be removed in a future version. To enable
case-sensitivity of extension names (i.e. treat 'sci' as distict from 'SCI')
set ``pyfits.EXTENSION_NAME_CASE_SENSITIVE = True``. The default is
``False``. (r1139)
- A new global configuration variable ``pyfits.STRIP_HEADER_WHITESPACE`` was
added. By default, if a string value in a header contains trailing
whitespace, that whitespace is automatically removed when the value is read.
Now if you set ``pyfits.STRIP_HEADER_WHITESPACE = False`` all whitespace is
preserved. (#146)
- The old ``classExtensions`` extension mechanism (which was deprecated in
PyFITS 3.0) is removed outright. To our knowledge it was no longer used
anywhere. (r1309)
- Warning messages from PyFITS issued through the Python warnings API are now
output to stderr instead of stdout, as is the default. PyFITS no longer
modifies the default behavior of the warnings module with respect to which
stream it outputs to. (r1319)
- The ``checksum`` argument to ``pyfits.open()`` now accepts a value of
'remove', which causes any existing CHECKSUM/DATASUM keywords to be ignored,
and removed when the file is saved.
New Features
^^^^^^^^^^^^
- Added support for the proposed "FITS" extension HDU type. See
http://listmgr.cv.nrao.edu/pipermail/fitsbits/2002-April/001094.html. FITS
HDUs contain an entire FITS file embedded in their data section. `FitsHDU`
objects work like other HDU types in PyFITS. Their ``.data`` attribute
returns the raw data array. However, they have a special ``.hdulist``
attribute which processes the data as a FITS file and returns it as an
in-memory HDUList object. FitsHDU objects also support a
``FitsHDU.fromhdulist()`` classmethod which returns a new `FitsHDU` object
that embeds the supplied HDUList. (#80)
- Added a new ``.is_image`` attribute on HDU objects, which is True if the HDU
data is an 'image' as opposed to a table or something else. Here the
meaning of 'image' is fairly loose, and mostly just means a Primary or Image
extension HDU, or possibly a compressed image HDU (#71)
- Added an ``HDUList.fromstring`` classmethod which can parse a FITS file
already in memory and instantiate and ``HDUList`` object from it. This
could be useful for integrating PyFITS with other libraries that work on
FITS file, such as CFITSIO. It may also be useful in streaming
applications. The name is a slight misnomer, in that it actually accepts
any Python object that implements the buffer interface, which includes
``bytes``, ``bytearray``, ``memoryview``, ``numpy.ndarray``, etc. (#90)
- Added a new ``pyfits.diff`` module which contains facilities for comparing
FITS files. One can use the ``pyfits.diff.FITSDiff`` class to compare two
FITS files in their entirety. There is also a ``pyfits.diff.HeaderDiff``
class for just comparing two FITS headers, and other similar interfaces.
See the PyFITS Documentation for more details on this interface. The
``pyfits.diff`` module powers the new ``fitsdiff`` program installed with
PyFITS. After installing PyFITS, run ``fitsdiff --help`` for usage details.
- ``pyfits.open()`` now accepts a ``scale_back`` argument. If set to
``True``, this automatically scales the data using the original BZERO and
BSCALE parameters the file had when it was first opened, if any, as well as
the original BITPIX. For example, if the original BITPIX were 16, this
would be equivalent to calling ``hdu.scale('int16', 'old')`` just before
calling ``flush()`` or ``close()`` on the file. This option applies to all
HDUs in the file. (#120)
- ``pyfits.open()`` now accepts a ``save_backup`` argument. If set to
``True``, this automatically saves a backup of the original file before
flushing any changes to it (this of course only applies to update and append
mode). This may be especially useful when working with scaled image data.
(#121)
Changes in Behavior
^^^^^^^^^^^^^^^^^^^
- Warnings from PyFITS are not output to stderr by default, instead of stdout
as it has been for some time. This is contrary to most users' expectations
and makes it more difficult for them to separate output from PyFITS from the
desired output for their scripts. (r1319)
Bug Fixes
^^^^^^^^^
- Fixed ``pyfits.tcreate()`` (now ``pyfits.tableload()``) to be more robust
when encountering blank lines in a column definition file (#14)
- Fixed a fairly rare crash that could occur in the handling of CONTINUE cards
when using Numpy 1.4 or lower (though 1.4 is the oldest version supported by
PyFITS). (r1330)
- Fixed ``_BaseHDU.fromstring`` to actually correctly instantiate an HDU
object from a string/buffer containing the header and data of that HDU.
This allowed for the implementation of ``HDUList.fromstring`` described
above. (#90)
- Fixed a rare corner case where, in some use cases, (mildly, recoverably)
malformatted float values in headers were not properly returned as floats.
(#137)
- Fixed a corollary to the previous bug where float values with a leading zero
before the decimal point had the leading zero unnecessarily removed when
saving changes to the file (eg. "0.001" would be written back as ".001" even
if no changes were otherwise made to the file). (#137)
- When opening a file containing CHECKSUM and/or DATASUM keywords in update
mode, the CHECKSUM/DATASUM are updated and preserved even if the file was
opened with checksum=False. This change in behavior prevents checksums from
being unintentionally removed. (#148)
- Fixed a bug where ``ImageHDU.scale(option='old')`` wasn't working at all--it
was not restoring the image to its original BSCALE and BZERO values. (#162)
- Fixed a bug when writing out files containing zero-width table columns,
where the TFIELDS keyword would be updated incorrectly, leaving the table
largely unreadable. This fix will be backported to the 3.0.x series in
version 3.0.10. (#174)
3.0.9 (2012-08-06)
------------------
This is a bug fix release for the 3.0.x series.
Bug Fixes
^^^^^^^^^
- Fixed ``Header.values()``/``Header.itervalues()`` and ``Header.items()``/
``Header.iteritems()`` to correctly return the different values for
duplicate keywords (particularly commentary keywords like HISTORY and
COMMENT). This makes the old Header implementation slightly more compatible
with the new implementation in PyFITS 3.1. (#127)
.. note::
This fix did not change the existing behavior from earlier PyFITS
versions where ``Header.keys()`` returns all keywords in the header with
duplicates removed. PyFITS 3.1 changes that behavior, so that
``Header.keys()`` includes duplicates.
- Fixed a bug where ``ImageHDU.scale(option='old')`` wasn't working at all--it
was not restoring the image to its original BSCALE and BZERO values. (#162)
- Fixed a bug where opening a file containing compressed image HDUs in
'update' mode and then immediately closing it without making any changes
caused the file to be rewritten unncessarily. (#167)
- Fixed two memory leaks that could occur when writing compressed image data,
or in some cases when opening files containing compressed image HDUs in
'update' mode. (#168)
3.0.8 (2012-06-04)
------------------
Changes in Behavior
^^^^^^^^^^^^^^^^^^^
- Prior to this release, image data sections did not work with scaled
data--that is, images with non-trivial BSCALE and/or BZERO values.
Previously, in order to read such images in sections, it was necessary to
manually apply the BSCALE+BZERO to each section. It's worth noting that
sections *did* support pseudo-unsigned ints (flakily). This change just
extends that support for general BSCALE+BZERO values.
Bug Fixes
^^^^^^^^^
- Fixed a bug that prevented updates to values in boolean table columns from
being saved. This turned out to be a symptom of a deeper problem that could
prevent other table updates from being saved as well. (#139)
- Fixed a corner case in which a keyword comment ending with the string "END"
could, in some circumstances, cause headers (and the rest of the file after
that point) to be misread. (#142)
- Fixed support for scaled image data and psuedo-unsigned ints in image data
sections (``hdu.section``). Previously this was not supported at all. At
some point support was supposedly added, but it was buggy and incomplete.
Now the feature seems to work much better. (#143)
- Fixed the documentation to point out that image data sections *do* support
non-contiguous slices (and have for a long time). The documentation was
never updated to reflect this, and misinformed users that only contiguous
slices were supported, leading to some confusion. (#144)
- Fixed a bug where creating an ``HDUList`` object containing multiple PRIMARY
HDUs caused an infinite recursion when validating the object prior to
writing to a file. (#145)
- Fixed a rare but serious case where saving an update to a file that
previously had a CHECKSUM and/or DATASUM keyword, but removed the checksum
in saving, could cause the file to be slightly corrupted and unreadable.
(#147)
- Fixed problems with reading "non-standard" FITS files with primary headers
containing SIMPLE = F. PyFITS has never made many guarantees as to how such
files are handled. But it should at least be possible to read their
headers, and the data if possible. Saving changes to such a file should not
try to prepend an unwanted valid PRIMARY HDU. (#157)
- Fixed a bug where opening an image with ``disable_image_compression = True``
caused compression to be disabled for all subsequent ``pyfits.open()`` calls.
(r1651)
3.0.7 (2012-04-10)
------------------
Changes in Behavior
^^^^^^^^^^^^^^^^^^^
- Slices of GroupData objects now return new GroupData objects instead of
extended multi-row _Group objects. This is analogous to how PyFITS 3.0 fixed
FITS_rec slicing, and should have been fixed for GroupData at the same time.
The old behavior caused bugs where functions internal to Numpy expected that
slicing an ndarray would return a new ndarray. As this is a rare usecase
with a rare feature most users are unlikely to be affected by this change.
- The previously internal _Group object for representing individual group
records in a GroupData object are renamed Group and are now a public
interface. However, there's almost no good reason to create Group objects
directly, so it shouldn't be considered a "new feature".
- An annoyance from PyFITS 3.0.6 was fixed, where the value of the EXTEND
keyword was always being set to F if there are not actually any extension
HDUs. It was unnecessary to modify this value.
Bug Fixes
^^^^^^^^^
- Fixed GroupData objects to return new GroupData objects when sliced instead
of _Group record objects. See "Changes in behavior" above for more details.
- Fixed slicing of Group objects--previously it was not possible to slice
slice them at all.
- Made it possible to assign `np.bool_` objects as header values. (#123)
- Fixed overly strict handling of the EXTEND keyword; see "Changes in
behavior" above. (#124)
- Fixed many cases where an HDU's header would be marked as "modified" by
PyFITS and rewritten, even when no changes to the header are necessary.
(#125)
- Fixed a bug where the values of the PTYPEn keywords in a random groups HDU
were forced to be all lower-case when saving the file. (#130)
- Removed an unnecessary inline import in `ExtensionHDU.__setattr__` that was
causing some slowdown when opening files containing a large number of
extensions, plus a few other small (but not insignficant) performance
improvements thanks to Julian Taylor. (#133)
- Fixed a regression where header blocks containing invalid end-of-header
padding (i.e. null bytes instead of spaces) couldn't be parsed by PyFITS.
Such headers can be parsed again, but a warning is raised, as such headers
are not valid FITS. (#136)
- Fixed a memory leak where table data in random groups HDUs weren't being
garbage collected. (#138)
3.0.6 (2012-02-29)
------------------
Highlights
^^^^^^^^^^
The main reason for this release is to fix an issue that was introduced in
PyFITS 3.0.5 where merely opening a file containing scaled data (that is, with
non-trivial BSCALE and BZERO keywords) in 'update' mode would cause the data
to be automatically rescaled--possibly converting the data from ints to
floats--as soon as the file is closed, even if the application did not touch
the data. Now PyFITS will only rescale the data in an extension when the data
is actually accessed by the application. So opening a file in 'update' mode
in order to modify the header or append new extensions will not cause any
change to the data in existing extensions.
This release also fixes a few Windows-specific bugs found through more
extensive Windows testing, and other miscellaneous bugs.
Bug Fixes
^^^^^^^^^
- More accurate error messages when opening files containing invalid header
cards. (#109)
- Fixed a possible reference cycle/memory leak that was caught through more
extensive testing on Windows. (#112)
- Fixed 'ostream' mode to open the underlying file in 'wb' mode instead of 'w'
mode. (#112)
- Fixed a Windows-only issue where trying to save updates to a resized FITS
file could result in a crash due to there being open mmaps on that file.
(#112)
- Fixed a crash when trying to create a FITS table (i.e. with new_table())
from a Numpy array containing bool fields. (#113)
- Fixed a bug where manually initializing an ``HDUList`` with a list of of
HDUs wouldn't set the correct EXTEND keyword value on the primary HDU.
(#114)
- Fixed a crash that could occur when trying to deepcopy a Header in Python <
2.7. (#115)
- Fixed an issue where merely opening a scaled image in 'update' mode would
cause the data to be converted to floats when the file is closed. (#119)
3.0.5 (2012-01-30)
------------------
- Fixed a crash that could occur when accessing image sections of files
opened with memmap=True. (r1211)
- Fixed the inconsistency in the behavior of files opened in 'readonly' mode
when memmap=True vs. when memmap=False. In the latter case, although
changes to array data were not saved to disk, it was possible to update the
array data in memory. On the other hand with memmap=True, 'readonly' mode
prevented even in-memory modification to the data. This is what
'copyonwrite' mode was for, but difference in behavior was confusing. Now
'readonly' is equivalent to 'copyonwrite' when using memmap. If the old
behavior of denying changes to the array data is necessary, a new
'denywrite' mode may be used, though it is only applicable to files opened
with memmap. (r1275)
- Fixed an issue where files opened with memmap=True would return image data
as a raw numpy.memmap object, which can cause some unexpected
behaviors--instead memmap object is viewed as a numpy.ndarray. (r1285)
- Fixed an issue in Python 3 where a workaround for a bug in Numpy on Python 3
interacted badly with some other software, namely to vo.table package (and
possibly others). (r1320, r1337, and #110)
- Fixed buggy behavior in the handling of SIGINTs (i.e. Ctrl-C keyboard
interrupts) while flushing changes to a FITS file. PyFITS already prevented
SIGINTs from causing an incomplete flush, but did not clean up the signal
handlers properly afterwards, or reraise the keyboard interrupt once the
flush was complete. (r1321)
- Fixed a crash that could occur in Python 3 when opening files with checksum
checking enabled. (r1336)
- Fixed a small bug that could cause a crash in the `StreamingHDU` interface
when using Numpy below version 1.5.
- Fixed a crash that could occur when creating a new `CompImageHDU` from an
array of big-endian data. (#104)
- Fixed a crash when opening a file with extra zero padding at the end.
Though FITS files should not have such padding, it's not explictly forbidden
by the format either, and PyFITS shouldn't stumble over it. (#106)
- Fixed a major slowdown in opening tables containing large columns of string
values. (#111)
3.0.4 (2011-11-22)
------------------
- Fixed a crash when writing HCOMPRESS compressed images that could happen on
Python 2.5 and 2.6. (r1217)
- Fixed a crash when slicing an table in a file opened in 'readonly' mode with
memmap=True. (r1230)
- Writing changes to a file or writing to a new file verifies the output in
'fix' mode by default instead of 'exception'--that is, PyFITS will
automatically fix common FITS format errors rather than raising an
exception. (r1243)
- Fixed a bug where convenience functions such as getval() and getheader()
crashed when specifying just 'PRIMARY' as the extension to use (r1263).
- Fixed a bug that prevented passing keyword arguments (beyond the standard
data and header arguments) as positional arguments to the constructors of
extension HDU classes.
- Fixed some tests that were failing on Windows--in this case the tests
themselves failed to close some temp files and Windows refused to delete them
while there were still open handles on them. (r1295)
- Fixed an issue with floating point formatting in header values on Python 2.5
for Windows (and possibly other platforms). The exponent was zero-padded to
3 digits; although the FITS standard makes no specification on this, the
formatting is now normalized to always pad the exponent to two digits.
(r1295)
- Fixed a bug where long commentary cards (such as HISTORY and COMMENT) were
broken into multiple CONTINUE cards. However, commentary cards are not
expected to be found in CONTINUE cards. Instead these long cards are broken
into multiple commentary cards. (#97)
- GZIP/ZIP-compressed FITS files can be detected and opened regardless of
their filename extension. (#99)
- Fixed a serious bug where opening scaled images in 'update' mode and then
closing the file without touching the data would cause the file to be
corrupted. (#101)
3.0.3 (2011-10-05)
------------------
- Fixed several small bugs involving corner cases in record-valued keyword
cards (#70)
- In some cases HDU creation failed if the first keyword value in the header
was not a string value (#89)
- Fixed a crash when trying to compute the HDU checksum when the data array
contains an odd number of bytes (#91)
- Disabled an unnecessary warning that was displayed on opening compressed
HDUs with disable_image_compression = True (#92)
- Fixed a typo in code for handling HCOMPRESS compressed images.
3.0.2 (2011-09-23)
------------------
- The ``BinTableHDU.tcreate`` method and by extension the ``pyfits.tcreate``
function don't get tripped up by blank lines anymore (#14)
- The presence, value, and position of the EXTEND keyword in Primary HDUs is
verified when reading/writing a FITS file (#32)
- Improved documentation (in warning messages as well as in the handbook) that
PyFITS uses zero-based indexing (as one would expect for C/Python code, but
contrary to the PyFITS standard which was written with FORTRAN in mind)
(#68)
- Fixed a bug where updating a header card comment could cause the value to be
lost if it had not already been read from the card image string.
- Fixed a related bug where changes made directly to Card object in a header
(i.e. assigning directly to card.value or card.comment) would not propagate
when flushing changes to the file (#69) [Note: This and the bug above it
were originally reported as being fixed in version 3.0.1, but the fix was
never included in the release.]
- Improved file handling, particularly in Python 3 which had a few small file
I/O-related bugs (#76)
- Fixed a bug where updating a FITS file would sometimes cause it to lose its
original file permissions (#79)
- Fixed the handling of TDIMn keywords; 3.0 added support for them, but got
the axis order backards (they were treated as though they were row-major)
(#82)
- Fixed a crash when a FITS file containing scaled data is opened and
immediately written to a new file without explicitly viewing the data first
(#84)
- Fixed a bug where creating a table with columns named either 'names' or
'formats' resulted in an infinite recursion (#86)
3.0.1 (2011-09-12)
------------------
- Fixed a bug where updating a header card comment could cause the value to be
lost if it had not already been read from the card image string.
- Changed ``_TableBaseHDU.data`` so that if the data contain an empty table a
``FITS_rec`` object with zero rows is returned rather than ``None``.
- The ``.key`` attribute of ``RecordValuedKeywordCards`` now returns the full
keyword+field-specifier value, instead of just the plain keyword (#46)
- Fixed a related bug where changes made directly to Card object in a header
(i.e. assigning directly to card.value or card.comment) would not propagate
when flushing changes to the file (#69)
- Fixed a bug where writing a table with zero rows could fail in some cases
(#72)
- Miscellanous small bug fixes that were causing some tests to fail,
particularly on Python 3 (#74, #75)
- Fixed a bug where creating a table column from an array in non-native byte
order would not preserve the byte order, thus interpreting the column array
using the wrong byte order (#77)
3.0.0 (2011-08-23)
--------------------
- Contains major changes, bumping the version to 3.0
- Large amounts of refactoring and reorganization of the code; tried to
preserve public API backwards-compatibility with older versions (private API
has many changes and is not guaranteed to be backwards-compatible). There
are a few small public API changes to be aware of:
* The pyfits.rec module has been removed completely. If your version of
numpy does not have the numpy.core.records module it is too old to be used
with PyFITS.
* The ``Header.ascardlist()`` method is deprecated--use the ``.ascard``
attribute instead.
* ``Card`` instances have a new ``.cardimage`` attribute that should be used
rather than ``.ascardimage()``, which may become deprecated.
* The ``Card.fromstring()`` method is now a classmethod. It returns a new
``Card`` instance rather than modifying an existing instance.
* The ``req_cards()`` method on HDU instances has changed: The ``pos``
argument is not longer a string. It is either an integer value (meaning
the card's position must match that value) or it can be a function that
takes the card's position as it's argument, and returns True if the
position is valid. Likewise, the ``test`` argument no longer takes a
string, but instead a function that validates the card's value and returns
True or False.
* The ``get_coldefs()`` method of table HDUs is deprecated. Use the
``.columns`` attribute instead.
* The ``ColDefs.data`` attribute is deprecated--use ``ColDefs.columns``
instead (though in general you shouldn't mess with it directly--it might
become internal at some point).
* ``FITS_record`` objects take ``start`` and ``end`` as arguments instead of
``startColumn`` and ``endColumn`` (these are rarely created manually, so
it's unlikely that this change will affect anyone).
* ``BinTableHDU.tcreate()`` is now a classmethod, and returns a new
``BinTableHDU`` instance.
* Use ``ExtensionHDU`` and ``NonstandardExtHDU`` for making new extension HDU
classes. They are now public interfaces, wheres previously they were
private and prefixed with underscores.
* Possibly others--please report if you find any changes that cause
difficulties.
- Calls to deprecated functions will display a Deprecation warning. However,
in Python 2.7 and up Deprecation warnings are ignored by default, so run
Python with the `-Wd` option to see if you're using any deprecated
functions. If we get close to actually removing any functions, we might
make the Deprecation warnings display by default.
- Added basic Python 3 support
- Added support for multi-dimensional columns in tables as specified by the
TDIMn keywords (#47)
- Fixed a major memory leak that occurred when creating new tables with the
``new_table()`` function (#49)
be padded with zero-bytes) vs ASCII tables (where strings are padded with
spaces) (#15)
- Fixed a bug in which the case of Random Access Group parameters names was not
preserved when writing (#41)
- Added support for binary table fields with zero width (#42)
- Added support for wider integer types in ASCII tables; although this is non-
standard, some GEIS images require it (#45)
- Fixed a bug that caused the index_of() method of HDULists to crash when the
HDUList object is created from scratch (#48)
- Fixed the behavior of string padding in binary tables (where strings should
be padded with nulls instead of spaces)
- Fixed a rare issue that caused excessive memory usage when computing
checksums using a non-standard block size (see r818)
- Add support for forced uint data in image sections (#53)
- Fixed an issue where variable-length array columns were not extended when
creating a new table with more rows than the original (#54)
- Fixed tuple and list-based indexing of FITS_rec objects (#55)
- Fixed an issue where BZERO and BSCALE keywords were appended to headers in
the wrong location (#56)
- ``FITS_record`` objects (table rows) have full slicing support, including
stepping, etc. (#59)
- Fixed a bug where updating multiple files simultaneously (such as when
running parallel processes) could lead to a race condition with mktemp()
(#61)
- Fixed a bug where compressed image headers were not in the order expected by
the funpack utility (#62)
jperkin
pushed a commit
that referenced
this issue
Mar 17, 2014
v0.8.2, 2013-11-20 ([changes](simplecov-ruby/simplecov@v0.8.1...v0.8.2)) ===================== ## Bugfixes * Replaced the locking behaviour [via lockfile gem](simplecov-ruby/simplecov#185) with plain Ruby explicit file locking when merging results. This should make simplecov merging to behave well on Windows again. See [#258](simplecov-ruby/simplecov#258) and [#223](simplecov-ruby/simplecov#223) (thanks to @tomykaira) v0.8.1, 2013-11-10 ([changes](simplecov-ruby/simplecov@v0.8.0...v0.8.1)) ===================== ## Bugfixes * Fixed a regression introduced in 0.8.0 - the Forwardable STDLIB module is now required explicitly. See [#256](simplecov-ruby/simplecov#256) (thanks to @kylev) v0.8.0, 2013-11-10 ([changes](simplecov-ruby/simplecov@v0.7.1...v0.8.0)) ===================== **Note: Yanked the same day because of the regression that 0.8.1 fixes, see above** ## TL;DR It's been way too long since the last official release 0.7.1, but this was partly due to it proving itself quite stable in most circumstances. This release brings various further stability improvements to result set merging (especially when working with parallel_tests), the configuration, source file encodings, and command name guessing. The 0.8 line is the last one to cooperate with Ruby < 1.9. Starting with 0.9, SimpleCov will assume to be running in Ruby 1.9+, and will not try to detect or bail silently on older Ruby versions. An appropriate deprecation warning has been added. ## Features * Configuration blocks now have access to variables and methods outside of the block's scope. See [#238](simplecov-ruby/simplecov#238) (thanks to @ms-tg) * You can now have a global `~/.simplecov` configuration file. See [#195](simplecov-ruby/simplecov#195) (thanks to @spagalloco) * simplecov-html now uses the MIT-licensed colorbox plugin. Some adjustments when viewing source files, including retaining the currently open file on refresh have been added. See [simplecov-html #15](simplecov-ruby/simplecov-html#15) (thanks to @chetan) * Adds support for Rails 4 command guessing, removes default group `vendor/plugins`. See [#181](simplecov-ruby/simplecov#181) and [#203](simplecov-ruby/simplecov#203) (thanks to @semanticart and @phallstrom) * You can now load simplecov without the default settings by doing `require 'simplecov/no_defaults'` or setting `ENV['SIMPLECOV_NO_DEFAULTS']`. Check `simplecov/defaults` to see what preconfigurations are getting dropped by using this. See [#209](simplecov-ruby/simplecov#209) (thanks to @ileitch) * The result set merging now uses the `lockfile` gem to avoid race conditions. See [#185](simplecov-ruby/simplecov#185) (thanks to @jshraibman-mdsol). * Automatically detect the usage of parallel_tests and adjust the command name with the test env number accordingly, See [#64](simplecov-ruby/simplecov#64) and [#185](simplecov-ruby/simplecov#185) (thanks to @jshraibman-mdsol). ## Enhancements * Rename adapters to "profiles" given that they are bundles of settings. The old adapter methods are deprecated, but remain available for now. See [#207](simplecov-ruby/simplecov#207) (thanks to @mikerobe) * Tweaks to the automatic test suite naming. In particular, `rspec/features` should now be correctly attributed to RSpec, not Cucumber. See [#212](simplecov-ruby/simplecov#212) (thanks to @ersatzryan and @betelgeuse) * MiniTest should now be identified correctly by the command name guesser. See [#244](simplecov-ruby/simplecov#244) (thanks to @envygeeks) * Makes SimpleCov resilient to inclusion of mathn library. See [#175](simplecov-ruby/simplecov#175) and [#140](simplecov-ruby/simplecov#140) (thanks to @scotje) * Allow coverage_dir to be an absolute path. * See [#190](simplecov-ruby/simplecov#190) (thanks to @jshraibman-mdsol) * The internal cucumber test suite now uses Capybara 2. See [#206](simplecov-ruby/simplecov#206) (thanks to @infertux) * Work-arounds for the Coverage library shipped in JRuby 1.6 to behave in line with MRI. See [#174](simplecov-ruby/simplecov#174) (thanks to @grddev) * Fix warning: instance variable @exit_status not initialized. See [#242](simplecov-ruby/simplecov#242) and [#213](simplecov-ruby/simplecov#213) (thanks to @sferik and @infertux) ## Bugfixes * Correct result calculations for people using :nocov: tags. See [#215](simplecov-ruby/simplecov#215) (thanks to @aokolish) * Average hits per line for groups of files is now computed correctly. See [#192](http://github.com/colszowka/simplecov/pull/192) and [#179](http://github.com/colszowka/simplecov/issues/179) (thanks to @Graysonwright) * Compatability with BINARY internal encoding. See [#194](simplecov-ruby/simplecov#194) and [#127](simplecov-ruby/simplecov#127) (thanks to @justfalter) * Special characters in `SimpleCov.root` are now correctly escaped before being used as a RegExp. See [#204](simplecov-ruby/simplecov#204) and [#237](simplecov-ruby/simplecov#237) (thanks to @rli9)
jperkin
pushed a commit
that referenced
this issue
Mar 18, 2014
v0.8.2, 2013-11-20 ([changes](simplecov-ruby/simplecov@v0.8.1...v0.8.2)) ===================== ## Bugfixes * Replaced the locking behaviour [via lockfile gem](simplecov-ruby/simplecov#185) with plain Ruby explicit file locking when merging results. This should make simplecov merging to behave well on Windows again. See [#258](simplecov-ruby/simplecov#258) and [#223](simplecov-ruby/simplecov#223) (thanks to @tomykaira) v0.8.1, 2013-11-10 ([changes](simplecov-ruby/simplecov@v0.8.0...v0.8.1)) ===================== ## Bugfixes * Fixed a regression introduced in 0.8.0 - the Forwardable STDLIB module is now required explicitly. See [#256](simplecov-ruby/simplecov#256) (thanks to @kylev) v0.8.0, 2013-11-10 ([changes](simplecov-ruby/simplecov@v0.7.1...v0.8.0)) ===================== **Note: Yanked the same day because of the regression that 0.8.1 fixes, see above** ## TL;DR It's been way too long since the last official release 0.7.1, but this was partly due to it proving itself quite stable in most circumstances. This release brings various further stability improvements to result set merging (especially when working with parallel_tests), the configuration, source file encodings, and command name guessing. The 0.8 line is the last one to cooperate with Ruby < 1.9. Starting with 0.9, SimpleCov will assume to be running in Ruby 1.9+, and will not try to detect or bail silently on older Ruby versions. An appropriate deprecation warning has been added. ## Features * Configuration blocks now have access to variables and methods outside of the block's scope. See [#238](simplecov-ruby/simplecov#238) (thanks to @ms-tg) * You can now have a global `~/.simplecov` configuration file. See [#195](simplecov-ruby/simplecov#195) (thanks to @spagalloco) * simplecov-html now uses the MIT-licensed colorbox plugin. Some adjustments when viewing source files, including retaining the currently open file on refresh have been added. See [simplecov-html #15](simplecov-ruby/simplecov-html#15) (thanks to @chetan) * Adds support for Rails 4 command guessing, removes default group `vendor/plugins`. See [#181](simplecov-ruby/simplecov#181) and [#203](simplecov-ruby/simplecov#203) (thanks to @semanticart and @phallstrom) * You can now load simplecov without the default settings by doing `require 'simplecov/no_defaults'` or setting `ENV['SIMPLECOV_NO_DEFAULTS']`. Check `simplecov/defaults` to see what preconfigurations are getting dropped by using this. See [#209](simplecov-ruby/simplecov#209) (thanks to @ileitch) * The result set merging now uses the `lockfile` gem to avoid race conditions. See [#185](simplecov-ruby/simplecov#185) (thanks to @jshraibman-mdsol). * Automatically detect the usage of parallel_tests and adjust the command name with the test env number accordingly, See [#64](simplecov-ruby/simplecov#64) and [#185](simplecov-ruby/simplecov#185) (thanks to @jshraibman-mdsol). ## Enhancements * Rename adapters to "profiles" given that they are bundles of settings. The old adapter methods are deprecated, but remain available for now. See [#207](simplecov-ruby/simplecov#207) (thanks to @mikerobe) * Tweaks to the automatic test suite naming. In particular, `rspec/features` should now be correctly attributed to RSpec, not Cucumber. See [#212](simplecov-ruby/simplecov#212) (thanks to @ersatzryan and @betelgeuse) * MiniTest should now be identified correctly by the command name guesser. See [#244](simplecov-ruby/simplecov#244) (thanks to @envygeeks) * Makes SimpleCov resilient to inclusion of mathn library. See [#175](simplecov-ruby/simplecov#175) and [#140](simplecov-ruby/simplecov#140) (thanks to @scotje) * Allow coverage_dir to be an absolute path. * See [#190](simplecov-ruby/simplecov#190) (thanks to @jshraibman-mdsol) * The internal cucumber test suite now uses Capybara 2. See [#206](simplecov-ruby/simplecov#206) (thanks to @infertux) * Work-arounds for the Coverage library shipped in JRuby 1.6 to behave in line with MRI. See [#174](simplecov-ruby/simplecov#174) (thanks to @grddev) * Fix warning: instance variable @exit_status not initialized. See [#242](simplecov-ruby/simplecov#242) and [#213](simplecov-ruby/simplecov#213) (thanks to @sferik and @infertux) ## Bugfixes * Correct result calculations for people using :nocov: tags. See [#215](simplecov-ruby/simplecov#215) (thanks to @aokolish) * Average hits per line for groups of files is now computed correctly. See [#192](http://github.com/colszowka/simplecov/pull/192) and [#179](http://github.com/colszowka/simplecov/issues/179) (thanks to @Graysonwright) * Compatability with BINARY internal encoding. See [#194](simplecov-ruby/simplecov#194) and [#127](simplecov-ruby/simplecov#127) (thanks to @justfalter) * Special characters in `SimpleCov.root` are now correctly escaped before being used as a RegExp. See [#204](simplecov-ruby/simplecov#204) and [#237](simplecov-ruby/simplecov#237) (thanks to @rli9)
jperkin
pushed a commit
that referenced
this issue
Apr 1, 2014
--- 3.7 --- * Gnome keyring no longer relies on the GNOME_KEYRING_CONTROL environment variable. * Issue #140: Restore compatibility for older versions of PyWin32. --- 3.6 --- * `Pull Request #1 (github) <https://github.com/jaraco/keyring/pull/1>`_: Add support for packages that wish to bundle keyring by using relative imports throughout. --- 3.5 --- * Issue #49: Give the backend priorities a 1.5 multiplier bump when an XDG_CURRENT_DESKTOP environment variable matches the keyring's target environment. * Issue #99: Clarified documentation on location of config and data files. Prepared the code base to treat the two differently on Unix-based systems. For now, the behavior is unchanged. --- 3.4 --- * Extracted FileBacked and Encrypted base classes. * Add a pyinstaller hook to expose backend modules. Ref #124 * Pull request #41: Use errno module instead of hardcoding error codes. * SecretService backend: correctly handle cases when user dismissed the collection creation or unlock prompt. --- 3.3 --- * Pull request #40: KWallet backend will now honor the ``KDE_FULL_SESSION`` environment variable as found on openSUSE. ----- 3.2.1 ----- * SecretService backend: use a different function to check that the backend is functional. The default collection may not exist, but the collection will remain usable in that case. Also, make the error message more verbose. Resolves https://bugs.launchpad.net/bugs/1242412. --- 3.2 --- * Issue #120: Invoke KeyringBackend.priority during load_keyring to ensure that any keyring loaded is actually viable (or raises an informative exception). * File keyring: - Issue #123: fix removing items. - Correctly escape item name when removing. - Use with statement when working with files. * Add a test for removing one item in group. * Issue #81: Added experimental support for third-party backends. See `keyring.core._load_library_extensions` for information on supplying a third-party backend. --- 3.1 --- * All code now runs natively on both Python 2 and Python 3, no 2to3 conversion is required. * Testsuite: clean up, and make more use of unittest2 methods. ----- 3.0.5 ----- * Issue #114: Fix logic in pyfs detection. ----- 3.0.4 ----- * Issue #114: Fix detection of pyfs under Mercurial Demand Import. ----- 3.0.3 ----- * Simplified the implementation of ``keyring.core.load_keyring``. It now uses ``__import__`` instead of loading modules explicitly. The ``keyring_path`` parameter to ``load_keyring`` is now deprecated. Callers should instead ensure their module is available on ``sys.path`` before calling ``load_keyring``. Keyring still honors ``keyring-path``. This change fixes Issue #113 in which the explicit module loading of keyring modules was breaking package-relative imports. ----- 3.0.2 ----- * Renamed ``keyring.util.platform`` to ``keyring.util.platform_``. As reported in Issue #112 and `mercurial_keyring #31 <https://bitbucket.org/Mekk/mercurial_keyring/issue/31>`_ and in `Mercurial itself <http://bz.selenic.com/show_bug.cgi?id=4029>`_, Mercurial's Demand Import does not honor ``absolute_import`` directives, so it's not possible to have a module with the same name as another top-level module. A patch is in place to fix this issue upstream, but to support older Mercurial versions, this patch will remain for some time. ----- 3.0.1 ----- * Ensure that modules are actually imported even in Mercurial's Demand Import environment. --- 3.0 --- * Removed support for Python 2.5. * Removed names in ``keyring.backend`` moved in 1.1 and previously retained for compatibilty. ----- 2.1.1 ----- * Restored Python 2.5 compatibility (lost in 2.0). --- 2.1 --- * Issue #10: Added a 'store' attribute to the OS X Keyring, enabling custom instances of the KeyringBackend to use another store, such as the 'internet' store. For example:: keys = keyring.backends.OS_X.Keyring() keys.store = 'internet' keys.set_password(system, user, password) keys.get_password(system, user) The default for all instances can be set in the class:: keyring.backends.OS_X.Keyring.store = 'internet' * GnomeKeyring: fix availability checks, and make sure the warning message from pygobject is not printed. * Fixes to GnomeKeyring and SecretService tests. ----- 2.0.3 ----- * Issue #112: Backend viability/priority checks now are more aggressive about module presence checking, requesting ``__name__`` from imported modules to force the demand importer to actually attempt the import. ----- 2.0.2 ----- * Issue #111: Windows backend isn't viable on non-Windows platforms. ----- 2.0.1 ----- * Issue #110: Fix issues with ``Windows.RegistryKeyring``. --- 2.0 --- * Issue #80: Prioritized backend support. The primary interface for Keyring backend classes has been refactored to now emit a 'priority' based on the current environment (operating system, libraries available, etc). These priorities provide an indication of the applicability of that backend for the current environment. Users are still welcome to specify a particular backend in configuration, but the default behavior should now be to select the most appropriate backend by default. ----- 1.6.1 ----- * Only include pytest-runner in 'setup requirements' when ptr invocation is indicated in the command-line (Issue #105). --- 1.6 --- * GNOME Keyring backend: - Use the same attributes (``username`` / ``service``) as the SecretService backend uses, allow searching for old ones for compatibility. - Also set ``application`` attribute. - Correctly handle all types of errors, not only ``CANCELLED`` and ``NO_MATCH``. - Avoid printing warnings to stderr when GnomeKeyring is not available. * Secret Service backend: - Use a better label for passwords, the same as GNOME Keyring backend uses. --- 1.5 --- * SecretService: allow deleting items created using previous python-keyring versions. Before the switch to secretstorage, python-keyring didn't set "application" attribute. Now in addition to supporting searching for items without that attribute, python-keyring also supports deleting them. * Use ``secretstorage.get_default_collection`` if it's available. On secretstorage 1.0 or later, python-keyring now tries to create the default collection if it doesn't exist, instead of just raising the error. * Improvements for tests, including fix for Issue #102. --- 1.4 --- * Switch GnomeKeyring backend to use native libgnome-keyring via GObject Introspection, not the obsolete python-gnomekeyring module. --- 1.3 --- * Use the `SecretStorage library <https://pypi.python.org/pypi/SecretStorage>`_ to implement the Secret Service backend (instead of using dbus directly). Now the keyring supports prompting for and deleting passwords. Fixes #69, #77, and #93. * Catch `gnomekeyring.IOError` per the issue `reported in Nova client <https://bugs.launchpad.net/python-novaclient/+bug/1116302>`_. * Issue #92 Added support for delete_password on Mac OS X Keychain. ----- 1.2.3 ----- * Fix for Encrypted File backend on Python 3. * Issue #97 Improved support for PyPy. ----- 1.2.2 ----- * Fixed handling situations when user cancels kwallet dialog or denies access for the app. ----- 1.2.1 ----- * Fix for kwallet delete. * Fix for OS X backend on Python 3. * Issue #84: Fix for Google backend on Python 3 (use of raw_input not caught by 2to3). --- 1.2 --- * Implemented delete_password on most keyrings. Keyring 2.0 will require delete_password to implement a Keyring. Fixes #79. ----- 1.1.2 ----- * Issue #78: pyfilesystem backend now works on Windows. ----- 1.1.1 ----- * Fixed MANIFEST.in so .rst files are included. --- 1.1 --- This is the last build that will support installation in a pure-distutils mode. Subsequent releases will require setuptools/distribute to install. Python 3 installs have always had this requirement (for 2to3 install support), but starting with the next minor release (1.2+), setuptools will be required. Additionally, this release has made some substantial refactoring in an attempt to modularize the backends. An attempt has been made to maintain 100% backward-compatibility, although if your library does anything fancy with module structure or clasess, some tweaking may be necessary. The backward-compatible references will be removed in 2.0, so the 1.1+ releases represent a transitional implementation which should work with both legacy and updated module structure. * Added a console-script 'keyring' invoking the command-line interface. * Deprecated _ExtensionKeyring. * Moved PasswordSetError and InitError to an `errors` module (references kept for backward-compatibility). * Moved concrete backend implementations into their own modules (references kept for backward compatibility): - OSXKeychain -> backends.OS_X.Keyring - GnomeKeyring -> backends.Gnome.Keyring - SecretServiceKeyring -> backends.SecretService.Keyring - KDEKWallet -> backends.kwallet.Keyring - BasicFileKeyring -> backends.file.BaseKeyring - CryptedFileKeyring -> backends.file.EncryptedKeyring - UncryptedFileKeyring -> backends.file.PlaintextKeyring - Win32CryptoKeyring -> backends.Windows.EncryptedKeyring - WinVaultKeyring -> backends.Windows.WinVaultKeyring - Win32CryptoRegistry -> backends.Windows.RegistryKeyring - select_windows_backend -> backends.Windows.select_windows_backend - GoogleDocsKeyring -> backends.Google.DocsKeyring - Credential -> keyring.credentials.Credential - BaseCredential -> keyring.credentials.SimpleCredential - EnvironCredential -> keyring.credentials.EnvironCredential - GoogleEnvironCredential -> backends.Google.EnvironCredential - BaseKeyczarCrypter -> backends.keyczar.BaseCrypter - KeyczarCrypter -> backends.keyczar.Crypter - EnvironKeyczarCrypter -> backends.keyczar.EnvironCrypter - EnvironGoogleDocsKeyring -> backends.Google.KeyczarDocsKeyring - BasicPyfilesystemKeyring -> backends.pyfs.BasicKeyring - UnencryptedPyfilesystemKeyring -> backends.pyfs.PlaintextKeyring - EncryptedPyfilesystemKeyring -> backends.pyfs.EncryptedKeyring - EnvironEncryptedPyfilesystemKeyring -> backends.pyfs.KeyczarKeyring - MultipartKeyringWrapper -> backends.multi.MultipartKeyringWrapper * Officially require Python 2.5 or greater (although unofficially, this requirement has been in place since 0.10). --- 1.0 --- This backward-incompatible release attempts to remove some cruft from the codebase that's accumulated over the versions. * Removed legacy file relocation support. `keyring` no longer supports loading configuration or file-based backends from ~. If upgrading from 0.8 or later, the files should already have been migrated to their new proper locations. If upgrading from 0.7.x or earlier, the files will have to be migrated manually. * Removed CryptedFileKeyring migration support. To maintain an existing CryptedFileKeyring, one must first upgrade to 0.9.2 or later and access the keyring before upgrading to 1.0 to retain the existing keyring. * File System backends now create files without group and world permissions. Fixes #67. ------ 0.10.1 ------ * Merged 0.9.3 to include fix for #75. ---- 0.10 ---- * Add support for using `Keyczar <http://www.keyczar.org/>`_ to encrypt keyrings. Keyczar is "an open source cryptographic toolkit designed to make it easier and safer for developers to use cryptography in their applications." * Added support for storing keyrings on Google Docs or any other filesystem supported by pyfilesystem. * Fixed issue in Gnome Keyring when unicode is passed as the service name, username, or password. * Tweaked SecretService code to pass unicode to DBus, as unicode is the preferred format. * Issue #71 - Fixed logic in CryptedFileKeyring. * Unencrypted keyring file will be saved with user read/write (and not group or world read/write). ----- 0.9.3 ----- * Ensure migration is run when get_password is called. Fixes #75. Thanks to Marc Deslauriers for reporting the bug and supplying the patch. ----- 0.9.2 ----- * Keyring 0.9.1 introduced a whole different storage format for the CryptedFileKeyring, but this introduced some potential compatibility issues. This release incorporates the security updates but reverts to the INI file format for storage, only encrypting the passwords and leaving the service and usernames in plaintext. Subsequent releases may incorporate a new keyring to implement a whole-file encrypted version. Fixes #64. * The CryptedFileKeyring now requires simplejson for Python 2.5 clients. ----- 0.9.1 ----- * Fix for issue where SecretServiceBackend.set_password would raise a UnicodeError on Python 3 or when a unicode password was provided on Python 2. * CryptedFileKeyring now uses PBKDF2 to derive the key from the user's password and a random hash. The IV is chosen randomly as well. All the stored passwords are encrypted at once. Any keyrings using the old format will be automatically converted to the new format (but will no longer be compatible with 0.9 and earlier). The user's password is no longer limited to 32 characters. PyCrypto 2.5 or greater is now required for this keyring. --- 0.9 --- * Add support for GTK 3 and secret service D-Bus. Fixes #52. * Issue #60 - Use correct method for decoding. ----- 0.8.1 ----- * Fix regression in keyring lib on Windows XP where the LOCALAPPDATA environment variable is not present. --- 0.8 --- * Mac OS X keyring backend now uses subprocess calls to the `security` command instead of calling the API, which with the latest updates, no longer allows Python to invoke from a virtualenv. Fixes issue #13. * When using file-based storage, the keyring files are no longer stored in the user's home directory, but are instead stored in platform-friendly locations (`%localappdata%\Python Keyring` on Windows and according to the freedesktop.org Base Dir Specification (`$XDG_DATA_HOME/python_keyring` or `$HOME/.local/share/python_keyring`) on other operating systems). This fixes #21. *Backward Compatibility Notice* Due to the new storage location for file-based keyrings, keyring 0.8 supports backward compatibility by automatically moving the password files to the updated location. In general, users can upgrade to 0.8 and continue to operate normally. Any applications that customize the storage location or make assumptions about the storage location will need to take this change into consideration. Additionally, after upgrading to 0.8, it is not possible to downgrade to 0.7 without manually moving configuration files. In 1.0, the backward compatibilty will be removed. ----- 0.7.1 ----- * Removed non-ASCII characters from README and CHANGES docs (required by distutils if we're to include them in the long_description). Fixes #55. --- 0.7 --- * Python 3 is now supported. All tests now pass under Python 3.2 on Windows and Linux (although Linux backend support is limited). Fixes #28. * Extension modules on Mac and Windows replaced by pure-Python ctypes implementations. Thanks to Jerome Laheurte. * WinVaultKeyring now supports multiple passwords for the same service. Fixes #47. * Most of the tests don't require user interaction anymore. * Entries stored in Gnome Keyring appears now with a meaningful name if you try to browser your keyring (for ex. with Seahorse) * Tests from Gnome Keyring no longer pollute the user own keyring. * `keyring.util.escape` now accepts only unicode strings. Don't try to encode strings passed to it. ----- 0.6.2 ----- * fix compiling on OSX with XCode 4.0 ----- 0.6.1 ----- * Gnome keyring should not be used if there is no DISPLAY or if the dbus is not around (https://bugs.launchpad.net/launchpadlib/+bug/752282). --- 0.6 --- * Added `keyring.http` for facilitating HTTP Auth using keyring. * Add a utility to access the keyring from the command line.
|
Erroneous Github auto-close. |
jperkin
pushed a commit
that referenced
this issue
Jun 2, 2014
2014-04-18 k <andk@cpan.org> * release 2.05 * amendments to the Changes file only, no code change: the github issue numbers were confused in the TRIAL releases. Thanks to Steve Hay for spotting. 2014-04-04 k <andk@cpan.org> * release 2.05-TRIAL2 * doc improvement for scan_cache/atstart (Slaven Rezic) * test improvement in 31session to fix false positives 2014-03-31 k <andk@cpan.org> * release 2.05-TRIAL * take github #68 as 086c901: smoke faster (Alexandr Ciornii) * take github #67 as cfa93ad, to fix github #64: local::lib shell variable string output (David Golden) * take github #66 as 4c0da4e, to fix github #65: loop with "notest test some-module-with-dependencies" (Andreas Koenig, David Golden) 2014-03-18 Andreas Koenig <k@UX31A> * release 2.04-TRIAL * history of master branch was rewritten after Tour de France bughunting (Lyon #QA2014); apologies to all repository followers: the real history, as it actually went, is not worth being recorded in the master branch. * address #91706 and #86915: the 'force install' bug and the endless loop bugs reported in the two tickets are fixed (joined forces) * new configure option 'use_prompt_default' (David Golden) * add new dummy distros OptionalPrereq and CircularPrereq for testing recommends/suggests support * experimental recommends/suggests support (David Golden, Andreas Koenig) * enable hiding of directories in the distroprefs tree (suggested by Slaven Rezić) 2013-09-15 k <andk@cpan.org> * release 2.03-TRIAL * load META.yml not META.json (Tatsuhiko Miyagawa) * support numerics in cpan IDs (Tatsuhiko Miyagawa) * address #88565: fix unreachable core bug (Father Chrysostomos, David Golden, bb225be54aff753058e149c95ac3047f54892746) * address #76831: spaces on Win32 combined with make_install_make_command (Reini Urban, Steve Hay) * address #86405, #86406: fix typos, clarify comments (found by David Steinbrunner) * address #86915: upgrade build method from "make" to "test" on dependencies declared as build_requires (Andreas Koenig, fa1d3087d5246a08741c944768a9732c35c944af) 2013-06-23 Andreas Koenig <k@UX31A> * release 2.02-TRIAL * the production of META.json was missing in 2.01 2013-06-22 Andreas Koenig <k@UX31A> * release 2.01-TRIAL * add binmode in two places in CPAN::Tarzip (Dave Saville via RT #86328) * make distroprefs tolerant against missing prefs dir (akoenig) * regain 5.6.2 compatibility (akoenig) * add PAUSE key up to 2015 (akoenig) 2013-06-18 Andreas Koenig <k@UX31A> * Use CPAN::Mirrors correctly (brian d foy) * Add default_mirror(), clean up docs a bit (brian d foy) * allow subdirectories in distroprefs (Alexandr Ciornii) * www.cpan.org is now the default CPAN mirror (David Golden) * Adds recommends_policy and suggests_policy to support recommended and suggested prerequisites (David Golden; incomplete because partially reverted) * Adds recommends_policy and suggests_policy to support (David Golden; incomplete because partially reverted) * Fix various prerequisite resolution bugs (David Golden) * Internal: Split 'make' method into 'prepare' and 'make' methods (Matt S. Trout and David Golden) * Internal: Refactor get/prepare/make/test/install shortcut logic and return values (David Golden)
jperkin
pushed a commit
that referenced
this issue
Aug 12, 2014
2014-07-02 version 0.5.9: * Support std::tr1 unordered containers by default (#51, #63, #68, #69) * Remove some warnings (#56) * Fix segmentation fault after malloc failures (#58, #59) * Fix alloc/dealloc mismatch (#52, #61) * Fix sample codes (#60, #64) * Support implicit conversion from integer to float/double (#54) * Improve documents (#45, #75, #82, #83) * Support CMake (#20, #87) * Remove Ruby dependencies in bootstrap (#86, #87) * Add FILE* buffer (#40) * Other bug fixes and refactoring: #39, #73, #77, #79, #80, #81, #84, #90
jperkin
pushed a commit
that referenced
this issue
Aug 12, 2014
This release includes the following changes: - Github issue #49 - Github issue #64 - skip meaningless chunk of 4 zero bytes between two otherwise-valid BIFF records - Github issue #61 - fix updating of escapement attribute of Font objects read from workbooks. - Implemented Sheet.visibility for xlsx files - Ignore anchors ($) in cell references - Dropped support for Python 2.5 and earlier, Python 2.6 is now the earliest Python release supported - Read xlsx merged cell elements. - Read cell comments in .xlsx files - Added xldate_to_datetime() function to convert from Excel serial date/time to datetime.datetime object.
jperkin
pushed a commit
that referenced
this issue
Apr 16, 2015
--------------
Changes in Devel::NYTProf 6.01 - 4th April 2015
Changed the clock used on Windows to high resolution QueryPerformanceCounter
which makes NYTProf useful on windows, at last, thanks to bulk88, #68
Fallback to checking PATH for nytprof scripts, #61 thanks to calid
Fix unused variable warnings thanks to zefram, RT#103107
Fix handling of PERL_DISABLE_PMC, thanks to bulk88, #67
Use larger buffer size when writing the data file, thanks to bulk88 #69
Clarified the docs re DB:: functions, #63 thanks to dbooth-boston
Documentation cleanup thanks to wollmers, #64
Clarify reason for loading Devel::NYTProf as early as possible.
Clarification of the RUN-TIME CONTROL OF PROFILING docs
jperkin
pushed a commit
that referenced
this issue
Apr 28, 2015
+ Version 2.12 (21.04.2015)
- This is a fix release for 2.11; the memory optimization with __slots__ on
Coord and AST nodes didn't take weakrefs into account, which broke cffi and
its many dependents (iseue #76). Fixed by adding __weakref__ to __slots__.
+ Version 2.11 (21.04.2015)
- Add support for C99 6.5.3.7 p7 - qualifiers within array dimensions in
function declarations. Started with issue #21 (reported with initial patch
by Robin Martinjak).
- Issue #27: bug in handling of unified wstring literals.
- Issue #28: fix coord reporting for 'for' loops.
- Added ``examples/using_gcc_E_libc.py`` to demonstrate how ``gcc -E`` can
be used instead of ``cpp`` for preprocessing.
- Pull request #64: support keywords like const, volatile, restrict and static
in dimensions in array declarations.
- Reduce memory usage of AST nodes (issue #72).
- Parsing order of nested pointer declarations fixed (issue #68).
jperkin
pushed a commit
that referenced
this issue
Jun 1, 2015
Upstream changes: version 3.27 (2015-05-05) [ENHANCEMENTS] * Cisco Aironet PSU information * Only log adding mibdirs at debug level 2 [BUG FIXES] * [#221] Drop Cisco Voice VLAN 4096 version 3.26 (2015-03-07) [ENHANCEMENTS] * Add fan and psu reporting to Layer3::Dell * Include Voice VLANs in (tagged) VLAN Membership on Cisco devices [BUG FIXES] * Fix typo in MRO::print_superclasses version 3.25 (2015-02-25) [ENHANCEMENTS] * Add new model name mappings for to Layer2::HP version 3.24 (2015-02-04) [ENHANCEMENTS] * Support RSTP and ieee8021d STP operating modes in RapidCity [BUG FIXES] * Fix single instance leafs defined in %FUNCS to behave like table leafs * Fix incorrect FDB ID to VLAN ID mapping in Bridge and L3:Enterasys version 3.23 (2014-12-09) [ENHANCEMENTS] * Update MIB used in L1::Asante * Enhanced STP support for L3::Extreme [BUG FIXES] * Fix Cisco VLAN membership issue introduced in 3.22 related to capturing port VLANs on Cisco interfaces which are configured for trunking but are not in operational trunking mode version 3.22 (2014-12-02) [NEW FEATURES] * Support obtaining FDB in Avaya SPBM edge deployments in L2::Baystack NOTE: This requires a RAPID-CITY MIB with the rcBridgeSpbmMacTable * Support for Fortinet devices in new class L3::Fortinet [ENHANCEMENTS] * Include LLDP support in base Layer2 and Layer3 classes. Due to the widespread adoption of LLDP, this should improve mapping networks when devices aren't supported in a more specific class. * No longer ignore interfaces based on name, in base L2/L3/L7 device classes. For several device classes SNMP::Info will now return tunnel interfaces and/or loopbacks, if present. * Use dot1qVlanCurrentTable if available to capture dynamic and static VLANs, fall back to dot1qVlanStaticTable if not available. * New method i_vlan_membership_untagged() for VLANs transmitted as untagged frames. * Capture Aruba AP hardware and software version when available * New STP methods to support gathering information from devices running mutiple STP instances such as PVST and MST * Enhanced STP support for Avaya and Foundry classes [BUG FIXES] * [#64] Misdetection: Wireless APs, add products MIB to L2::3Com * Use FDB ID to VID mapping if available to determine end station VLAN rather than assuming they are the same. * Capture port VLANs on Cisco interfaces which are configured for trunking but are not in operational trunking mode * Correct munging of stp_p_port(), i_stp_port(), and stp_root() methods in Bridge * In LLDP.pm don't create a variable in a conditional version 3.20 (2014-09-08) [NEW FEATURES] * Override layers in Juniper for routers with switch modules [BUG FIXES] * Update MANIFEST to include Ubiquiti files version 3.19 (2014-08-01) [NEW FEATURES] * Support for Ubiquiti Access Points in new class L2::Ubiquiti (begemot) * Preliminary support for 3Com switches in new class L2::3Com (begemot) [BUG FIXES] * Fix Avaya detection lldp_port() * Silence uninitialized value warning in L3::Cisco * H3C fixes (begemot) * Only use L2::ZyXEL_DSLAM for ZyXEL DSL modules version 3.18 (2014-07-02) [ENHANCEMENTS] * Pseudo ENTITY-MIB methods added to L3::Tasman for hardware information * Capture VPC Keepalive IP addresses in L3::Nexus (jeroenvi) * L2::Netgear inheritance clean up and removal of unnecessary c_* methods defined in Info base class [BUG FIXES] * Correctly identify device type (class) for instantiated objects which have overridden layers. * [#58] Fix inheritance in L3::FWSM and L3::CiscoASA * [#71] Don't try to match on a false port description in lldp_if * [#54] Possible bad values returned for cdp_id and lldp_port with some HP gear (Joel Leonhardt) version 3.17 (2014-06-23) [ENHANCEMENTS] * POD tests are not required for distribution. version 3.16 (2014-06-23) [ENHANCEMENTS] * Add method resolution discovery in SNMP::Info::MRO helper module * Consolidate CiscoImage class into CiscoStats class * Clean up inheritance for Cisco classes. With this change all applicable classes now inherit CiscoAgg, CiscoStpExtensions, CiscoPortSecurity, CiscoPower, and LLDP classes. * Remove inheritance of classes the devices do not support in L3::FWSM and L3::CiscoASA [BUG FIXES] * Use CiscoVTP methods to get interface VLAN in L3::Cisco rather than solely relying on the interface description. version 3.15 (2014-07-10) [NEW FEATURES] * Offline mode and Cache export/priming. [ENHANCEMENTS] * Return serial number for Cisco 3850 from entPhysicalSerialNum [BUG FIXES] * Cisco SB serial number probably did not work version 3.14 (2014-06-07) [ENHANCEMENTS] * Improvements to Mikrotik module (Alex Z) * Don't unshift length from broken lldpRemManAddrTable implementations (G. Shtern) * 802.3ad LAG support in Layer3::H3C * Add LLDP capabilities to Layer2::HPVC class [BUG FIXES] * Return correct VLAN info with qb_fw_table() on Layer2::HP version 3.13 (2014-03-27) [ENHANCEMENTS] * Cisco PAgP support added to LAG method * HP ProCurve LAG support by inheriting Info::Aggregate class version 3.12 (2014-02-10) [ENHANCEMENTS] * Modify L3::Passport to obtain forwarding table information from RAPID-CITY if information is not available in either Q-BRIDGE-MIB or BRIDGE-MIB. Needed for VSP 9000 prior to version 4.x (Tobias Gerlach) [BUG FIXES] * [#52] NETSCREEN-IP-ARP-MIB considered harmful * Foundry/Brocade aggreate port master ifIndex resolved properly version 3.11 (2014-01-26) [NEW FEATURES] * [#31] port-channel (aggregate) support. Aggregate support added in new agg_ports() method. Inital support added for Arista (ifStack), Avaya (MLT), Brocade (MST), and Cisco (802.3ad). [ENHANCEMENTS] * Use Q-BRIDGE-MIB as default with fallback to BRIDGE-MIB across all classes for the fw_mac, fw_port, and fw_status methods * Additional support for Avaya 8800 series in L3::Passport [BUG FIXES] * Modify cdp_cap() to handle devices which return space delimited strings for cdpCacheCapabilities rather than hex strings * [#51] Netdisco shows broken topology for devices with no alias entry for primary IP - Collect nsIfMngIp when getting IP interfaces in L3::Netscreen * Fix Extreme XOS i_vlan_membership - Revert [28bbe0], fix bug with untagged being added to @ret twice (Robert Kerr) * Skip default CPU management addresses on VSP and 8800/8600 series in L3::Passport to prevent erroneous duplicate addresses version 3.10 (2013-12-16) [BUG FIXES] * Data values of zero are now sent to munge method instead of skipped version 3.09 (2013-12-15) [NEW FEATURES] * [#45] IBM (Blade Network Technologies) Rackswitch support in new class L3::IBMGbTor * [] set_i_untagged combines both set_i_vlan and set_i_pvid in one method * [#41] Riverbed Steelhead support added in new class L3::Steelhead * New c_cap(), cdp_cap(), and lldp_cap() methods which return a hash of arrays with each array containing the system capabilities reported as supported by the remote system via CDP or LLDP. [ENHANCEMENTS] * Remove "Switch" from model name in L3::Foundry * [#49] IOS-XR support, add identification of IOS XR and version in CiscoStats * Aruba POE Support * Aruba utilizes Q-BRIDGE-MIB when available for VLAN information to better support wired switches * Add lldp_platform() method which uses lldp_rem_sysdesc() or lldp_rem_sysname() to provide a clue to type of remote LLDP capable device. * [RT#78232] Extend cdpCacheCapabilities to show more CDP bits [BUG FIXES] * Modify _xos_i_vlan_membership() in L3::Extreme to only include tagged ports * When determining the BSSID in Airespace there is only one hexadecimal digit available so skip if outside the range of 1-16, 17 is reserved for 3rd party AP's * Don't assume entity index 1 is the chassis and has serial in Layer3 * Capture serial number on newer Aruba devices * munge_bits() correctly unpacks BITS * Fix for single instance table leafs in test_class_mocked.pl * Fix power module indexing version 3.08 (2013-10-22) [ENHANCEMENTS] * Rewrite of L3::Aruba, now supports pseudo ENTITY-MIB methods to gather module information, more interface information for APs, more wireless information to include client stats, and arpnip information from wireless clients. WARNING: AP device interfaces are now based on AP MAC and radio versus BSSID to align with other wireless classes. * [#64] Add i_speed_admin() to L2::2900 (psychiatric) * [#66] Support for VSS via CISCO-VIRTUAL-SWITCH-MIB in L3::6500 * [#67] Add the possibility to set speed for Layer3::C4000 (psychiatric) * [#69] set speed and duplex on Cisco VSS system (psychiatric) * munge_null() now removes all non-printable control characters * Support Aironet standalone access points (Layer2::Aironet) running IOS15 * lldp_port() returns port ID instead of port description if the port ID subtype is "interface name". This improves the ability to correlate ports by name when a port description is also set. * Add docs note about make_snmpdata.pl under EXTENDING SNMP::Info * [#46] Brocade (Foundry) Module Support * Brocade (Foundry) POE Support * Support peth_port_power() power supplied by PoE ports in L2::Baystack * Update test_class.pl utility to allow ignore of snmp.conf and test summarize more standard class methods * On EOS, the LLDP port ID is a dot1d port * Use LLDP in Layer3::Aruba, for switches * Clean up more model names in L2::Baystack [BUG FIXES] * [#68] Fix device_port entries for switches with non-unique ifDesc (Nic Bernstein) * Don't try to munge undef values * [#49] Perl 5.18 UNIVERSAL::can change could cause infinite loop * Silence warning from uninitialized variable in L3::Passport e_descr() version 3.07 (2013-10-01) [ENHANCEMENTS] * Support for Pica8 switches in L3::Pica8 * Factor out cache/munge code from global/attr methods [BUG FIXES] * [#48] Switch duplicate J9624A for J9626A in Layer2/HP (R. Kerr) * Correct device serial number reporting for Nexus devices * Override ipAddrTable methods in L3::Nexus as some versions do not index the table with the IPv4 address in accordance with the MIB definition. version 3.05 (2013-08-16) [ENHANCEMENTS] * [#47] Add model info on HP 2530 and HP 2920 series * Add support for Cisco Small Business series Layer2/CiscoSB class * Add proper LLDP support to Netgear.pm * Change $netgear->interfaces() to use ifName rather than ifDescr as the former is unique per interface while the latter is not. If ifName is not present, concatenate ifDescr and ifIndex to achieve a unique value. * Properly report hardware version, Serial No. and OS Version for Netgear. version 3.03 (2013-07-11) [BUG FIXES] * Add missing =back to POD (A. Hartmaier) version 3.02 (2013-07-08) [ENHANCEMENTS] * Properly pull os_ver from Netgear GS series switches. * Support Alcatel devices with layer3 features. * Identify Cisco Aironet 1140 APs as Layer2::Aironet * LAN switch support added to Layer3::Aruba class * [RT#86725] - Identify Cisco Catalyst 3850 as Layer3::C6500 (C. Causer) version 3.01 (2013-04-13) [API Changes] * The methods c_ip(), c_if(), c_port(), c_id(), and c_platform() now represent common topology methods and will try to return a combined hash of data from all L2 topology protocols either running on the device or specified in the method call. The topology specific methods have been been prefixed with the protocol name in lowercase so that they can be called directly, sonmp_ip(), cdp_ip(), etc. * L2::Bay and L2::Foundry have been removed from the distribution. Both classes were depreciated and all functionality is available through L2::Baystack and L3::Foundry. [NEW FEATURES] * [3160037] - Support _raw suffix on methods to skip munging * [3185391] - Support for F5 devices in new class L3::F5 * [3323814] - Arp support for Netscreen (David Baldwin) * [3323821] - Support for Netscreen w/ WLAN (eg SSG5) (David Baldwin) * [3599277] - Q-BRIDGE Support to collect VLAN in macsuck * [3033731] - Alcatel-Lucent OmniSwich AMAP Support in new AMAP class * [3598896] - Lantronix device support (J R Binks) * [3598337] - Lantronix SLC support * Support for Cisco ASA in L3::CiscoASA (Kraus/Hartmaier/Bernstein) * Support for Avaya VSP 9000 series in L3::Passport * Support for Avaya VSP 7000 series in L2::Baystack * Support Avaya (Trapeze) Wireless Controllers in new class L2::NWSS2300 * Support Juniper (Trapeze) Wireless Controllers in new class L2::Trapeze * Support for newer Radware Alteon ADC switches 4408/4416/5412/5224 and older AWS 2000/3000 series in existing L3::AlteonAD * Support for H3C & HP A-series in new class L3::H3C * Support for Citrix Netscaler appliances in new class L7::Netscaler * New configuration option IgnoreNetSNMPConf will ignore Net-SNMP configuration files on object initialization * Two new utilities added in t/util to assist in developing device support; make_snmpdata.pl gathers SNMP data (snmpwalk) in a format that can be used with test_class_mocked.pl which mocks an SNMP agent to enable testing with no network access to a device. [ENHANCEMENTS] * UNIVERSAL::can() now works with dynamic methods * Dynamically generated methods are added to symbol table to avoid AUTOLOAD on subsequent calls * L2::Airespace now supports 802.11n client tx rates * L2::Airespace now reports AP Ethernet MAC as port MAC for radio ports * CiscoStats improvements to determine os versions, eg IOS XE ver on Sup7L-E * CiscoStats now reports 'ios-xe' if the device runs IOS XE (used to be 'ios') * Improved support of XOS based Extreme devices [BUG FIXES] * [3564920] - lldp_if gives wrong data for Enterasys version 2.11 (2012-12-09) [BUG FIXES] * Add fall-back for sysDescr on Force10 version 2.10 (2012-12-08) [NEW FEATURES] * Support for Force10 devices (W. Bulley)
jperkin
pushed a commit
that referenced
this issue
Jun 17, 2015
== 2.6.1 / 2015-05-25
* Bugs:
* Make columnar store handle all supported extensions, not just the first.
* Avoid circular require when using the columnar store.
== 2.6 / 2015-05-25
* New Feature:
* Columnar data storage for the MIME::Types registry, contributed by Jeremy
Evans (@jeremyevans). Reduces default memory use substantially (the mail
gem drops from 19 Mib to about 3 Mib). Resolves
{#96}[mime-types/ruby-mime-types#96],
{#94}[mime-types/ruby-mime-types#94],
{#83}[mime-types/ruby-mime-types#83]. Partially
addresses {#64}[mime-types/ruby-mime-types#64]
and {#62}[mime-types/ruby-mime-types#62].
* Development:
* Removed caching of deprecation messages in preparation for mime-types 3.0.
Now, deprecated methods will always warn their deprecation instead of only
warning once.
* Added a logger for deprecation messages.
* Renamed <tt>lib/mime.rb</tt> to <tt>lib/mime/deprecations.rb</tt> to not
conflict with the {mime}[https://rubygems.org/gems/mime] gem on behalf of
the maintainers of the {Praxis Framework}[http://praxis-framework.io/].
Provided by Josep M. Blanquer (@blanquer),
{#100}[mime-types/ruby-mime-types#100].
* Added the columnar data conversion tool, also provided by Jeremy Evans.
* Documentation:
* Improved documentation and ensured that all deprecated methods are marked
as such in the documentation.
* Development:
* Added more Ruby variants to Travis CI.
* Silenced deprecation messages for internal tools. Noisy deprecations are
noisy, but that's the point.
== 2.5 / 2015-04-25
* Bugs:
* David Genord (@albus522) fixed a bug in loading MIME::types cache where a
container loaded from cache did not have the expected +default_proc+,
{#86}[mime-types/ruby-mime-types#86].
* Richard Schneeman (@schneems) provided a patch that substantially reduces
unnecessary allocations.
* Documentation:
* Tibor Szolár (@flexik) fixed a typo in the README,
{#82}[mime-types/ruby-mime-types#82]
* Fixed {#80}[mime-types/ruby-mime-types#80],
clarifying the relationship of MIME::Type#content_type and
MIME::Type#simplified, with Ken Ip (@kenips).
* Development:
* Juanito Fatas (@JuanitoFatas) enabled container mode on Travis CI,
{#87}[mime-types/ruby-mime-types#87].
* Moved development to a mime-types organization under
{mime-types/ruby-mime-types}[https://github.com/mime-types/ruby-mime-types].
jperkin
pushed a commit
that referenced
this issue
Jun 17, 2015
Version 1.4.1 - 05 May 2015
* Fix for WAL archival stop working if first backup is EMPTY
(Closes: #64)
* Fix exception during error handling in Barman recovery (Closes:
#65)
* After a backup, limit cron activity to WAL archiving only
(Closes: #62)
* Improved robustness and error reporting of the backup delete
command (Closes: #63)
* Fix computation of WAL production ratio as reported in the
show-backup command
* Improved management of xlogb file, which is now correctly fsynced
when updated. Also, the rebuild-xlogdb command now operates on a
temporary new file, which overwrites the main one when finished.
* Add unit tests for dateutil module compatibility
* Modified Barman version following PEP 440 rules and added support
of tests in Python 3.4
jperkin
pushed a commit
that referenced
this issue
Jul 13, 2015
Update LICENSE HOMEPAGE and MASTER_SITES
Now it is python3 compatible
Complete test target
Upstream changes:
3.0.8 2015-06-23
[NEW] Added a monitoring guide to the documentation.
[FIX] Improved packaging (thanks to Larissa Reis).
[FIX] Fixed and improved various test cases.
3.0.7 2015-03-01
[FIX] State of resources and requests were inconsistent before the request has been processed (issue #62).
[FIX] Empty conditions were never triggered (regression in 3.0.6, issue #63).
[FIX] Environment.run() will fail if the until event does not get triggered (issue #64).
[FIX] Callback modification during event processing is now prohibited (thanks to Andreas Beham).
3.0.6 - 2015-01-30
[NEW] Guide to SimPy resources.
[CHANGE] Improve performance of condition events.
[CHANGE] Improve performance of filter store (thanks to Christoph Körner).
[CHANGE] Exception tracebacks are now more compact.
[FIX] AllOf conditions handle already processed events correctly (issue #52).
[FIX] Add sync() to RealtimeEnvironment to reset its internal wall-clock reference time (issue #42).
[FIX] Only send copies of exceptions into processes to prevent traceback modifications.
[FIX] Documentation improvements.
3.0.5 2014-05-14
[CHANGE] Move interruption and all of the safety checks into a new event (pull request #30)
[FIX] FilterStore.get() now behaves correctly (issue #49).
[FIX] Documentation improvements.
3.0.4 2014-04-07
[NEW] Verified, that SimPy works on Python 3.4.
[NEW] Guide to SimPy events
[CHANGE] The result dictionary for condition events (AllOF / & and AnyOf / |) now is an OrderedDict sorted in the same way as the original events list.
[CHANGE] Condition events now also except processed events.
[FIX] Resource.request() directly after Resource.release() no longer successful. The process now has to wait as supposed to.
[FIX] Event.fail() now accept all exceptions derived from BaseException instead of only Exception.
3.0.3 2014-03-06
[NEW] Guide to SimPy basics.
[NEW] Guide to SimPy Environments.
[FIX] Timing problems with real time simulation on Windows (issue #46).
[FIX] Installation problems on Windows due to Unicode errors (issue #41).
[FIX] Minor documentation issues.
3.0.2 2013-10-24
[FIX] The default capacity for Container and FilterStore is now also inf.
3.0.1 2013-10-24
[FIX] Documentation and default parameters of Store didn’t match. Its default capacity is now inf.
3.0 2013-10-11
SimPy 3 has been completely rewritten from scratch. Our main goals were to simplify the API and code base as well as making SimPy more flexible and extensible. Some of the most important changes are:
Stronger focus on events. Processes yield event instances and are suspended until the event is triggered. An example for an event is a timeout (formerly known as hold), but even processes are now events, too (you can wait until a process terminates).
Events can be combined with & (and) and | (or) to create condition events.
Process can now be defined by any generator function. You don’t have to subclass Process anymore.
No more global simulation state. Every simulation stores its state in an environment which is comparable to the old Simulation class.
Improved resource system with newly added resource types.
Removed plotting and GUI capabilities. Pyside and matplotlib are much better with this.
Greatly improved test suite. Its cleaner, and the tests are shorter and more numerous.
Completely overhauled documentation.
jperkin
pushed a commit
that referenced
this issue
Oct 16, 2015
1.10.0 ------ - Issue #122: Improve the performance of `six.int2byte` on Python 3. - Pull request #55 and issue #99: Don't add the `winreg` module to `six.moves` on non-Windows platforms. - Pull request #60 and issue #108: Add `six.moves.getcwd` and `six.moves.getcwdu`. - Pull request #64: Add `create_unbound_method` to create unbound methods.
jperkin
pushed a commit
that referenced
this issue
Oct 29, 2015
v1.3.0 ====== * Added `ffi.memmove()`_. * Pull request #64: out-of-line API mode: we can now declare floating-point types with ``typedef float... foo_t;``. This only works if ``foo_t`` is a float or a double, not ``long double``. * Issue #217: fix possible unaligned pointer manipulation, which crashes on some architectures (64-bit, non-x86). * Issues #64 and #126: when using ``set_source()`` or ``verify()``, the ``const`` and ``restrict`` keywords are copied from the cdef to the generated C code; this fixes warnings by the C compiler. It also fixes corner cases like ``typedef const int T; T a;`` which would previously not consider ``a`` as a constant. (The cdata objects themselves are never ``const``.) * Win32: support for ``__stdcall``. For callbacks and function pointers; regular C functions still don't need to have their `calling convention`_ declared. * Windows: CPython 2.7 distutils doesn't work with Microsoft's official Visual Studio for Python, and I'm told this is `not a bug`__. For ffi.compile(), we `removed a workaround`__ that was inside cffi but which had unwanted side-effects. Try saying ``import setuptools`` first, which patches distutils... .. _`ffi.memmove()`: using.html#memmove .. __: https://bugs.python.org/issue23246 .. __: https://bitbucket.org/cffi/cffi/pull-requests/65/remove-_hack_at_distutils-which-imports/diff .. _`calling convention`: using.html#windows-calling-conventions
jperkin
pushed a commit
that referenced
this issue
Dec 14, 2015
Pkgsrc changes:
- use ${PREFIX} for icon path in example.jwmrc
- rename patch files per new format
- add patch comments
- take maintainership
Upstream changes list from
http://joewing.net/projects/jwm/release-2.3.shtml
JWM v2.3 Release Notes
This is a collection of major changes between JWM v2.2 and JWM v2.3.
Version 2.3.0 was released 20150618.
You can download the latest snapshot of JWM here: jwm-1356.tar.xz.
New Features
* Added support for client requested XRaiseWindow (issue #117).
* Added native language support for the confirm dialog.
* Added support for _NET_RESTACK_WINDOW (issue #118).
* Added key binding to send the current window to a different desktop (issue
#119).
* Support the specification of an alternate configuration file (patch from
Brian Bidulock)
* Added Corner option to configure the roundedness of windows.
* Updated the look of borders around menus and trays.
* Add support for _NET_WM_MOVERESIZE (issue #142).
* Add the fullscreen group option (patch from George Shaw).
* Made window style configuration more consistent (may break old
configuration files).
* Add scale background type.
* Added group options: nomin, nomax, noclose, nomove, noresize (issue #152),
and nofullscreen (issue #163).
* Added the Outline tag to MenuStyle to specify the color of menu outlines
(issue #31).
* Added the Outline tag to TrayStyle to specify the color of tray outlines.
* To conform with GNU standards, running "make install" no longer strips the
executable. To strip the executable, "make install?strip" can be used
instead.
* Added the ability to swallow the same client into a tray multiple times.
* Added the ability to specify where the tray is hidden when auto-hide is
enabled (issue #34).
* Menu Includes are now loaded dynamically when a menu is shown rather than
when JWM starts.
* Added the sendu, sendd, sendl and sendr key bindings to send a window to a
different desktop (issue #119).
* Added the maxh, maxv, maxtop, maxbottom, maxleft and maxright key bindings
(issues #120 and #157).
* Added the ability to have separate actions per mouse button for tray
buttons (issue #171). This is accomplished using the Button tag. For
example:
<TrayButton label="My Button">
<Button mask="1">
exec:program_for_left_click
</Button>
<Button mask="45">
exec:program_for_scroll_wheel
</Button>
</TrayButton>
The Button tags are optional. By default the action will use mouse button
mask 123.
* Add the ability to have separate actions per mouse button for clock tray
components (issue #171) and the ability to have clock tray components run
actions like tray buttons (issue #172).
* Add support for more than 10 menus. Now 26 additional menus can be defined
using the letters a through z.
Configuration Changes
The following XSLT is available to update JWM v2.2 configuration files for use
with JWM v2.3: jwm-2.3.xslt.
To convert an existing v2.2 configuration file using xsltproc, run:
cp ~/.jwmrc ~/.jwmrc.old
xsltproc jwm-2.3.xslt ~/.jwmrc.old > ~/.jwmrc
If you have multiple configuration files, it may be necessary to apply the XSLT
to some or all of them depending on what configuration options are stored in
the file.
A summary of configuration changes follows.
* The ActiveBackground and ActiveForeground tags have been replaced by
Background and Foreground under the Active tag. This applies to TrayStyle,
TaskListStyle, TrayButtonStyle, PagerStyle, and MenuStyle.
* The Inactive tag under WindowStyle has been removed. The tags that used to
go within this tag now go directly under the WindowStyle tag.
* The autohide attribute in Tray now determines where the tray should be
hidden (left, right, top, bottom, or off) instead of true or false.
* Now actions in the Clock tag must be prefixed with exec: to run an external
program.
See the configuration documentation for documentation on all configuration
options.
Bug Fixes
* ICCCM 2.0 WM_S selection compliance (patch from Brian Bidulock).
* Fixed client window position after maximize/restore (issue #115, patch from
Biran Bidulock).
* Fixed window mapping bug with show desktop (issue #114).
* Give focus to the top-most window after show desktop (issue #64).
* Fix uninitialized memory when loading images (patch from Brian Bidulock).
* Fix overlapping string issue with FriBidi (patch from Brian Bidulock).
* Fixed non-UTF8 locales (issue #56).
* Fixed transparency issue with some applications (issue #130).
* Fixed focus after key events (patch from Brian Bidulock).
* Fixed loss of focus after restoring windows (issue #131).
* Fix setting of _NET_WM_STATE_HIDDEN when a window is minimized (issue #133,
patch from Brian Bidulock).
* Grab input focus at startup if not already set (issue #148).
Updated Translations
* Russian (Aleksandr Samusenko)
* French (Pierrick)
* Italian (Flavio aka Man from Mars)
* Spanish (Pablo Lezaeta)
Changes in 2.3.1 (20150628)
* Added an option to group windows by class in the task bar. (the group
attribute of the TrayStyle tag).
* Fixed an issue with menus showing up across monitors when Xinerama is
enabled.
* Added the ability to show Motif-style handles on windows (the decorations
attribute of WindowStyle).
* Fixed an issue where the next/prev key bindings would not advance past a
window that does not accept input focus.
* Fixed the behavior of the Include tag within menus so that it no longer
creates a submenu.
* Menus included using Include are no longer loaded each time the menu is
accessed.
* Added a Dynamic submenu that will re-load its menu contents each time it is
accessed.
Changes in 2.3.2 (20150913)
* Restored the ability to specifiy that windows should not have an icon
(using the "icon:" group option).
* JWM will now try several common extensions when loading icons.
* Fixed the height and default label for dynamic menus (issue #188).
* Improved handling of colormaps for pseudo-color displays.
* Fixed handling of WM_STATE on big-endian machines.
* Fixed an issue with menus getting stuck open.
* Removed the TaskListStyle, TrayButtonStyle, and ClockStyle configuration
options. These options are now set from TrayStyle.
* Added the Hungarian translation (from Hermit).
* Added the ability to give a 3D look to menus and trays by specifying
decorations="motif" in MenuStyle and TrayStyle respectively.
* Fixed an issue where JWM key bindings would not be available to
applications (issue #201).
* JWM now highlights the first menu item when opening a menu with the
keyboard (issue #102).
* Add the ability to selectively enable popups (issue #189).
* Various other fixes.
Changes in 2.3.3 (20151118)
* JWM windows now set _NET_WM_WINDOW_TYPE (issue #223).
* Added the Chinese translation (from Christopher Meng).
* Added the height attribute to TaskList (issue #227).
* Fixed tray button mouse bindings for the scroll wheel buttons (issue #229).
* Added the restore key binding (issue #233).
* Made middle-click on a task list item close the window (issue #232).
* Added support for tooltips in menus (issue #111).
* Added Portuguese (Brazil) translation (from Holmes).
* Fixed an issue where the dock would change size if its size was not
explicitly set (issue #238).
* Fixed the height calculation of vertical trays (issue #228).
Changes in 2.3.4 (20151122)
* Now a negative tray width/height can be specified to subtract from the
screen width/height (issue #250).
* Added the list configuration option to TrayStyle to allow displaying
windows from all desktops (all) or only the current desktop (the default,
desktop) in task lists.
* Improved scaling of JPEG and SVG images (issue #253).
* Fixed the rendering of fixed-aspect background images.
* Added the drag group option (issue #235).
* Fixed rendering of window borders without a title bar.
jperkin
pushed a commit
that referenced
this issue
Jan 19, 2016
Changes: Version 5.1.2 ============= Code Fixes ---------- * Code hardening using reallocarray() from OpenBSD. * Sanity check in giffilter catches files with malformed extension records Fixes SourceForge bug #63: malformed gif causes segfault in giffilter. * Inexpensive sanity check in DGifSlurp() catches malformed files with no image descriptor. Fixes SourceForge bug #64: malformed gif causes crash in giftool. * Fix SourceForge bug #66: GifDrawBoxedText8x8() modifying constant input parameter. * Bail out of GIF read on invalid pixel width. Addresses Savannah bug #67: invalid shift in dgif_lib.c * Fix SourceForge bug #69: #69 Malformed: Gif file with no extension block after a GRAPHICS_EXT_FUNC_CODE extension causes segfault (in giftext). * Fix SourceForge bug #71: Buffer overwrite when giffixing a malformed gif. * Fix SourceForge bug #73: Null pointer deference in gifclrmap (only reachable with malformed GIF). * Fix SourceForge bug #74: Double free in gifsponge under 5.1,1, for any valid gif image. * Fix SourceForge bug #75: GAGetArgs overflows due to uncounted use of va_arg. * Sanity check in giffix catches some malformed files. Addresses SourceForge bug #77: dgif_lib.c: extension processing error
jperkin
pushed a commit
that referenced
this issue
Aug 30, 2016
Add ALTERNATIVES file. v0.10.0: 2016.05.02 - New Action birthday: list birthdays, sorted by month and day - option -p, --pretty was renamed to -p, --parsable: So, the pretty formatted email or phone number table is the default now. Please adapt the configuration files of potential email and phone applications (e.g.: mutt email -p %s) v0.11.0: 2016.07.17 - Made khard python3 compatible (#59) - Enhanced read and write support for vcard versions 3.0 and 4.0 - user input parser: - Improved robustness and error handling - Fixed org attribute parsing (#57) - Support for private vcard extensions (#51) - New action birthdays (#64) - New options: --display to display contacts by first or last name (#66) --search-in-source-files to speed up program initialization (#75) --skip-unparsable to skip unparsable vcard files (#75) --strict-search to narrow the contact search to the name field - Added some aliases for program actions (#65) - Removed davcontroler module due to the python3 incompatibility (script moved into the misc folder) - Updated zsh completion function and khards example config file v0.11.1: 2016.07.31 - Workaround for the photo attribute parsing issue of vobject library 0.9.2 (#80) - setup.py: try to convert readme file into restructured text format (pypi requirement) and specify encoding explicitly (#83)
mamash
pushed a commit
that referenced
this issue
Oct 10, 2016
v1.3.0 ====== * Added `ffi.memmove()`_. * Pull request #64: out-of-line API mode: we can now declare floating-point types with ``typedef float... foo_t;``. This only works if ``foo_t`` is a float or a double, not ``long double``. * Issue #217: fix possible unaligned pointer manipulation, which crashes on some architectures (64-bit, non-x86). * Issues #64 and #126: when using ``set_source()`` or ``verify()``, the ``const`` and ``restrict`` keywords are copied from the cdef to the generated C code; this fixes warnings by the C compiler. It also fixes corner cases like ``typedef const int T; T a;`` which would previously not consider ``a`` as a constant. (The cdata objects themselves are never ``const``.) * Win32: support for ``__stdcall``. For callbacks and function pointers; regular C functions still don't need to have their `calling convention`_ declared. * Windows: CPython 2.7 distutils doesn't work with Microsoft's official Visual Studio for Python, and I'm told this is `not a bug`__. For ffi.compile(), we `removed a workaround`__ that was inside cffi but which had unwanted side-effects. Try saying ``import setuptools`` first, which patches distutils... .. _`ffi.memmove()`: using.html#memmove .. __: https://bugs.python.org/issue23246 .. __: https://bitbucket.org/cffi/cffi/pull-requests/65/remove-_hack_at_distutils-which-imports/diff .. _`calling convention`: using.html#windows-calling-conventions
jperkin
pushed a commit
that referenced
this issue
Oct 22, 2016
Based on a PR by Jussi Sallinen. 1.6.9 2016-01-11 - Fix a regression introduced in version 1.6.8, which caused GeoIP_database_info to erroneously return NULL. 1.6.8 2016-01-11 - Allow compilation on older systems by relaxing the autoconf and automake minimum versions. Thank you, Jose Rubio! - Avoid potential problems in multi-threaded environments by consistently using pread() rather than read(). - Fix various small issues reported by clang's static analyser. 1.6.7 2015-10-30 - Fixed a MSVC parser stack overflow when parsing `regionName.c` and `timeZone.c`. Fix by elliotlo. GitHub #64. - Updated region codes and timezones. - When using `GEOIP_MEMORY_CACHE` with an invalid database file, the search tree traversal could attempt to read memory outside of the memory allocated for the memory cache, resulting in a segmentation fault. A check was added to ensure that the traversal code does not try to read beyond the end of the file, whether in memory, memory mapped, or on disk. - Previously the return values from file reads were ignored. We now check these values to ensure that there were no errors. 1.6.6 2015-07-28 - Replaced usage of deprecated fileno, read, and lseek on Visual Studio 2005+ with their ISO C++ conformant replacements. - A warning about using a double as a float was fixed. - Fixed segfault when doing a lookup on an empty database. - Fixed a memcheck error from valgrind in the `_check_mtime` function. - Fixed `_check_mtime` to check the return value of `gettimeofday` rather than just assuming it worked. 1.6.5 2015-02-25 - A segmentation fault in `geoiplookup` was fixed when the utility was passed an invalid database. - Additional validation was added for validation of the size used in the creation of the index cache. - Changed the code to only look up country codes by using functions which ensure that we do not try to look past the end of an array. 1.6.4 2015-01-12 - Update Fips codes - Several issues with the MinGW build were fixed. - Use a constructor in pread.c to ensure the critical section is always initialized. - Added missing include of `io.h` on Windows. - Fixed `configure` warning that `'missing' script is too old or missing`. - Previously `nmake /f Makefile.vc clean` would fail on Windows. This was fixed. - Obsolete win32 and NetWare make files were removed. - Numerous documentation updates. 1.6.3 2014-10-29 - Added a GEOIP_SILENCE flag. Include this flag when calling GeoIP_open to prevent any messages from being written to stderr. - Mitigate a possible race condition when running under threads in the GeoIP_cleanup function. - Added some recommendations to the docs on using this library in a threaded application. - Fixed some bugs discovered by coverity, including failure to check some system call return values and making sure all strings are null-terminated. 1.6.2 2014-07-08 - Two files required for building on Win32 were missing from the 1.6.1 release. These files were added. There are no changes affecting other platforms. 1.6.1 2014-06-26 - Improve Win32 support - Update FIPS codes 1.6.0 2013-10-29 - Remove geoipupdate 1.5.2 2013-10-29 - Update region and time zones - Fix benchmark script - Remove autogenerated files ltmain.sh, man/geoip*.1 - Explain how to download free geolite databases in the README.md and GeoIP.conf.default - geoipupdate returns 1 on error 0 on success instead of the error code - README is replaced by README.md - Add support for OS X Mavericks 1.5.1 2013-05-14 - Update time_zone for Ontario, Canada - geoiplookup and geoiplookup6 exit code is 0 when user asked for help - Added -h option to geoiplookup6 - Do not load the database file if nodes and file size do not make sense. - Keep README and man pages in pure ascii. - It doesn't make sense to use GEOIP_INDEX_MODE with small databases like GEOIP_COUNTRY_EDITION. Instead of undefined behaviour we handle it silently as GEOIP_MEMORY_MODE - Update FIPS codes for Greece 1.5.0 2013-02-21 - Rename custom_directory to GeoIP_custom_directory. - Make sure the database match the requested type. This is helpful for Databases with the same default name and the general geoiplookup form (geoiplookup without a specific database) - apps/geoiplookup6.c use the ipnum instead of the hostname for lookups. - Use configure.ac instead of configure.in - Region lookup is a bit faster - Add pkg-config file - Updates required to build a Windows DLL under MinGW - Make API thread safe - geoiplookup's default charset is UTF8 -l change the charset back to iso8859-1 - geoipupdate skips \r otherwise it might be part of the last product_id - Update time zones - Update Region codes - Remove the unused CITYCONFIDENCE* database types - bootstrap rebuilds ltmain.sh - Update README.OSX for Lion - Change Macedonia to Macedonia, The Former Yugoslav Republic of - Add region_name to geoiplookup GEOIP_CITY_EDITION_REV1 - Add region_name to geoiplookup GEOIP_CITY_EDITION_REV0 - Add a --disable-data-files option. This allows you to build and install the library without having a data/GeoIP.dat file. This is useful when building the library from a checkout of the source tree, rather than a tarball - Add GEOIP_ACCURACYRADIUS_EDITION and GEOIP_ACCURACYRADIUS_EDITION_V6 - Add more database types GEOIP_COUNTRYCONF_EDITION, GEOIP_CITYCONF_EDITION, GEOIP_REGIONCONF_EDITION and GEOIP_POSTALCONF_EDITION - Fix default filenames for GEOIP_NETSPEED_EDITION_REV1 and GEOIP_NETSPEED_EDITION_REV1_V6
jperkin
pushed a commit
that referenced
this issue
Apr 18, 2017
v1.2.3 2017/3/25 * Reduce the number of String objects allocated when loading zoneinfo files. #54. * Make Timezone#friendly_identifier compatible with frozen string literals. * Improve the algorithm for deriving the utc_offset from zoneinfo files. This now correctly handles Pacific/Apia switching from one side of the International Date Line to the other whilst observing daylight savings time. #66. * Fix an UnknownTimezone exception when calling transitions_up_to or offsets_up_to on a TimezoneProxy instance obtained from Timezone.get_proxy. * Allow the Factory zone to be obtained from the Zoneinfo data source. * Ignore the /usr/share/zoneinfo/timeconfig symlink included in Slackware distributions. #64. * Fix Timezone#strftime handling of %Z expansion when %Z is prefixed with more than one percent. #31. * Support expansion of %z, %:z, %::z and %:::z to the UTC offset of the time zone in Timezone#strftime. #31 and #67.
jperkin
pushed a commit
that referenced
this issue
Jun 6, 2017
## Changes between 2.1.0 and 2.2.0 (unreleased) ### Timestamps are Encoded as 64-bit Unsigned Integers This is a potentially **breaking change**. It is recommended that all applications that use this gem and pass date/time values in message properties or headers are upgraded at the same time. GitHub issue: [#64](ruby-amqp/amq-protocol#64). Contributed by Carl Hoerberg.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add the autoserial patch like
http://wiki.powerdns.com/trac/attachment/ticket/301/pdns-2.9.22-soa-autoserial.diff
The text was updated successfully, but these errors were encountered: