forked from jsonn/pkgsrc
-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pkgin install mysql-server-5.5 before client will install incompatible mysql-client-5.6 #55
Comments
ghost
assigned mamash
May 21, 2013
I rebuilt the packages yesterday, fixing the loose dependency pattern. There's a new rebuild in progress right now that adds SMF support for mysql-server-5.6, too. |
mamash
pushed a commit
that referenced
this issue
Nov 27, 2013
--- 1.2 --- * Issue #26: Add support for SVN 1.7. Special thanks to Philip Thiem for the contribution. * Issue #94: Wheels are now distributed with every release. * Setuptools "natural" launcher support, introduced in 1.0, is now officially supported. ----- 1.1.7 ----- * Fixed behavior of NameError handling in 'script template (dev).py' (script launcher for 'develop' installs). * ``ez_setup.py`` now ensures partial downloads are cleaned up following a failed download. * Distribute #363 and Issue #55: Skip an sdist test that fails on locales other than UTF-8.
jperkin
pushed a commit
that referenced
this issue
Dec 9, 2013
libass (0.10.1) * Fix letter spacing * Add \rSTYLENAME syntax support (GC #43) * Fix border generation and border style reset (GC #56) * Fix various issues with bug-for-bug compatibility of transformations (\fax, \fay, etc.) to VSFilter (GC #46, GC #42) * Fix drawing parsing (GC #47) * Various fixes to shaper (GC #54, GC #55, GC#59) * Fix change detection * Add ass_set_line_position API to set a vertical subtitle offset * Fix scaling of drawing baseline offset (\pbo) values * Fix skipping of zero-width characters for FriBiDi shaper * Use LTR text base direction by default, similar to VSFilter libass (0.10.0) * Bidirectional layout and Arabic shaping via FriBidi (GC #13) * OpenType shaping via HarfBuzz-ng (GC #13) * Add API for shaper configuration * Add support for `Language' Script Info property, this can be used for hinting the text language * Vertical layout improvements * Use `vert' and `vkna' OpenType features for vertical glyph variants * Position rotated glyphs onto baseline * Parse font encoding property for base text direction hinting * Refactor cache system * Use generic outlines in place of FreeType glyphs * Direct outline bitmap rendering * Fix whitespace trimming (GC #35) * Do not render border if there's no shadow or glyph (GC #29) * Adjust spacing after a italic to non-italic style change (GC #37) * Fix fade timing * Fix x positioning with borders (GC #27) * Build system tweaks
jperkin
pushed a commit
that referenced
this issue
Dec 9, 2013
3.4 (2013-04-24) ---------------- - Switch to unicode internally. This should fix all en/decoding errors. [thet] - Support for non-ascii parameter values. Fixes #88. [warvariuc] - Added functions to transform chars in string with '\\' + any of r'\,;:' chars into '%{:02X}' form to avoid splitting on chars escaped with '\\'. [warvariuc] - Allow seconds in vUTCOffset properties. Fixes #55. [thet] - Let ``Component.decode`` better handle vRecur and vDDDLists properties. Fixes #70. [thet] - Don't let ``Component.add`` re-encode already encoded values. This simplifies the API, since there is no need explicitly pass ``encode=False``. Fixes #82. [thet] - Rename tzinfo_from_dt to tzid_from_dt, which is what it does. [thet] - More support for dateutil parsed tzinfo objects. Fixes #89. [leo-naeka] - Remove python-dateutil version fix at all. Current python-dateutil has Py3 and Py2 compatibility. [thet] - Declare the required python-dateutil dependency in setup.py. Fixes #90. [kleink] - Raise test coverage. [thet] - Remove interfaces module, as it is unused. [thet] - Remove ``test_doctests.py``, test suite already created properly in ``test_icalendar.py``. [rnix] - Transformed doctests into unittests, Test fixes and cleanup. [warvariuc]
jperkin
pushed a commit
that referenced
this issue
Dec 9, 2013
--- 1.2 --- * Issue #26: Add support for SVN 1.7. Special thanks to Philip Thiem for the contribution. * Issue #94: Wheels are now distributed with every release. * Setuptools "natural" launcher support, introduced in 1.0, is now officially supported. ----- 1.1.7 ----- * Fixed behavior of NameError handling in 'script template (dev).py' (script launcher for 'develop' installs). * ``ez_setup.py`` now ensures partial downloads are cleaned up following a failed download. * Distribute #363 and Issue #55: Skip an sdist test that fails on locales other than UTF-8.
jperkin
pushed a commit
that referenced
this issue
Jan 6, 2014
Incompatible Changes: * can no longer use both `\' and `:' (didn't work anyway) New Features: * Handling of run-time errors (default: die) is now overridable by subclasses via signature_error_handler(). [github #54] * Can now have aliased named parameters. [github #57] * remove dependency on Devel::BeginLift [github #39] * can now use `when' to specify default conditions [github #48] * can use `//=' as a shortcut for `when undef' [github #45] * can now provide `where' constraints in addition to (or instead of) a type [github #7] * can now use `...' to disable further argument checking [github #49] * can now specify more than one alternative in type unions [github #55] * can now nest parameterized types Bug Fixes: * Removed experimental smartmatch warnings * Don't require Data::Alias for named params unless you have to [github #71] * Fixed obscure bug where an eval in Method::Signatures wouldn't be skipped when carp'ing (i.e. in carp_location_for()) [github #72] * Data::Alias is only loaded when needed avoiding a threads + eval bug in most cases and improving compile time performance. [rt.cpan.org 82922, github #62] * Compile-time errors now reporting proper line numbers. [github #61] * Trailing commas on parameter lists are now ok. [rt.cpan.org 81364] * Default condition of `when {}' now interpreted as `when { $_ ~~ {} }' (avoids parse error). [github #60] Optimizations: * better signature parsing using PPI [github #11] Distribution Fixes: * Fixed failing test in 5.10.0 (uncovered by CPAN Testers) * Fixed repo link in metadata (thanks dsteinbrunner) [github #87] * Add M::S::Parameter to MANIFEST [github #76] * Change representation of Infinity to work on Win32 [github #75] * Fixed stray detritus in MANIFEST. * Somehow my last-minute fix to the new error handler test didn't make it in; this will fix "Can't locate Moose.pm" errors. * Fixed test failing on 5.10.0 as per github #59. * Fixed subtests failing on Test::More's prior to 0.96. Docs: * Updated close parend problem to include quotes and a workaround [rt.cpan.org 85925] * Fixed some typos (thanks dsteinbrunner) [github #88] * Found and fixed missing parend * Minor clarifications here and there. * Clarified what doesn't work in Perl 5.8. * Added Function::Parameters to See Also section. * Updated copyright. * documented all new features * new ASCI-art breakdown of signature syntax * minor tweaks and corrections Misc: * Rearranged so signature is now an object [github #30] * Add hook for Travis CI [github #78] * Failure to parse parameters will now produce a more useful error.
jperkin
pushed a commit
that referenced
this issue
Jan 21, 2014
--- 1.2 --- * Issue #26: Add support for SVN 1.7. Special thanks to Philip Thiem for the contribution. * Issue #94: Wheels are now distributed with every release. * Setuptools "natural" launcher support, introduced in 1.0, is now officially supported. ----- 1.1.7 ----- * Fixed behavior of NameError handling in 'script template (dev).py' (script launcher for 'develop' installs). * ``ez_setup.py`` now ensures partial downloads are cleaned up following a failed download. * Distribute #363 and Issue #55: Skip an sdist test that fails on locales other than UTF-8.
jperkin
pushed a commit
that referenced
this issue
Jan 21, 2014
Incompatible Changes: * can no longer use both `\' and `:' (didn't work anyway) New Features: * Handling of run-time errors (default: die) is now overridable by subclasses via signature_error_handler(). [github #54] * Can now have aliased named parameters. [github #57] * remove dependency on Devel::BeginLift [github #39] * can now use `when' to specify default conditions [github #48] * can use `//=' as a shortcut for `when undef' [github #45] * can now provide `where' constraints in addition to (or instead of) a type [github #7] * can now use `...' to disable further argument checking [github #49] * can now specify more than one alternative in type unions [github #55] * can now nest parameterized types Bug Fixes: * Removed experimental smartmatch warnings * Don't require Data::Alias for named params unless you have to [github #71] * Fixed obscure bug where an eval in Method::Signatures wouldn't be skipped when carp'ing (i.e. in carp_location_for()) [github #72] * Data::Alias is only loaded when needed avoiding a threads + eval bug in most cases and improving compile time performance. [rt.cpan.org 82922, github #62] * Compile-time errors now reporting proper line numbers. [github #61] * Trailing commas on parameter lists are now ok. [rt.cpan.org 81364] * Default condition of `when {}' now interpreted as `when { $_ ~~ {} }' (avoids parse error). [github #60] Optimizations: * better signature parsing using PPI [github #11] Distribution Fixes: * Fixed failing test in 5.10.0 (uncovered by CPAN Testers) * Fixed repo link in metadata (thanks dsteinbrunner) [github #87] * Add M::S::Parameter to MANIFEST [github #76] * Change representation of Infinity to work on Win32 [github #75] * Fixed stray detritus in MANIFEST. * Somehow my last-minute fix to the new error handler test didn't make it in; this will fix "Can't locate Moose.pm" errors. * Fixed test failing on 5.10.0 as per github #59. * Fixed subtests failing on Test::More's prior to 0.96. Docs: * Updated close parend problem to include quotes and a workaround [rt.cpan.org 85925] * Fixed some typos (thanks dsteinbrunner) [github #88] * Found and fixed missing parend * Minor clarifications here and there. * Clarified what doesn't work in Perl 5.8. * Added Function::Parameters to See Also section. * Updated copyright. * documented all new features * new ASCI-art breakdown of signature syntax * minor tweaks and corrections Misc: * Rearranged so signature is now an object [github #30] * Add hook for Travis CI [github #78] * Failure to parse parameters will now produce a more useful error.
jperkin
pushed a commit
that referenced
this issue
Jan 21, 2014
Changelog (from History.txt) === 1.0.6 2014-01-17 * rescue Launchy::CommandNotFoundError #56 === 1.0.5 2014-01-16 * use HTTPS for OAuth::Consumer #55 * thank you for contributing @ymrl === 1.0.4 2014-01-08 * update gem dependencies === 1.0.3 2014-01-08 * bugfix for rainbow 1.99.x #54 * use launchy gem to open OAuth-URL #53 === 1.0.2 2013-11-27 * fix syntax error on ruby1.8.7 === 1.0.1 2013-11-23 * bugfix -user:add #51 === 1.0.0 2013-11-21 * fix for twitter gem v5.0.0 #50
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
libass (0.10.1) * Fix letter spacing * Add \rSTYLENAME syntax support (GC #43) * Fix border generation and border style reset (GC #56) * Fix various issues with bug-for-bug compatibility of transformations (\fax, \fay, etc.) to VSFilter (GC #46, GC #42) * Fix drawing parsing (GC #47) * Various fixes to shaper (GC #54, GC #55, GC#59) * Fix change detection * Add ass_set_line_position API to set a vertical subtitle offset * Fix scaling of drawing baseline offset (\pbo) values * Fix skipping of zero-width characters for FriBiDi shaper * Use LTR text base direction by default, similar to VSFilter libass (0.10.0) * Bidirectional layout and Arabic shaping via FriBidi (GC #13) * OpenType shaping via HarfBuzz-ng (GC #13) * Add API for shaper configuration * Add support for `Language' Script Info property, this can be used for hinting the text language * Vertical layout improvements * Use `vert' and `vkna' OpenType features for vertical glyph variants * Position rotated glyphs onto baseline * Parse font encoding property for base text direction hinting * Refactor cache system * Use generic outlines in place of FreeType glyphs * Direct outline bitmap rendering * Fix whitespace trimming (GC #35) * Do not render border if there's no shadow or glyph (GC #29) * Adjust spacing after a italic to non-italic style change (GC #37) * Fix fade timing * Fix x positioning with borders (GC #27) * Build system tweaks
jperkin
pushed a commit
that referenced
this issue
Mar 14, 2014
3.4 (2013-04-24) ---------------- - Switch to unicode internally. This should fix all en/decoding errors. [thet] - Support for non-ascii parameter values. Fixes #88. [warvariuc] - Added functions to transform chars in string with '\\' + any of r'\,;:' chars into '%{:02X}' form to avoid splitting on chars escaped with '\\'. [warvariuc] - Allow seconds in vUTCOffset properties. Fixes #55. [thet] - Let ``Component.decode`` better handle vRecur and vDDDLists properties. Fixes #70. [thet] - Don't let ``Component.add`` re-encode already encoded values. This simplifies the API, since there is no need explicitly pass ``encode=False``. Fixes #82. [thet] - Rename tzinfo_from_dt to tzid_from_dt, which is what it does. [thet] - More support for dateutil parsed tzinfo objects. Fixes #89. [leo-naeka] - Remove python-dateutil version fix at all. Current python-dateutil has Py3 and Py2 compatibility. [thet] - Declare the required python-dateutil dependency in setup.py. Fixes #90. [kleink] - Raise test coverage. [thet] - Remove interfaces module, as it is unused. [thet] - Remove ``test_doctests.py``, test suite already created properly in ``test_icalendar.py``. [rnix] - Transformed doctests into unittests, Test fixes and cleanup. [warvariuc]
jperkin
pushed a commit
that referenced
this issue
Mar 14, 2014
--- 1.2 --- * Issue #26: Add support for SVN 1.7. Special thanks to Philip Thiem for the contribution. * Issue #94: Wheels are now distributed with every release. * Setuptools "natural" launcher support, introduced in 1.0, is now officially supported. ----- 1.1.7 ----- * Fixed behavior of NameError handling in 'script template (dev).py' (script launcher for 'develop' installs). * ``ez_setup.py`` now ensures partial downloads are cleaned up following a failed download. * Distribute #363 and Issue #55: Skip an sdist test that fails on locales other than UTF-8.
jperkin
pushed a commit
that referenced
this issue
Mar 14, 2014
Incompatible Changes: * can no longer use both `\' and `:' (didn't work anyway) New Features: * Handling of run-time errors (default: die) is now overridable by subclasses via signature_error_handler(). [github #54] * Can now have aliased named parameters. [github #57] * remove dependency on Devel::BeginLift [github #39] * can now use `when' to specify default conditions [github #48] * can use `//=' as a shortcut for `when undef' [github #45] * can now provide `where' constraints in addition to (or instead of) a type [github #7] * can now use `...' to disable further argument checking [github #49] * can now specify more than one alternative in type unions [github #55] * can now nest parameterized types Bug Fixes: * Removed experimental smartmatch warnings * Don't require Data::Alias for named params unless you have to [github #71] * Fixed obscure bug where an eval in Method::Signatures wouldn't be skipped when carp'ing (i.e. in carp_location_for()) [github #72] * Data::Alias is only loaded when needed avoiding a threads + eval bug in most cases and improving compile time performance. [rt.cpan.org 82922, github #62] * Compile-time errors now reporting proper line numbers. [github #61] * Trailing commas on parameter lists are now ok. [rt.cpan.org 81364] * Default condition of `when {}' now interpreted as `when { $_ ~~ {} }' (avoids parse error). [github #60] Optimizations: * better signature parsing using PPI [github #11] Distribution Fixes: * Fixed failing test in 5.10.0 (uncovered by CPAN Testers) * Fixed repo link in metadata (thanks dsteinbrunner) [github #87] * Add M::S::Parameter to MANIFEST [github #76] * Change representation of Infinity to work on Win32 [github #75] * Fixed stray detritus in MANIFEST. * Somehow my last-minute fix to the new error handler test didn't make it in; this will fix "Can't locate Moose.pm" errors. * Fixed test failing on 5.10.0 as per github #59. * Fixed subtests failing on Test::More's prior to 0.96. Docs: * Updated close parend problem to include quotes and a workaround [rt.cpan.org 85925] * Fixed some typos (thanks dsteinbrunner) [github #88] * Found and fixed missing parend * Minor clarifications here and there. * Clarified what doesn't work in Perl 5.8. * Added Function::Parameters to See Also section. * Updated copyright. * documented all new features * new ASCI-art breakdown of signature syntax * minor tweaks and corrections Misc: * Rearranged so signature is now an object [github #30] * Add hook for Travis CI [github #78] * Failure to parse parameters will now produce a more useful error.
jperkin
pushed a commit
that referenced
this issue
Mar 14, 2014
Changelog (from History.txt) === 1.0.6 2014-01-17 * rescue Launchy::CommandNotFoundError #56 === 1.0.5 2014-01-16 * use HTTPS for OAuth::Consumer #55 * thank you for contributing @ymrl === 1.0.4 2014-01-08 * update gem dependencies === 1.0.3 2014-01-08 * bugfix for rainbow 1.99.x #54 * use launchy gem to open OAuth-URL #53 === 1.0.2 2013-11-27 * fix syntax error on ruby1.8.7 === 1.0.1 2013-11-23 * bugfix -user:add #51 === 1.0.0 2013-11-21 * fix for twitter gem v5.0.0 #50
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
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.
jperkin
pushed a commit
that referenced
this issue
Apr 15, 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.
jperkin
pushed a commit
that referenced
this issue
Apr 15, 2014
Feature request #44: Allow override of the From: field on forensic reports. Feature request #45: Log the host portion of ignored Authentication-Results fields at "debug" level. Feature request #56: Add "RequiredHeaders" setting to enforce syntax checks against a message and reject those that don't comply. Feature request #65: Add "ForensicReportsBcc". Fix bug #46: Charitable tweak to a couple of log messages. Fix bug #55: The "SoftwareHeader" setting wasn't being set properly. Fix bug #58: The "smtp.mailfrom" part of an Authentication-Results field might contain only a domain name. Fix bug #60: Default AuthservID to the name provided by the MTA, not the local host name, which is consistent with what OpenDKIM does. Merge request #2: Validate external recipients before adding them to report recipient lists. Record all DKIM results to the history file, rather than only passing results. BUILD: Fix bug #50: Check libbsd for strlcat() and strlcpy() so we don't make our own when we don't need to. CONTRIB: Fix bug #52: Update path to draft RFC in contrib/spec. CONTRIB: Fix bug #59: Allow database name, userid and password to be specified on the command line rather than hard-coding them. DOCS: Fix bug #48: Add a libopendmarc use overview page. DOCS: Fix bug #53: Add man page for opendmarc-importstats. REPORTS: Fix bug #51: Check status after every phase of SMTP when sending reports. REPORTS: Fix DKIM status importing. LIBOPENDMARC: Fix bug #68: Fix strict/relaxed checking logic when a public suffix list is available. LIBOPENDMARC: Fixed a bug where in some instances the fetch of the orgainizational domain could wrongly return the from domain. LIBOPENDMARC: Fix call to missing function.
jperkin
pushed a commit
that referenced
this issue
May 19, 2014
Changes: 2014-05-03 David Schweikert <[email protected]> * Version 3.10 * Fix confusing error message with -g and IPv6 addresses (#58, reported by * Axel Beckert) * Allow option '-f' also for non-root (since setuid privileges are * dropped) * Do not retry twice DNS lookup on DNS lookup problem * Remove support for NIS groups * Better document -B backoff-factor and when it can be used (#33, Oleksiy * Zagorskyi) * More tests added 2014-03-08 David Schweikert <[email protected]> * Version 3.9 * Fix random output on socket error (reported by Aleksandrs Saveljevs, * #56) * Support ppc64le architecture by including alpha libtool version (reported by Amit Kumar Gupta and Aravinda B Thunug) * Fix compilation problem on FreeBSD (#57) * Initial test suite and continous intergration (with travis-ci.org / * coveralls.io) * Don't output usage information on error 2013-11-08 David Schweikert <[email protected]> * Version 3.8 * Fix segmentation fault introduced in version 3.7 with loop mode * (reported by Vlad Glagolev, #55) 2013-11-04 David Schweikert <[email protected]> * Version 3.7 * Allow running as non-root on Mac OS X by using non-privileged ICMP (#7) * Remove unnecessary IPv6 socket options * Fix again compatibility issue with FreeBSD (Shawn Chu) * Fix fping hanging forever on permanent sendto failure (Shawn Chu) * Fix duplicate echo reply packets causing early stop in count mode (reported by Ramon Schwammberger, #53) 2013-10-10 David Schweikert <[email protected]> * Version 3.6 * Fix loop issue after 65536 pings (reported by Peter Folk and GBert, #12) * Minimum ping data size is now 0 * Removed setsockopt IPV6_CHECKSUM, which shouldn't be set and breaks compiling on Solaris (reported by Juergen Arndt) * Fix wrong min RTT value with -Q option (reported by Alexander Ivanov, * #51) 2013-05-22 David Schweikert <[email protected]> * Version 3.5 * Fix sprint_tm buffer size crash (reported by Japheth Cleaver) * Addded -D flag to print timestamps (Toke Høiland-Jørgensen) * Fix fping6 build on OS X 10.8 (unknown contributor) * Fix compatibility issue with FreeBSD (Alexandre Raynaud, Jason Harris, * #39) * Fping.spec: fix setuid permissions and provides fping6 (Marcus Vinicius * Ferreira) * Re-create configure script with autoconf 2.69 for aarch64 support (Chuck * Anderson, #45) 2012-09-04 David Schweikert <[email protected]> * Version 3.4 * Revert "Output statistics to stdout instead of stderr", because it * breaks tools assuming the output goes to stderr 2012-08-19 David Schweikert <[email protected]> * Version 3.3 * Do not output icmp errors with -q (#1) * Add --enable-ipv4 and --enable-ipv6 options to configure (Niclas * Zeising) * Fix removing of unreachable hosts when doing loop (Thomas Liske, #13 * #23) * Fix -A for fping6 (reported by Matt LaPlante, #14) * Fix "options inet6" breaking IPv4 name resolution (reported by Matt * LaPlante, #17) * Output statistics to stdout instead of stderr (suggested by Simon * Leinen, #9) * Set default data size to 56 bytes on all architectures (#18) * Added contrib/fping.spec (Stephen Schaefer, #24) * Convert man-page source to POD for easier maintenance * Fix error message on DNS error for IPv6 hosts (#27) * Fix -n flag in fping6 (#28) * Man-page fix: TOS option typo (Thomas Liske, #23) * Man-page fix: inconsistency in regards to numeric arguments (Robert * Henney) * Man-page fix: better description of option -q (#15) 2012-05-29 David Schweikert <[email protected]> * Version 3.2 * Improve documentation for -g option (G.W. Haywood) * Performance optimization for big select timeouts (#10, Andrey * Bondarenko) * Fix restart of select call after interrupt signal (#8, Boian Bonev) * Fix infinite loop caused by linked list corruption (#11, Boian Bonev) 2012-04-26 David Schweikert <[email protected]> * Version 3.1 * -g option (generate): exclude network and broadcast address for cidr ranges (idea by Eric Brander) * do not explicitely check if running as root, to make it possible to install fping with linux capabilities instead of making it setuid (setcap cap_net_raw+ep fping) * ANSI C (C89) compiler now a requirement * Portability fixes * Reorganized source directory * Bugfix: fix timeout issue on Solaris (Sandor Geller) * Man-page fixes (Axel Beckert) * Added -H option to specify number of hops (Paul Duda) * Output usage information to stdout when called with -h (Paul Duda) 2011-12-28 David Schweikert <[email protected]> * Version 3.0 * rewritten main loop for improved performance * -T parameter (select timeout) now obsolete * Maintenance taken over from unresponsive previous maintainer (anybody please step up, if you disagree) * New homepage: www.fping.org 2009-12-21 Tobi Oetiker <[email protected]> * Version v2.4b2-to3-ipv6 * added -On option to set the TOS octet * Removed unused variables from code * updated to current autoconf standards * Merged Debian changes (see below) ---------------------------------------------------------------------- fping (2.4b2-to-ipv6-16.1) unstable; urgency=low * NMU during Moenchengladbach BSP * Fixes FTBFS on kfreebsd (Closes: #555398) * Fixes typo "Paramter" in binary -- Axel Beckert <[email protected]> Sat, 23 Jan 2010 16:22:02 +0100 fping (2.4b2-to-ipv6-16) unstable; urgency=low * Fix the following bugs - Network byte order sensitivity was missing completely. Added hopefully all missing calls. - The sequence numbering scheme used led to packet drops. Changed it to a more senseful numbering scheme. - Some minor C programming mistakes ('=' instead of '=='). Patch by Stephan Fuhrmann; closes: #502569 * Add support for command line select timeout setting Patch by Marton Balint; closes: #502575 * Remove symlinks in /usr/sbin; closes: #377732 * Standards-Version is 3.8.0 -- Anibal Monsalve Salazar <[email protected]> Sat, 18 Oct 2008 12:04:52 -- +1100 fping (2.4b2-to-ipv6-15) unstable; urgency=low * Added interface binding (-I) for fping Patch by Peter Naulls <[email protected]> Closes: #439014 * Fixed a couple of typos in fping.8. Closes: #423180 * Added homepage control header * Bumped Standards-Version to 3.7.3 * Fixed the following lintian issue: - debian-rules-sets-DH_COMPAT -- Anibal Monsalve Salazar <[email protected]> Mon, 03 Mar 2008 17:46:17 -- +1100 fping (2.4b2-to-ipv6-13) unstable; urgency=low * Fixed stdout flush problem, closes: #340146. Patch by Bart Martens <[email protected]>. -- Anibal Monsalve Salazar <[email protected]> Fri, 30 Dec 2005 08:30:09 -- +1100 fping (2.4b2-to-ipv6-12) unstable; urgency=low * Fixed "problem with option -r (retry limit)", closes: #318402. Patch by Qingning Huo <[email protected]>. -- Anibal Monsalve Salazar <[email protected]> Sat, 08 Oct 2005 21:26:35 -- +1000 fping (2.4b2-to-ipv6-11) unstable; urgency=low * Fixed "would be useful to specify 'source address' like ping for multi homed machines", closes: #198486. Patch by Marc Haber <[email protected]>. -- Anibal Monsalve Salazar <[email protected]> Thu, 02 Jun 2005 08:14:54 -- +1000 fping (2.4b2-to-ipv6-10) unstable; urgency=low * Fixed "unnecessary delay with the -c option after the last packet" (Closes: #293856). Patch by Niko Tyni <[email protected]> -- Anibal Monsalve Salazar <[email protected]> Sun, 06 Feb 2005 23:25:57 -- +1100 fping (2.4b2-to-ipv6-9) unstable; urgency=low * Fixed "fping6 always does reverse lookup" (Closes: #273647). Patch by Jeroen Massar and forwarded by Bernhard Schmidt <[email protected]> -- Anibal Monsalve Salazar <[email protected]> Mon, 10 Jan 2005 -- 00:01:32 +1100 fping (2.4b2-to-ipv6-7) unstable; urgency=low * Build fping in build/ipv[46] instead of build and build-ipv6. * Made DNS errors non-fatal for IPv6 (closes: #198056). -- Herbert Xu <[email protected]> Fri, 20 Jun 2003 21:36:30 +1000 fping (2.4b2-to-ipv6-6) unstable; urgency=low * Do not use incorrect linux.h file (closes: #85468). -- Herbert Xu <[email protected]> Sat, 17 May 2003 14:13:11 +1000 fping (2.4b2-to-ipv6-5) unstable; urgency=low * Fixed yet another divide by zero bug (closes: #148445). -- Herbert Xu <[email protected]> Tue, 4 Jun 2002 12:18:03 +1000 fping (2.4b2-to-ipv6-4) unstable; urgency=low * Made fping6 setuid (closes: #136386). * Moved fping back into bin. * Partially applied IPv6 patch to fix IPv6 checksums (closes: #136479). -- Herbert Xu <[email protected]> Sun, 7 Apr 2002 20:36:56 +1000 fping (2.4b2-to-ipv6-3) unstable; urgency=low * Added compatibility symlink for fping (closes: #135203). -- Herbert Xu <[email protected]> Sat, 23 Feb 2002 08:34:11 +1100 fping (2.4b2-to-ipv6-2) unstable; urgency=low * Fixed another divide by zero error (closes: #132370). -- Herbert Xu <[email protected]> Thu, 7 Feb 2002 20:10:48 +1100 fping (2.4b2-to-ipv6-1) unstable; urgency=low * New upstream release. * Install fping into sbin as done by upstream.
jperkin
pushed a commit
that referenced
this issue
May 19, 2014
2014-04-16 Release 6.06 Ville Skyttä (3): Merge pull request #44 from dsteinbrunner/master Spelling fixes. Merge pull request #55 from oalders/master Karen Etheridge (2): Merge pull request #38 from mbeijen/typo-sting Merge pull request #43 from dsteinbrunner/master David Steinbrunner (2): Spelling corrections Olaf Alders (1): Typo fixes. Steffen Ullrich (1): correct behavior for https_proxy, e.g. don't send plain https:// requests to proxy, but instead establish CONNECT tunnel and then send requests inside tunnel. This change does together with a change in LWP::Protocol::https. The change supports LWP::Protocol::https with the default IO::Socket::SSL backend, but also with Net::SSL. Also: - proxy authorization is supported (http://user:pass@host:port as proxy URL, Net::SSL still needs special HTTPS_PROXY_* environemt variables, as before) - CONNECT request does not need to be the first request inside the tunnel (not with Net::SSL) - conn_cache is read and written inside request(), instead of writing in request() and reading in _new_socket(). If a https tunnel is established the cache_key no longer depends only on proxy host,port but also on the tunnel endpoint - CONNECT is a proxy request and must always use Proxy-Authorization, not Authorization header turugina (1): fix: auth-header of Digest auth did not conform to RFC 2617 when WWW-Authenticate has 'qop' parameter. Gisle Aas (1): SSL libs might trigger ENOTTY on read Michiel Beijen (1): Small typo.
jperkin
pushed a commit
that referenced
this issue
Jun 2, 2014
Changes: 2014-05-03 David Schweikert <[email protected]> * Version 3.10 * Fix confusing error message with -g and IPv6 addresses (#58, reported by * Axel Beckert) * Allow option '-f' also for non-root (since setuid privileges are * dropped) * Do not retry twice DNS lookup on DNS lookup problem * Remove support for NIS groups * Better document -B backoff-factor and when it can be used (#33, Oleksiy * Zagorskyi) * More tests added 2014-03-08 David Schweikert <[email protected]> * Version 3.9 * Fix random output on socket error (reported by Aleksandrs Saveljevs, * #56) * Support ppc64le architecture by including alpha libtool version (reported by Amit Kumar Gupta and Aravinda B Thunug) * Fix compilation problem on FreeBSD (#57) * Initial test suite and continous intergration (with travis-ci.org / * coveralls.io) * Don't output usage information on error 2013-11-08 David Schweikert <[email protected]> * Version 3.8 * Fix segmentation fault introduced in version 3.7 with loop mode * (reported by Vlad Glagolev, #55) 2013-11-04 David Schweikert <[email protected]> * Version 3.7 * Allow running as non-root on Mac OS X by using non-privileged ICMP (#7) * Remove unnecessary IPv6 socket options * Fix again compatibility issue with FreeBSD (Shawn Chu) * Fix fping hanging forever on permanent sendto failure (Shawn Chu) * Fix duplicate echo reply packets causing early stop in count mode (reported by Ramon Schwammberger, #53) 2013-10-10 David Schweikert <[email protected]> * Version 3.6 * Fix loop issue after 65536 pings (reported by Peter Folk and GBert, #12) * Minimum ping data size is now 0 * Removed setsockopt IPV6_CHECKSUM, which shouldn't be set and breaks compiling on Solaris (reported by Juergen Arndt) * Fix wrong min RTT value with -Q option (reported by Alexander Ivanov, * #51) 2013-05-22 David Schweikert <[email protected]> * Version 3.5 * Fix sprint_tm buffer size crash (reported by Japheth Cleaver) * Addded -D flag to print timestamps (Toke Høiland-Jørgensen) * Fix fping6 build on OS X 10.8 (unknown contributor) * Fix compatibility issue with FreeBSD (Alexandre Raynaud, Jason Harris, * #39) * Fping.spec: fix setuid permissions and provides fping6 (Marcus Vinicius * Ferreira) * Re-create configure script with autoconf 2.69 for aarch64 support (Chuck * Anderson, #45) 2012-09-04 David Schweikert <[email protected]> * Version 3.4 * Revert "Output statistics to stdout instead of stderr", because it * breaks tools assuming the output goes to stderr 2012-08-19 David Schweikert <[email protected]> * Version 3.3 * Do not output icmp errors with -q (#1) * Add --enable-ipv4 and --enable-ipv6 options to configure (Niclas * Zeising) * Fix removing of unreachable hosts when doing loop (Thomas Liske, #13 * #23) * Fix -A for fping6 (reported by Matt LaPlante, #14) * Fix "options inet6" breaking IPv4 name resolution (reported by Matt * LaPlante, #17) * Output statistics to stdout instead of stderr (suggested by Simon * Leinen, #9) * Set default data size to 56 bytes on all architectures (#18) * Added contrib/fping.spec (Stephen Schaefer, #24) * Convert man-page source to POD for easier maintenance * Fix error message on DNS error for IPv6 hosts (#27) * Fix -n flag in fping6 (#28) * Man-page fix: TOS option typo (Thomas Liske, #23) * Man-page fix: inconsistency in regards to numeric arguments (Robert * Henney) * Man-page fix: better description of option -q (#15) 2012-05-29 David Schweikert <[email protected]> * Version 3.2 * Improve documentation for -g option (G.W. Haywood) * Performance optimization for big select timeouts (#10, Andrey * Bondarenko) * Fix restart of select call after interrupt signal (#8, Boian Bonev) * Fix infinite loop caused by linked list corruption (#11, Boian Bonev) 2012-04-26 David Schweikert <[email protected]> * Version 3.1 * -g option (generate): exclude network and broadcast address for cidr ranges (idea by Eric Brander) * do not explicitely check if running as root, to make it possible to install fping with linux capabilities instead of making it setuid (setcap cap_net_raw+ep fping) * ANSI C (C89) compiler now a requirement * Portability fixes * Reorganized source directory * Bugfix: fix timeout issue on Solaris (Sandor Geller) * Man-page fixes (Axel Beckert) * Added -H option to specify number of hops (Paul Duda) * Output usage information to stdout when called with -h (Paul Duda) 2011-12-28 David Schweikert <[email protected]> * Version 3.0 * rewritten main loop for improved performance * -T parameter (select timeout) now obsolete * Maintenance taken over from unresponsive previous maintainer (anybody please step up, if you disagree) * New homepage: www.fping.org 2009-12-21 Tobi Oetiker <[email protected]> * Version v2.4b2-to3-ipv6 * added -On option to set the TOS octet * Removed unused variables from code * updated to current autoconf standards * Merged Debian changes (see below) ---------------------------------------------------------------------- fping (2.4b2-to-ipv6-16.1) unstable; urgency=low * NMU during Moenchengladbach BSP * Fixes FTBFS on kfreebsd (Closes: #555398) * Fixes typo "Paramter" in binary -- Axel Beckert <[email protected]> Sat, 23 Jan 2010 16:22:02 +0100 fping (2.4b2-to-ipv6-16) unstable; urgency=low * Fix the following bugs - Network byte order sensitivity was missing completely. Added hopefully all missing calls. - The sequence numbering scheme used led to packet drops. Changed it to a more senseful numbering scheme. - Some minor C programming mistakes ('=' instead of '=='). Patch by Stephan Fuhrmann; closes: #502569 * Add support for command line select timeout setting Patch by Marton Balint; closes: #502575 * Remove symlinks in /usr/sbin; closes: #377732 * Standards-Version is 3.8.0 -- Anibal Monsalve Salazar <[email protected]> Sat, 18 Oct 2008 12:04:52 -- +1100 fping (2.4b2-to-ipv6-15) unstable; urgency=low * Added interface binding (-I) for fping Patch by Peter Naulls <[email protected]> Closes: #439014 * Fixed a couple of typos in fping.8. Closes: #423180 * Added homepage control header * Bumped Standards-Version to 3.7.3 * Fixed the following lintian issue: - debian-rules-sets-DH_COMPAT -- Anibal Monsalve Salazar <[email protected]> Mon, 03 Mar 2008 17:46:17 -- +1100 fping (2.4b2-to-ipv6-13) unstable; urgency=low * Fixed stdout flush problem, closes: #340146. Patch by Bart Martens <[email protected]>. -- Anibal Monsalve Salazar <[email protected]> Fri, 30 Dec 2005 08:30:09 -- +1100 fping (2.4b2-to-ipv6-12) unstable; urgency=low * Fixed "problem with option -r (retry limit)", closes: #318402. Patch by Qingning Huo <[email protected]>. -- Anibal Monsalve Salazar <[email protected]> Sat, 08 Oct 2005 21:26:35 -- +1000 fping (2.4b2-to-ipv6-11) unstable; urgency=low * Fixed "would be useful to specify 'source address' like ping for multi homed machines", closes: #198486. Patch by Marc Haber <[email protected]>. -- Anibal Monsalve Salazar <[email protected]> Thu, 02 Jun 2005 08:14:54 -- +1000 fping (2.4b2-to-ipv6-10) unstable; urgency=low * Fixed "unnecessary delay with the -c option after the last packet" (Closes: #293856). Patch by Niko Tyni <[email protected]> -- Anibal Monsalve Salazar <[email protected]> Sun, 06 Feb 2005 23:25:57 -- +1100 fping (2.4b2-to-ipv6-9) unstable; urgency=low * Fixed "fping6 always does reverse lookup" (Closes: #273647). Patch by Jeroen Massar and forwarded by Bernhard Schmidt <[email protected]> -- Anibal Monsalve Salazar <[email protected]> Mon, 10 Jan 2005 -- 00:01:32 +1100 fping (2.4b2-to-ipv6-7) unstable; urgency=low * Build fping in build/ipv[46] instead of build and build-ipv6. * Made DNS errors non-fatal for IPv6 (closes: #198056). -- Herbert Xu <[email protected]> Fri, 20 Jun 2003 21:36:30 +1000 fping (2.4b2-to-ipv6-6) unstable; urgency=low * Do not use incorrect linux.h file (closes: #85468). -- Herbert Xu <[email protected]> Sat, 17 May 2003 14:13:11 +1000 fping (2.4b2-to-ipv6-5) unstable; urgency=low * Fixed yet another divide by zero bug (closes: #148445). -- Herbert Xu <[email protected]> Tue, 4 Jun 2002 12:18:03 +1000 fping (2.4b2-to-ipv6-4) unstable; urgency=low * Made fping6 setuid (closes: #136386). * Moved fping back into bin. * Partially applied IPv6 patch to fix IPv6 checksums (closes: #136479). -- Herbert Xu <[email protected]> Sun, 7 Apr 2002 20:36:56 +1000 fping (2.4b2-to-ipv6-3) unstable; urgency=low * Added compatibility symlink for fping (closes: #135203). -- Herbert Xu <[email protected]> Sat, 23 Feb 2002 08:34:11 +1100 fping (2.4b2-to-ipv6-2) unstable; urgency=low * Fixed another divide by zero error (closes: #132370). -- Herbert Xu <[email protected]> Thu, 7 Feb 2002 20:10:48 +1100 fping (2.4b2-to-ipv6-1) unstable; urgency=low * New upstream release. * Install fping into sbin as done by upstream.
jperkin
pushed a commit
that referenced
this issue
Jun 2, 2014
2014-04-16 Release 6.06 Ville Skyttä (3): Merge pull request #44 from dsteinbrunner/master Spelling fixes. Merge pull request #55 from oalders/master Karen Etheridge (2): Merge pull request #38 from mbeijen/typo-sting Merge pull request #43 from dsteinbrunner/master David Steinbrunner (2): Spelling corrections Olaf Alders (1): Typo fixes. Steffen Ullrich (1): correct behavior for https_proxy, e.g. don't send plain https:// requests to proxy, but instead establish CONNECT tunnel and then send requests inside tunnel. This change does together with a change in LWP::Protocol::https. The change supports LWP::Protocol::https with the default IO::Socket::SSL backend, but also with Net::SSL. Also: - proxy authorization is supported (http://user:pass@host:port as proxy URL, Net::SSL still needs special HTTPS_PROXY_* environemt variables, as before) - CONNECT request does not need to be the first request inside the tunnel (not with Net::SSL) - conn_cache is read and written inside request(), instead of writing in request() and reading in _new_socket(). If a https tunnel is established the cache_key no longer depends only on proxy host,port but also on the tunnel endpoint - CONNECT is a proxy request and must always use Proxy-Authorization, not Authorization header turugina (1): fix: auth-header of Digest auth did not conform to RFC 2617 when WWW-Authenticate has 'qop' parameter. Gisle Aas (1): SSL libs might trigger ENOTTY on read Michiel Beijen (1): Small typo.
jperkin
pushed a commit
that referenced
this issue
Mar 5, 2015
12.0 Remove dependency on jaraco.util. Instead depend on surgical packages. Deprecated irc.logging in favor of jaraco.logging. Dropped support for Python 3.2. 11.1.1 Issue #55: Correct import error on Python 2.7. 11.1 Decoding errors now log a warning giving a reference to the Decoding Input section of the readme. 11.0 Renamed irc.client.Manifold to irc.client.Reactor. Reactor better reflects the implementation as a reactor pattern <. This name makes it’s function much more clear and inline with standard terminology. Removed deprecated manifold and irclibobj properties from Connection. Use reactor instead. Removed deprecated ircobj from SimpleIRCClient. Use reactor instead. 10.1 Added ServerConnection.as_nick, a context manager to set a nick for the duration of the context. 10.0 Dropped support for Python 2.6. Dropped irc.client.LineBuffer and irc.client.DecodingBuffer (available in irc.client.buffer). Renamed irc.client.IRC to irc.client.Manifold to provide a clearer name for that object. Clients supporting 8.6 and later can use the Manifold name. Latest clients must use the Manifold name. Renamed irc.client.Connection.irclibobj property to manifold. The property is still exposed as irclibobj for compatibility but will be removed in a future version. Removed unused irc.client.mask_matches function. Removed unused irc.client.nick_characters. Added extra numerics for ‘whoisaccount’ and ‘cannotknock’. 9.0 Issue #46: The whois command now accepts a single string or iterable for the target. NickMask now returns None when user, host, or userhost are not present. Previously, an IndexError was raised. See Pull Request #26 for details.
jperkin
pushed a commit
that referenced
this issue
Apr 16, 2015
Version 1.4.0 - 26 Jan 2015 * Incremental base backup implementation through the reuse_backup global/server option. Possible values are off (disabled, default), copy (preventing unmodified files from being transferred) and link (allowing for deduplication through hard links). * Store and show deduplication effects when using reuse_backup= link. * Added transparent support of pg_stat_archiver (PostgreSQL 9.4) in check, show-server and status commands. * Improved administration by invoking WAL maintenance at the end of a successful backup. * Changed the way unused WAL files are trashed, by differentiating between concurrent and exclusive backup cases. * Improved performance of WAL statistics calculation. * Treat a missing pg_ident.conf as a WARNING rather than an error. * Refactored output layer by removing remaining yield calls. * Check that rsync is in the system path. * Include history files in WAL management. * Improved robustness through more unit tests. * Fixed bug #55: Ignore fsync EINVAL errors on directories. * Fixed bug #58: retention policies delete.
jperkin
pushed a commit
that referenced
this issue
Aug 29, 2015
…nce. Let me know if you need one of the removed options. Version 4.8.14 - Core * Minimal version of GLib is 2.14.0 * Add new panel binding "!SelectExt" to select/unselect files with the same extension as the current file (#3228) * Speed up of directory size calculation (#3247) * Support of italic text (#3065) - Editor * New syntax highlighting support: - puppet (#3266) - Viewer * Rewrite mcview's rendering and scrolling (#3250, #3256) - no more partial lines at the top and failure to scroll when Up or Down is pressed; - better handling of CJK characters; - handle combining accents; - improved nroff support; - more conventional scrolling behavior at the end of the file. * Use VIEW_SELECTED_COLOR in plain mode (#3405) * In !QuickView panel, don't pass any chars to command line to avoid unexpected command execution (#3253) - Misc * Code cleanup (#3265, #3262) * Bind poedit to Edit action for .po files (#3287) * Better grammar mcedit user menu (#3246) - Fixes * Fail to build against musl libc (#3267) * Error compiling with glib 2.20.3 (#3333) * Overwrite of the PROMPT_COMMAND bash variable (#2027) * contrib/*.?sh are not recreated after rerun of configure (#3181) * File rename handles zero-length substitutions incorrectly (#2952) * Lose files on "Skip" when "Cannot preallocate space for target file" (#3297) * Info panel can't obtain file system statistics on Solaris (#3277) * "Shell patterns" broken beyond repair (#2309) * File selection by patterns uses bytes instead of unicode characters (#2743) * Copy files dosn't work as expected, when copying to a directory with the special symbol in its name (#3235) * Wrong order of old_colors table items (#3404) * Input line: Alt+Backspace on one-letter word erases too much (#3390) * "Directory scanning" window is too narrow (#3162) * No Help for User Menu (#3409) * mcedit: paste from clipboard does not work (#3339) * mcviewer: hang when viewing broken man page (#2966) * mcview hex: incorrect highlight when search string not found (#3263) * mcview hex edit: UTF-8 chars are not updated (#3259) * mcview hex edit: can't enter certain UTF-8 characters (#3260) * mcview hex edit: CJK overflow (#3261) * mcedit: status line doesn't show full path to file (#3285) * Freeze when copying from one FTP location to another (#358) Version 4.8.13 - Core * New engine of user-friendly interruption of long-time operations (#2136) - Editor * Improvements of syntax highlighting: * CMake (#3216) * PHP (#3230) * Translate language names in the spelling assistant dialogue (#3233) - Viewer * Add separate normal(default) colour pair for viewer (#3204) * Dealing with utf-8 man pages in view/open (#1539) * "Goto line" is 1-based now (#3245) - Misc * Code cleanup (#3189, #3223, #3242) * Add new skins: gray-green-purple256 and gray-orange-blue256 (#3190) - Fixes * First Backspace/Delete is ignored after mouse click in an input widget (#3225) * Recursive find file doesn't work on Samba share (#3097) * Recursive find file doesn't work on Windows NFS share (#3202) * Incorrect file counter in move operation (#3196, #3209) * "Directory scanning" window is too narrow (#3162) * Colon is not recognized inside escape seq in prompt (#3241) * Quick view doesn't grab focus on mouse click (#3251) * fish subshell: overridden prompt (#3232, #3237) * mcviewer: broken switch between raw and parse modes (#3219) * mcviewer: incorrect percentage in mcview hex mode (#3258) * RAR VFS incorrectly recognizes UnRAR version (#3240) * viewbold and viewselected are missing from some skins (#3244) * Incorrect enconding name for manual page (#3239) * "User menu -> View manual page" doesn't do coloring (#3243) Version 4.8.12 - Core * Speed up of file find (#2290) * If cwd is a symlink it is kept at startup (#3093) * Improve support of Zsh (#3121, #3124, #3125, #3177) * Launch external editor/viewer without passing line number (#3117) * Exit without confirmation by default (#3132) * Simple user-friendly skin selector (#2165, #3178) * Use Joliet and RockRidge in ISO9660 image view action (#3187) - VFS * Use .zip extension as preferred way to recognize ZIP archives (#2857) - Editor * Configurable selection reset on CK_Store (#3111) - Misc * Code cleanup (#3113, #3151) * Adjust script permissions to installed ones (#2274) * Fix name of FSF in add source files (#3167) * Skin cleanups (#3180, #3184) * Do not consider "String not found" message as error (#3179) - Fixes * Broken build with NCurses (#3114) * Incorrect tilde expansion in copy/rename/move dialog (#3131) * Advanced chown: Escape on user list accepts value (#3150) * Toggling hidden files using mouse doesn't update the other panel (#3156) * Question mark in delete confirmation is on its own line (#3123) * Popup dialogs wander upwards upon resize (#3173) * Keypad '*' doesn't work with numlock off (#3133) * Some inconsistencies in "Learn keys" UI (#3134) * Unconventional behavior of "Display bits" dialog (#3152) * Shift-Fn keys don't work in 256-color mode of tmux (#2978) * mcedit: format paragraph produces inconsistent wrapping (#3119) * mcedit: file out-of-date check on saving is botched (#3142) * mcedit: 1st line is shifted after paragraph format (#1666) * mcedit: trailing newline check applied too early when exiting (#3140) * Inconsistency of the arrow's direction in the panel header line across skins (#3157) * Possible segfault while passing messages to widgets (#3116) * Possible segfault when freeing a VFS (#3116) * Segfault in cpio VFS while reading corrupted RPM (#3116) * Segfault in sftpfs VFS when trying to view a file (#3176) * Incorrect handling of filenames with unrar v5 (#3073) * FISH VFS: remote panel confused by filenames with '%' (#2983) * iso9660: xorriso shows only one depth (#3122) * Nicedark skin looks bad on black-on-white terminals (#3154) * Incorrect definition of "topmiddle" and "bottommiddle" characters (#3183) Version 4.8.11 - Core * Live update of panels size when editing layout (#3060) * Support "Compute totals" option in move file operation (#2075) - VFS * rpm extfs - show dependency version (#2812) - support tar payload (#3064) - improve support for EPOCH tag (#1588) - add support for PREINPROG/POSTINPROG/PREUNPROG/POSTUNPROG, VERIFYSCRIPTPROG and TRIGGERSCRIPTS/TRIGGERSCRIPTPROG tags (#1588) - Editor * Support "bracketed paste mode" of xterm (#2661) * Clarify Java syntax highlighting (#3057) - Misc * Print warnings about unknown '--with-' / '--enable-' configure options (#3029) * Code cleanup and refactoring (#3051, #3066) - Fixes * FTBFS on GNU Hurd (#3053, #3071) * Segfault while moving files (#3059, #3105) * Broken handling of mc command line arguments (#3047) * Copy/move doesn't work if num_history_items_recorded=0 (#3076) * No subdir path completion in current dir, if stub is not starting with './' (#3018) * Deprecated "find -perm +xxx" syntax is used (#3089) * Home, End, Shift-Fn keys don't work in tmux (#2978) * Improper [en|dis]abling of layout dialog split adjustment buttons (#3061) * Bogus strings in 'Confirmation' config dialog (#2271) * "Configure options" first entry not highlighted (#3084) * "Setup saved to ~/.config/mc/ini" message is misleading (#3096) * F3 doesn't work on .so files in FreeBSD 9.x (#3101) * Typo in mc.lib: "less=%filename +%linenog" instead of "+%lineno" (part of #3044) * Wrong order of filename and line number for external editor (part of #3044) * mcedit: tabs are lost when text is pasted (#1797 as part of #2661) * mcedit: question on large file treats Escape as Yes (#3107) * Broken case-sensitive search in editor/viewer/diffviewer (#3069) * Changes to files in nested .zip archives are lost (#3070) * Incorrect handling of filenames with spaces with unrar v5 (#3073) * iso9660 VFS: filenames truncating in ISO file listing (#3091) * vfs_path_from_str_flags() doesn't support VPF_STRIP_HOME (#3098) * Bright colors are used as background colors in 16-color skins (#3050) * Various defects in documentation (#3052, #3092) Version 4.8.10 - Core * Do not link GModule if it is not required (save space on embedded systems) (#2995) * Behavior of the 'Right' key in the 'Directory hotlist' was changed: now 'Right' key is used only to enter into the group (#3045) - Misc * Code cleanup (#3035) - Fixes * Build failure on Cygwin (#3041) * Broken NCurses detection (#3043) * Broken handling of mc command line arguments (#3047) * Cannot enter into zip archive in tar one (#3034) * Cannot open some jar files * mcedit: file descriptor leak (#3040) * mcedit: paragraph format doesn't respect multibyte characters (#2713) * Crash after entering a wrong SFTP password (#3036) Version 4.8.9 - VFS * extfs: support unrar-5 (#3015) * extfs: use xorriso (if exists) for writing into ISO images (#3027) - Editor * Support unlimited file size (#1743) - Misc * Lot of code cleanups (#2990, #2071, #2164, #2998, #3003, #3005, #3022) * Display additional info while viewing (by F3) *.iso files (#2006) * New skins: - modarin256: set of 256-color skins from Oliver Lange (#2737) - Fixes * Fail to link if system lib does not contain strverscmp (#2992) * Segfault when mc's temporary directory doesn't belong to the correct user (#3021) * Race condition when creating temporary directory (#3025) * Mouse doesn't work in screen and tmux (#3011) * Incorrect file size in copy/move overwrite query dialog (#3000) * Garbage in subshell prompt (#3001) * Incorrect WLabel redraw after text change (#2991) * Find File: "All charsets" options don't work (#3026) * When an unknown key is pressed, it is interpreted as garbage (#2988) * Segfault on creating new file in external editor (#3020) * Rotating dash is not removed when mc finishes reading the directory (#2163) * mcedit: word completion failed if word to be completed is begun from begin of file (#2245) * mcview: broken switch between raw and parse modes (#2968) * Hex viewer: continue search doesn't work (#2706) * sftpfs: broken SSH aliases (#2923) Version 4.8.8 - Core * Make copy/move progress dialog window wider up to 2/3 of screen width (#2076) * Ask file name before create new file in editor (#2585) * Support newer extended mouse protocol SGR-1006 instead of URXVT-1015 (#2956) * Allow skip directory scanning before file operation. Print directory count and size in addition to directory name (#2101) * Add jump support to target line in some external editors and viewers (#2206) - Editor * Update syntax highlighting: - Jal programming language (#2855) - gplink configuration files (.lkr extension) (#2855) - Makefile with .mak extension (#2896) - ZSH configuration files (#2950) - Fortran (#2962) - Misc * Code cleanup (#2944, #2954) * Report real compiler in MC_CHECK_ONE_CFLAG instead of 'gcc' * Hints files now translated via Transifex (#2980) - Fixes * Segfault in file operation due to unhandled regexp error (#2493) * Tab completion vs. spaces and escaping (#55)\ * Special chars are not escaped in autocompletion of filenames (#2626) * Buttons in the 'Directory hotlist' window are placed incorrectly (#2958) * Mouse doesn't select text in subshell in native console (#2964) * Mouse click below non-droppeddown menubar activates menu box (#2971) * Insufficient quoting and wrong message in user menu (#2947) * mcedit: floating point exception (division by zero) (#2953) * mcedit: broken autocompletion (#2957) * mcview: broken magic mode (#2976) * Broken opening of .war archives (#2974) Version 4.8.7 - Core * Minimal GLib version is 2.12.0 * Implementation of suspend/resume in copy/move file operations (#2111) * Start of widget subsystem reimplementation (#2919) - VFS * uc1541 extfs plug-in updated up to version 2.5 (#2935) - Editor * Reset selection after text paste (only in non-persistent selection mode) (#2660) * Don't indent blank lines (#303). * Add .psgi as Perl syntax highlighting (#2912) * Place cursor after inserted chars (#319) * Add option in ini file to save spelling language (spell_language=NONE for disable aspell support) (#2914) - Misc * Code cleanup (#2888, #1950) * Minimal "check" utility version is 0.9.8 * Remove the empty contrib/dist/debian/ since it maintained separately in Debian (#2871) * mc.ext updates: - add support of SVG images (#2895) - add support of .asm file extension (#2892) - add support of .hh file extension (#2892) - all file extension for source files now are case insensitive (#2892) - add support of JNG and MNG images (#2893) - add support of Gnumeric's spreadsheets (#2894) - add support of .war archives (#2891) - make a choice between arj and unarj archivers (#2890) - make a choice between 7z and 7za archivers (#2890) - add support of ape, aac and wvm4a media formats (#2767) - add support of cbr and cbz comic books (#2739) - add support of epub e-book format (#2739) - add support of PAR archives (#2739) - use libreoffice instead of ooffice, if found, to open ODT files (#2723) - use dvicat if dvi2tty not found to view DVI files (#1686) - use 'see' utility as default pdf viewer, if found (#1686) - use 'see' utility to view images in console (#1686) * Highlight OGV files as media (#2934) * Added new translations: - Persian (fa) - Croatian (hr) - Fixes * Build failure on Cygwin (#2917) * Fail to check ncurses library if --with-ncurses-inc and --with-ncurses-libs options are used (#2926) * Crash on Solaris while trying to copy a file (#2906) * CVE-2012-4463: Does not sanitize MC_EXT_SELECTED variable properly (#2913) * Attributes of existing directories are never preserved when copying (#2924) * Broken path completion on paths starting with ~/ (#2898) * Terminal settings are not changed when window is resized (#2198) * Enter into symlink to compressed patch shows empty patch (#2910) * Test failure on Cygwin due to incorrect linkage flag (#2918) * Non-portable test (#2883) Version 4.8.6 - Fixes * mcedit: two-columns extra offset of cursor after tab character (#2881) * diffviewer: cannot open file if name contains '$' (#2873) Version 4.8.5 - Core * Implemented case-insensitive patterns in mc.ext bindings (#2250) - Editor * Code refactoring and cleanup (#1977) - Diff viewer * Bidirectional merge (F5 merge left-to-right, F15 - merge right-to-left) (#2863) - Misc * Syntax highlighting news and updates: - update assembler.syntax: x86 AMD64 registers highlighting (#2542) - new cmake.syntax: preliminary and incomplete syntax file for CMakeLists.txt files (#2084) - new dlink.syntax: syntax highlighting for D-Link switches command set (#2649) - update properties.syntax: more nice look-and-feel (#1869) * mc.ext enhancement (#2103): - use chm_http text-mode handler for CHM files - play sounds only from videos in text mode - use pdftotext -layout -nopgbrk switches - try to use elinks before links for HTML - soffice2html text-mode handler for SXW files - wvHtml text-mode handler for doc files - xlhtml text-mode handler for XLS files - ppthtml text-mode handler for PPT/PPS files - open=view+pager fallback (noX) for PostScript, PDF, OD[PST] and DVI - standarized $DISPLAY checks * File extension support: - SQLite database files (#2103) - compiled Java files (*.class) (#2103) - m4a for MP4 containers with audio data in the Advanced Audio Coding (AAC) or its own Apple Lossless (ALE, ALAC) formats (#2869) - .ogm extension was deprecated in favor of .ogv (#2664) - Fixes * Bad EXTHELPERSDIR substitution if --prefix is not set (#2849) * Partially broken loading of user-defined keymap file (#2848) * Enter on directory named '~' goes to the home one (#2874) * Cannot Copy/Move files with filename encoding change (#2791) * Cannot view compressed files named like log.1.gz (with digit in name) (#2852) * Panel is not refreshed if panel history is called using mouse (#2854) * Duplicate entities in panel with 'tree view' mode (#2835) * Broken synchronization with filelist and tree panels (#2862) * Standalone mcedit doesn't load saved file position (#2853) * mcedit segfaults when aspell (en) dictionary is not installed (#2856) * mcedit segfaults after "Back from declaration" call (#2859) * mcedit: unable to save changes in "Safe save" mode(#2832) * Segfault when viewing HTML files with "mc -v" (#2858) * Broken 'Enter' action on a rpm file containing space character in filename (#2838) * extfs: uc1541 broken handling (#2864) * mc.ext: OGV format handled as audio (#2869) Version 4.8.4 - Core * Use xdg-open by default in mc.ext.in if present to open files, fallback on current scheme otherwise (#2118) * Improve of mouse event handling in dialogs (#2817) * Show extended info about compiled-in paths for internal/external macros in the "mc -F" output (2495) - VFS * Added SFTP support (#1535) - Editor * Multieditor: allow edit many files in one mcedit window (#2261, #2839) * Aspell support for spell check (#2788) - Viewer * Handle CK_FileNext/CK_FilePrev actions inside mcviewer (#2814) - Misc * Tweak and cleanup of code in case of --disable-charset option usage (#2827) * File extension support: - .gem - rubygems (#2797) - .cpio.xz - compressed cpio archives (#2798) - .webm - WebM video (#2746) - .lib - gputils artifacts (#2751) - Fixes * Build failure on FreeBSD 6 (#2808) * src/filemanager/filegui.c does not compile on Solaris due to missing macros (#2825) * Loss of data on copy to full partition (#2829) * Crash at Chown command (#2784) * Crash when creating relative symlink (#2787) * Misinterpretation of dirs as command line arguments (#2783, #2805) * Number of panelized files was limited to 127 (#2813) * CK_History removes CK_HistoryNext entries (#2313) * URL with port was stored wrong in history (#2833) * Can't find 00 (zeroes) in patterns in hex search (#2795) * Hotkey conflicts in 'Search' dialog (#2843) * Error message when entering into compressed tar and cpio archives (#2785) * Garbage directory listing in ftpfs (#2800) * Incomplete sand256 skin (#2807) * mcedit scripts are installed as data files (#1437) * Fails to build from source with --enable-tests (#2786) * Tests failure on PowerPC,S390,S390x (#2804) * Fail to compile if --without-vfs configure option specified (#2834) * do_panel_cd: FTBFS with --enable-tests on [kfreebsd-i386,kfreebsd-amd64,ia64,armhf] (#2803) Version 4.8.3 - Misc * Code cleanup (#2780) - Fixes * Broken support of XDG_* shell variables (#1851) * Segmentation fault while background copying (#2663) * MC ignores second directory argument (#2762) * Interpretation of LANG variable needs to be case insensitive (#2386) * Cannot copy zero-length files with "Preallocate space" option (#2755) * Problem in the Copy operation with unchecked the "Preserve attributes" option (#2278) * * Cursor position reset after update when panel is panelized, but doesn't (#2766) * File selection reset after exit from the archive in the root (#2776) * Hotlist: broken newly added entries if old-style path is present (#2753) * Can't rebind Fx keys in the file manager (#2384) * "justified" menu alignment (#2756) * The last (or single) word of hyperlinks in the interactive help don't act on mouse clicks (#2763) * 'cd' command is not working in shell link (#2758) * mc hangs on switching screens (#2608) * Case sensitive search with SEARCH_TYPE_PCRE is broken (#2764) * mcedit can't run w/o file as parameter (#2754) * mcedit can't record input char (#2757) * mcedit: save file on top of existing directory changes dir's permissions (#2761) * Unable to edit gzipped files (#2759) * mcedit hangs up on replace with regexp contains '^' or '$' (#1868) * Segfault after open incorrect archive (#2775) * mcdiff crashes if one panel is not in the listing mode (#2769) * The password for vfs sessions remains in input history (#2760) * Showing directory sizes is broken in VFS'es (#2765) * Stale symlinks in vfs (#2777) * Active VFS directories list contain incorrect current path (#2779) * Date not set properly in manpage (#2692) * Empty texinfo rule in mc.ext (#2774) * Test failure if 'HOME' contains trailing slashes (#2768) Version 4.8.2 - Core * Added new flag -X (--no-x11) to allow dont't use X11 to get the state of modifiers Alt, Ctrl, Shift (#86) * Support of '~' as home dir in 'Start at:' field in 'Find File' dialog (#2694) * Support of '~' as home dir in hotlists (#2747) * Learn of 'Back Tab' is possible now in 'Learn keys' dialog (#2628) * Optional '0x' prefix for hexadecimal search (#2705) * Dynamically resize panels (#2465) * New bindings (ScrollLeft, ScrollRight) for scroll long filenames in panels (#2731) - VFS * Internal VFS reorganization (#2695) - Editor * Added as.syntax (#2708) - Viewer * Added action bindings for backward search (#2105) - Misc * Added hotkeys for all radio/check-buttons in search/replace dialogs (#2704) * New file bindings: - .m4v, .ts - video (#2702) - djv - DjVu? (#2645) * Simplify mc.menu - remove LZMA|LZ and change p7 to 7z (#2703) * Updated list of known browsers: gnome-moz-remote mozilla firefox konqueror opera (#2725) * Added MC_HOME environment variable to set up home directory of MC (as part of #2738) * Lot of code cleanup (#2740) - Fixes * Compile failure of 4.8.1 on xBSD because "Undefined symbols: _posix_fallocate" (#2689) * MC deletes the wrong file because of forced panel reload before file operation (#2736) * Cannot chdir to directory if directory name contains the dollar sign (#2451) * Incorrect panel size after change panel split type (#2521) * Wrong total bytes counter for subdirs in copy/move dialog (#2503) * Display corruption in panels after window shrink (#2684) * Command line is unaccessible from tree panel (#2714) * Extra confirmation before delete an empty hotlist group (#1576) * Can't open an edit zero-length file from VFS in mcedit (#2710) * mcedit crashes when ~/.config is a file (#2738) * mcedit: reset selection after END/HOME/PgDn/PgUp (#2726) * 'make check' fails on arm and alpha (-z muldefs) (#2732) Version 4.8.1 - Core * Use posix_fallocate64() when copying files/moving to a new mount point (#2610) * Faster startup (#2637) * Support of extended mouse clicks beyond 223 (#2662) - VFS * Added exit point ("..") at the top of file list (after external panelization) (#275, #278) - Editor * Lex/Flex sources (extension .l) handled by yxx.syntax file. Yacc/Bison syntax completed with all symbols (#1647) * Updated syntax files: - lua - Misc * Updated skins: - sand256 (#2640) - xoria256 (#2641) * Added ability to move MC config files to specified place instead of multiple places in $HOME (#2636) * Added configure option --with-homedir (default value: XDG) (#2636) * Respect traditional placement of user preferences on Mac OS X (#2658 as part of #2636) * A few useful additions to filehighlight.ini (#2646) - Fixes * Doesn't compile when using --disable-nls (#2639) * Can't compile on OpenIndiana (Solaris) (#2643) * Moving content of bindings to mc.ext during 4.7 -> 4.8 upgrade breaks mc * Free space on filesystems >2TB is not displayed properly (#2338) * Not all errors are skipped after "Ignore all" choose (#71) * Input field in password mode is fully masked with asterisks (#2653) * In "Copy File" dialog the "preserve Attributes" checkbox is always unchecked for filesystems mounted with FUSE (#2254) * Command line cursor misplaced after a resize in viewer/editor (#2678) * Save of some learned keys is broken (#2676) * Editor sometimes shows two dots instead of letter (#2372) * Editor: word completion should ignore the current word (#2614) * Viewer sometimes shows two dots instead of letter (#1730) * Viewer shows two dialogs when searcj hot found (#2677) * Cannot navigate over spftp servers (#2634) * mc adds spaces at the beginning of all files/dirs on ftp servers (#2635) * VFS: broken SMB (#2652) * man page lies about mc.keymap (#2675) * mc does not preserve file mtime when copying over ssh (#2625) Version 4.8.0 - Misc * Code cleanup (#2620) * License version updated to GPL3+ (#1551) * Added new translation: - Interlingua - Fixes * Viewer: cursor position is not restored in hex mode (#2543) * fish: broken panels drawing after entering password (#2611) * fish: content of modified file is appended instead of overwritten in the remote host (#2632) * extfs: broken navigation in archives if current path is encoded (#2621) * extfs: strange error message when opening a 7z file if p7zip is not installed (#2598) Version 4.8.0-pre2 - Core * Added -g/--oldmouse option to support of NORMAL/BUTTON_EVENT mouse type (useful for screen/tmux) (#2601) - VFS * New extfs plugin: gitfs (#2467) * patchfs enchancement: join several hunks of the same file into one VFS entry (#2573) - Misc * mc.ext: use "include" for $EDITOR entries (#1689) * New file bindings: - .3gp - video (#2583) - Fixes * Cannot compile 4.8.0-pre1 and 4.7.5.3 on Solaris (#2587) * Recent autoconf displays warnings about missing AC_LANG_SOURCE (#2589) * Duplication of variable declarations (#2576) * Incorrect TTY layer initialization (#2601) * Wrong Backspace key behavior in QuickSearch mode if BS key is mapped to CdParentSmart action (#2522) * M-o works unexpectedly on symlink shortcuts (#2590) * Panelize doesn't honour current sorting (#2175) * Hintbar jumps to the top of the screen and overwrites main menu (#2593) * File size column is bogus for widths above 9 (#2580) * Hex search: incorrect length usage in hexadecimal search (#2579) * Editor: Incorrect Pascal syntax highlighting (#2531) * Editor: mouse clicks are ignored on the bottom line (#2591) * Editor: extended keybingings are broken (#2586) * Viewer: Fixed search finds bold/underlined strings twice and highlight search results (#265) * Broken listing in ExtFS VFS module (#81) * File name length is limited in tar archive (#2201) * Crash when copying symlink over ssh (#2582) * Broken panels recode (#2595) * ftp failures - leading white space in file name (#2594) * FISH hangs while copiyng a lot of small files (#2605) Version 4.8.0-pre1 WARNING: Configuration files was moved from your $HOME/.mc directory into XDG_CONFIG_* directories to respect FDO standard (http://standards.freedesktop.org/basedir-spec/basedir-spec-0.7.html). To get more information, see ticket #1851. WARNING: VFS paths now handled as vfsprefix1://vfsdata/vfsprefix2://vfsdata (see #2361). Also, 'bindings' user file was renamed to 'mc.ext', so you need search in this file all Open=file.ext#vfsprefix and replace them to Open=file.ext/vfsprefix:// After this you should rename your 'bindings' file to 'mc.ext'. Old-style paths are handled just in 'Directory hotlist' dialog, but you couldn't mix URL-like and old style path elements in one path string. Support of old-style paths will be removed in next major release (probably in 4.9, who knows...) WARNING: keybinding names was renamed to provide some unification (see #2511). The correspondence of old and new keybinging names are described in doc/keybind-migration.txt file and in doc/keybindMigration web page. Be aware. - Core * Added 256 colours support (#2169, #2173, #2475) * Changed default text in filtered view (alt-!) to input command line (if not empty) or stay old behaviour (current file under cursor) (#2266) * Added simple swap mode that means the swap of panel locations, in addition to current swap of panel content (#2368) * Cofiguration files now moved to directory specified in XDG_CONFIG_HOME environment variable (#1851) * Panel options are read now from [Panels] section only. [Midnight-Commander] section is not read (#2305) * "Show mini info" checkbox was moved from the "Layout" dialog window to the "Panel options" one (#2305) * Select files by shift-left/right in file panel (#2534) * Added support of skip all errors on multi-file/dir operation (#71) * 'Find Files' improvements: - support relative ignored directories (#2275); - handle of ignored directories in dialog window (#2275); - "Search for content" checkbox is enabled by default (#2462) * Added hardlinks detection for filehighlight (#2478) * Unification of keybind names (#2511): - most of keybinding names are changes to unify that names. Table of old and new names is available in doc/keybind-migration.txt; - improve of key rebinding: previously, to rebind some keys, used must redefine the entire section where that bindings are placed in user keymap file. New merge algorithm doesn't require that and allows rebind only wanted keys; - added --nokeymap command line option to disable external keymaps * Sources in 'lib' directory now independent to sources in 'src' one (#2501) * Added configure parameter --enable-mclib for build libmc.so shared library (#2501) * Added new engine for universal event system (as part of #2501) * Optimized loading and saving of configurations and histories (#2541, #2545) * Reimplemented i18n support in 'Chmod' dialog window (#2557) - VFS * VFS structure changes (as part of #2501): - moved from lib/vfs/mc-vfs to lib/vfs; - split VFS-modules by directories and moved to src/vfs; - lib/vfs/vfs-impl.h was merged into lib/vfs/vfs.h * VFS now used URL-like paths (#2361) - Editor * New engine of the editor macro (#323) * Multiply repeat of the recorded actions (#323) * Call extermal scripts from the editor (#323, #2512) * Added REDO action (#25) * Group UNDO by action (#27) * Selection is not reset after execute user menu (#2463) * Vertical selection is not reset after copy/move (#2504) * More intuitive word left/right action (now the cursor stop beside EOL/BOL) (#2483) * Duble-click marks the current word. Added action MarkWord to mark word, MarkLine to mark current line (#2499) * Regexp search&replace: support escape sequences in replacement string (#1882) - Misc * Minor enhancement in mc.ext: * added -C key to nm utility in View action for static libraries (#2485) * New file bindings: - .torrent: view using ctorrent (#2562); - .mts: handle as videofile (#2566) * Added new entries in cedit.menu: "Sort selection", "Upper case", "Lower case" * New skins: - Xoria256 (#2469) - mc-4.6 (#2524) * Updated skins: * Nice dark (#1791) * Added support for check unit test framework (http://check.sourceforge.net) (as part of #2501) * Added -F/--datadir-info option to show extended information about used data dirs (#2495) * Added --configure-options to easy update & reconfigure existing mc (#2495) * Language-specific man pages and hint and help files are not installed if mc is built with --disable-nls option (#2514) * Added new translation: - Esperanto * Code cleanup (#2481, #2515, #2518, #2560, #2570) - Fixes * Build failure on DragonFly BSD (#2516) * Broken Del & Backspace in dialogs (in locale CP866) (#1634) * Screen and input corruption under xterm in non-UTF locales (#1668) * Alt-Backspace shortcut doesn't work (#2455) * Broken command autocompletion (#2458) * Swap panels doesn't respect sort options (#2368) * File list format of panel is initialized incorrectly after switch back from quick view or info mode to file list one (#2390) * Main menu is not drawn correctly after change of it visibility and activity (#2466) * MC switches to left panel after call of command history using mouse (#2459) * Find file: don't check content regexp if search for content is not used (#2464) * Find file: broken lynx-like navigation in panelization of search result (#2491) * Dialog trims leading spaces in input field (#2544) * Panelize content is lost when doing F5/F6/F8 on a file on the other panel (#2312) * Color of panel header cannot be set in the command line (#2170) * ctrl-g key closes file panels (#2520) * Incorrect files mark by mouse (#2556) * Editor: incorrect restore selection after UNDO (#2456) * Editor: segfault after getting the previous char in utf8 (#2484) * Editor: incorrect detection of the word boundary (added '{', '}' as end of word) (#2500) * Bold and selected colors of viewer cannot be set in the command line (#2489) * Viewer: fixed incorrect starting offset for 'search again' (#2294) * Viewer: fixed problems while displaying UTF-8 manual pages (#1629) * Diff viewer: quick left/right movements don't work in non-default key maps (#2509) * AI_ADDRCONFIG is not optional for RFC 3493 non-compliant systems (#2401) * FTP directories containing @ result severe security risks (eg. deletion of homedir) (#2220) * Builtin ftp client can't download files with apostrophe in a file name (#2251) * Unable to show FTP listing if password contains # (#2360) * FTP: fixed access to file names starting with space (#81) * Bashisms in extfs (#2569) * Browsing *.deb files is broken with latest Perl (#2552) * isoinfo adds ";1" to the end of file name when Joliet without Rock Ridge is used (#2471) * patchfs incorrectly works with filenames containing spaces (#2572) * cd to ~ processed incorrectly in the command line if more than one space is separating the "cd" and "~" (#2120)
jperkin
pushed a commit
that referenced
this issue
Oct 5, 2015
### 1.7.7 / 2015-09-22 * Make HighLine::Question coerce its question argument into a String. (@97-109-107 and Abinoam P. Marques Jr. (@abinoam), #159, PR #160) ### 1.7.6 / 2015-09-17 * Fix a typo in a var name affecting solaris. (Danek Duvall (@dhduvall) and Abinoam P. Marques Jr. (@abinoam), #155, PR #156) ### 1.7.5 / 2015-09-14 * Support jruby9k for system extensions (Michael (@mmmries), PR #153) ### 1.7.4 / 2015-06-16 * Workaround on #55 for stty
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
Jun 7, 2016
Notable changes between 0.5 and 0.6: Options from OpenSSL 1.0.2f Use "any" protocol, but SSL. Merge pull request #20 from Zash/zash/checkissued Method for checking if one certificate issued another Merge pull request #68 from ignacio/master Enables building with LuaRocks and MS compilers Enables building with LuaRocks and MS compilers Merge pull request #56 from gleydsonsoares/Makefile-tweaks Makefile tweaks Keep 'sslv23' for compability, but deprected. (it will be removed in the next version) Merge pull request #62 from gleydsonsoares/update_protocol_samples add TLS_method / rename "sslv23" to "any" / update protocol samples. update protocol samples(bring "tlsv1_2" to clients and "any" to servers) for consistency and readability, rename "sslv23" to "any" since that it is related to {TLS, SSLv23}methods that handles all supported protocols. add TLS_method(). for now, keep SSLv23_method() for compatibility. Update samples (using 'tlsv1'). Merge pull request #55 from gleydsonsoares/ifndef-OPENSSL_NO_SSL3 guard SSLv3_method() with #ifndef OPENSSL_NO_SSL3 Add lsec_testcontext(). bump MACOSX_VERSION fix typo; s,intall,install, guard SSLv3_method() with #ifndef OPENSSL_NO_SSL3 Set flags to compile with internal inet_ntop() by default. Tag "alpha" explicit. MinGW progress. Merge pull request #53 from hishamhm/master Reuse tag in the LuaSec upstream repository. Merge pull request #26 from Tieske/master Update rockspec to fix Windows build Alternative implementation to inet_ntop() for old versions of Windows. Do not hardcode ar added batch files to generate sample certs on Windows Perform all validation before allocating structures Validate signatures too. API changes to root:issued([intermediate]*, cert) Fix inet_ntop() on Windows. Merge branch 'master' of https://github.com/brunoos/luasec Merge branch 'moteus_rock' added bindir to lib section, as mingw links against dll's to be found in bindir updated defines in rockspec Merge branch 'master' of github.com:Tieske/luasec into moteus_rock use winsock 2 Don't set globals from C. Fix unpack(). Stop using module(). Change to luaL_newlib(). Remove luaL_optint() and luaL_checkint(). BSD headers. Merge pull request #21 from Zash/zash/iPAddress-fix iPAddress encoding Stop if we don't have a string. Changed for strict compiles. Fix for LibreSSL/OPENSSL_NO_COMP Problem on Win64, since double does not represent SOCKET_INVALID exactly. - Add a parameter to server:sni(), so that we can accept an unknown name, using the initial context. - Add the method :getsniname() to retrieve the SNI hostname used. Updated (and renamed) rockspec Windows Encode iPAddress fields in human readable form Don't try to encode IP addresses as UTF-8 Return early if ASN1 string is invalid Push nil if unable to encode ASN1 string as UTF-8 Return human readable error message from cert:issued() SNI support. SNI support. Merge pull request #17 from Zash/zash/checkkey Verify that certificate and key belong together Merge pull request #19 from Zash/zash/pubkey Zash/pubkey Add cert:pubkey() to methods registry Add cert:issued(leafcert) for checking chains Check if private key matches cert only if both key and cert are set Check that certificate matches private key Add method for extracting public key, type and size from x509 objects
jperkin
pushed a commit
that referenced
this issue
Jul 17, 2016
- Fix incorrectly reporting files containing disabled formatting as being formatted. - Fix incorrect handling of quoted arguments in the options file (#321). - Fix error in identifying an enum return type as an enumeration (#322, 323). - Fix error in identifying an enum argument as an enumeration (#327). - Fix recognition of Qt keywords when used as variables in C++ (#329). - Fix recognition of a pointer in a C++ cast (#316). - Fix removing trailing whitespace after a changed pointer or reference cast. - Add new bracket style option "style=vtk" (#155). - Add new option "indent-preproc-block" to indent blocks of preprocessor directives (#21, #114, #229, #242, #294). - Add new option, "dry-run", to run AStyle without updating the files (#184, #285). - Add new options, "html" (-!") and "html=###", to display the HTML help documentation in the default browser. - Add tags "*INDENT-OFF*" and "*INDENT_ON*" to disable formatting of source code blocks (#2, #47, #55, #78, #110, #176). - Add tag *NOPAD* to disable selected formatting on a single line. - Add '__attribute__ ((visibility ("default")))' to Linux exported functions. - Remove option "style=ansi" and make it depreciated (#146). - Remove fix for broken 'case' statements from release 2.02.1, Nov 21, 2011. - Improve Korean translation (#256). - Change shared libraries to include the version number as part of the file name (#264) - Change "help" display to stdout to allow piping and redirection (#63). - Change "version" display to stdout. - Change headers to include foreach, forever, Q_FOREACH, and Q_FOREVER (#98, #154). - Change compiler definition ASTYLE_NO_VCX (no Visual Studio exports) to ASTYLE_NO_EXPORTS. - Change shared library error handler argument from "char*" to "const char*". - Fix not recognizing noexcept, interrupt, and autoreleasepool as pre-command headers (#225, #259). - Fix formatting of C++11 uniform initializer brackets (#253, #257, #260, #284). - Fix to not automatically space pad C++11 uniform initializer brackets (#275). - Fix formatting of enums with leading commas (#159, #179, #270). - Fix formatting of logical && operator in class initializers (#290). - Fix flagging a 'const' variable as a 'const' method (#275). - Fix piping and redirection adding an extra character to the output (#245, #252, #305). - Fix "indent-modifiers" to attach class access modifiers to Horstmann style brackets. - Fix ASFormatter to correctly recognize the end of a C++ raw string literal (#261). - Fix to recognize C++11 "enum class" as an enum (#303). - Fix indent of C++11 "noexecpt" statements within a class (#260, #304). - Fix not resetting templateDepth when a template was not found (#295). - Fix formatting of multiplication in a block paren (#144). - Fix whitespace padding when formatting an rvalue references (#297). - Fix to recognize an rvalue reference without a name (#265). - Fix to not identify an operator overload method as a calculation (#296). - Fix concatenating multiplication with a pointer dereference (#291). - Fix recognition of a pointer dereference following a question mark (#213). - Fix extra space after a trailing reference type (#300). - Fix _asm blocks not being identified as a block opener and the variable not cleared on exit (#163). - Fix indentation of line comments before a "class" opening bracket. - Fix indentation of line comments before a "namespace" opening bracket. - Fix isBracketType() method to correctly process a NULL_TYPE. - Fix unpad-paren to recognize additional variables (#43, #132, #143). - Fix indentation of C# "let" statements. - Fix a few omissions with "fill-empty-lines". - Fix file read to read 64K blocks of data. - Refactor to un-obfuscate (clarify) the code, and improve design and decomposition:: - Extract class Utf8_16 from ASConsole. - Replace Linux dependency on iconv with a Utf8_16 class for ASLibrary. - Move global "using" statements to the astyle namespace in astyle.h and ASLocalizer.h. - Move shared library declarations from astyle.h to astyle_main.h. - Move indentable macros from ASEnhancer to ASResource and create static pairs. - Simplify ASBeautifier procedure to identify the colon (:) type. - Major refactoring in ASBeautifier to create separate variables for an enum, a class statement and a class initializer. - This was needed to fix the processing of C++11 uniform initializers in a class initializer. - Minor changes to ASFormatter and ASBeautifier based on results of the Clang analyzer. - Change several methods in astyle_main to "const".
jperkin
pushed a commit
that referenced
this issue
Aug 12, 2016
--------------------------- * version 2.6.1 released 2016-03-01 ** flex resources *** The flex project is now hosted at github. Consider this a "period of transition". In particular, you should start at https://github.com/westes/flex for the flex codebase, issue tracking and pull requests. *** New releases of flex are to be found at https://github.com/westes/flex/releases. ** flex internals *** Flex now uses more modern and more standard names for variable types. There's more work to be done on that front yet, though. *** A number of compiler warnings have been remedied. *** Line directives should now work as expected and be absent when that is expected. ** test suite *** When running the test suite, c++ files are compiled with the c++ header inside the flex distribution, rather than relying on the build system's flex header , which might not be installed yet or which might be out of date with respect to what flex tests expect. *** Some portability fixes in the test suite such as opening files for reading in binary mode ** Building flex *** The file src/scan.c asdistributed with flex source is now built with the current version of flex. Occasionally this had to be done manually to pick up new flex features. It's now just a part of flex's build system. *** The pdf version of the manual is no longer distributed with flex, although if you have the texinfo package installed, you can still build it. *** lots of general build system cleanup *** the build system tries a bit harder to find libtoolize and texi2dvi. *** When help2man and texi2dvi are missing, the error messages are now much more helpful. ** bug fixes *** resolved github issues #53, #54, #55, #61. *** Resolved sf bugs #128, #129, #155, #160, #184, #187, #195. (pkgsrc changes) - Githubify - pre-configure: stage set for ./autogen.sh - Add patch-src_Makefile.am to generate parse.h before main.c is compiled (MAKE_JOBS_SAFE = no without this patch) - Drop (or convert) patches patch-src_filter.c -- upstream taken patch-src_Makefile.in -- file is gone patch-src_Makefile.am converted to the same name, different purpose patch-tests_Makefile.in converted to patch-tests_Makefile.am - Add BUILD_DEPENDS+= help2man-[0-9]*:../../converters/help2man
jperkin
pushed a commit
that referenced
this issue
Aug 24, 2016
NEWS: Version 2.5.3 ------------- - Updated zoneinfo to 2016d - Fixed parser bug where unambiguous datetimes fail to parse when dayfirst is set to true. (gh issue #233, pr #234) - Bug in zoneinfo file on platforms such as Google App Engine which do not do not allow importing of subprocess.check_call was reported and fixed by @savraj (gh issue #239, gh pr #240) - Fixed incorrect version in documentation (gh issue #235, pr #243) Version 2.5.2 ------------- - Updated zoneinfo to 2016c - Fixed parser bug where yearfirst and dayfirst parameters were not being respected when no separator was present. (gh issue #81 and #217, pr #229) Version 2.5.1 ------------- - Updated zoneinfo to 2016b - Changed MANIFEST.in to explicitly include test suite in source distributions, with help from @koobs (gh issue #193, pr #194, #201, #221) - Explicitly set all line-endings to LF, except for the NEWS file, on a per-repository basis (gh pr #218) - Fixed an issue with improper caching behavior in rruleset objects (gh issue #104, pr #207) - Changed to an explicit error when rrulestr strings contain a missing BYDAY (gh issue #162, pr #211) - tzfile now correctly handles files containing leapcnt (although the leapcnt information is not actually used). Contributed by @hjoukl (gh issue #146, pr #147) - Fixed recursive import issue with tz module (gh pr #204) - Added compatibility between tzwin objects and datetime.time objects (gh issue #216, gh pr #219) - Refactored monolithic test suite by module (gh issue #61, pr #200 and #206) - Improved test coverage in the relativedelta module (gh pr #215) - Adjusted documentation to reflect possibly counter-intuitive properties of RFC-5545-compliant rrules, and other documentation improvements in the rrule module (gh issue #105, gh issue #149 - pointer to the solution by @phep, pr #213). Version 2.5.0 ------------- - Updated zoneinfo to 2016a - zoneinfo_metadata file version increased to 2.0 - the updated updatezinfo.py script will work with older zoneinfo_metadata.json files, but new metadata files will not work with older updatezinfo.py versions. Additionally, we have started hosting our own mirror of the Olson databases on a github pages site (https://dateutil.github.io/tzdata/) (gh pr #183) - dateutil zoneinfo tarballs now contain the full zoneinfo_metadata file used to generate them. (gh issue #27, gh pr #85) - relativedelta can now be safely subclassed without derived objects reverting to base relativedelta objects as a result of arithmetic operations. (lp:1010199, gh issue #44, pr #49) - relativedelta 'weeks' parameter can now be set and retrieved as a property of relativedelta instances. (lp: 727525, gh issue #45, pr #49) - relativedelta now explicitly supports fractional relative weeks, days, hours, minutes and seconds. Fractional values in absolute parameters (year, day, etc) are now deprecated. (gh issue #40, pr #190) - relativedelta objects previously did not use microseconds to determine of two relativedelta objects were equal. This oversight has been corrected. Contributed by @elprans (gh pr #113) - rrule now has an xafter() method for retrieving multiple recurrences after a specified date. (gh pr #38) - str(rrule) now returns an RFC2445-compliant rrule string, contributed by @schinckel and @armicron (lp:1406305, gh issue #47, prs #50, #62 and #160) - rrule performance under certain conditions has been significantly improved thanks to a patch contributed by @dekoza, based on an article by Brian Beck (@exogen) (gh pr #136) - The use of both the 'until' and 'count' parameters is now deprecated as inconsistent with RFC2445 (gh pr #62, #185) - Parsing an empty string will now raise a ValueError, rather than returning the datetime passed to the 'default' parameter. (gh issue #78, pr #187) - tzwinlocal objects now have a meaningful repr() and str() implementation (gh issue #148, prs #184 and #186) - Added equality logic for tzwin and tzwinlocal objects. (gh issue #151, pr #180, #184) - Added some flexibility in subclassing timelex, and switched the default behavior over to using string methods rather than comparing against a fixed list. (gh pr #122, #139) - An issue causing tzstr() to crash on Python 2.x was fixed. (lp: 1331576, gh issue #51, pr #55) - An issue with string encoding causing exceptions under certain circumstances when tzname() is called was fixed. (gh issue #60, #74, pr #75) - Parser issue where calling parse() on dates with no day specified when the day of the month in the default datetime (which is "today" if unspecified) is greater than the number of days in the parsed month was fixed (this issue tended to crop up between the 29th and 31st of the month, for obvious reasons) (canonical gh issue #25, pr #30, #191) - Fixed parser issue causing fuzzy_with_tokens to raise an unexpected exception in certain circumstances. Contributed by @MichaelAquilina (gh pr #91) - Fixed parser issue where years > 100 AD were incorrectly parsed. Contributed by @Bachmann1234 (gh pr #130) - Fixed parser issue where commas were not a valid separator between seconds and microseconds, preventing parsing of ISO 8601 dates. Contributed by @RyansS (gh issue #28, pr #106) - Fixed issue with tzwin encoding in locales with non-Latin alphabets (gh issue #92, pr #98) - Fixed an issue where tzwin was not being properly imported on Windows. Contributed by @labrys. (gh pr #134) - Fixed a problem causing issues importing zoneinfo in certain circumstances. Issue and solution contributed by @alexxv (gh issue #97, pr #99) - Fixed an issue where dateutil timezones were not compatible with basic time objects. One of many, many timezone related issues contributed and tested by @labrys. (gh issue #132, pr #181) - Fixed issue where tzwinlocal had an invalid utcoffset. (gh issue #135, pr #141, #142) - Fixed issue with tzwin and tzwinlocal where DST transitions were incorrectly parsed from the registry. (gh issue #143, pr #178) - updatezinfo.py no longer suppresses certain OSErrors. Contributed by @bjamesv (gh pr #164) - An issue that arose when timezone locale changes during runtime has been fixed by @carlosxl and @mjschultz (gh issue #100, prs #107, #109) - Python 3.5 was added to the supported platforms in the metadata (@tacaswell gh pr #159) and the test suites (@moreati gh pr #117). - An issue with tox failing without unittest2 installed in Python 2.6 was fixed by @moreati (gh pr #115) - Several deprecated functions were replaced in the tests by @moreati (gh pr #116) - Improved the logic in Travis and Appveyor to alleviate issues where builds were failing due to connection issues when downloading the IANA timezone files. In addition to adding our own mirror for the files (gh pr #183), the download is now retried a number of times (with a delay) (gh pr #177) - Many failing doctests were fixed by @moreati. (gh pr #120) - Many fixes to the documentation (gh pr #103, gh pr #87 from @radarhere, gh pr #154 from @gpoesia, gh pr #156 from @awsum, gh pr #168 from @ja8zyjits) - Added a code coverage tool to the CI to help improve the library. (gh pr #182) - We now have a mailing list - [email protected], graciously hosted by Python.org. Version 2.4.2 ------------- - Updated zoneinfo to 2015b. - Fixed issue with parsing of tzstr on Python 2.7.x; tzstr will now be decoded if not a unicode type. gh #51 (lp:1331576), gh pr #55. - Fix a parser issue where AM and PM tokens were showing up in fuzzy date stamps, triggering inappropriate errors. gh #56 (lp: 1428895), gh pr #63. - Missing function "setcachesize" removed from zoneinfo __all__ list by @RyansS, fixing an issue with wildcard imports of dateutil.zoneinfo. (gh pr #66). - (PyPi only) Fix an issue with source distributions not including the test suite. Version 2.4.1 ------------- - Added explicit check for valid hours if AM/PM is specified in parser. (gh pr #22, issue #21) - Fix bug in rrule introduced in 2.4.0 where byweekday parameter was not handled properly. (gh pr #35, issue #34) - Fix error where parser allowed some invalid dates, overwriting existing hours with the last 2-digit number in the string. (gh pr #32, issue #31) - Fix and add test for Python 2.x compatibility with boolean checking of relativedelta objects. Implemented by @nimasmi (gh pr #43) and Cédric Krier (lp: 1035038) - Replaced parse() calls with explicit datetime objects in unit tests unrelated to parser. (gh pr #36) - Changed private _byxxx from sets to sorted tuples and fixed one currently unreachable bug in _construct_byset. (gh pr #54) - Additional documentation for parser (gh pr #29, #33, #41) and rrule. - Formatting fixes to documentation of rrule and README.rst. - Updated zoneinfo to 2015a.
wiedi
pushed a commit
to wiedi/pkgsrc-legacy
that referenced
this issue
Nov 17, 2016
Slightly based on wip/flex by Makoto Fujiwara and Juraj Lutter. * version 2.6.2 released 2016-10-24 ** flex internals *** a segfalt involving yyrestart(NULL) has been fixed *** flex should now handle quoting when mixed with m4 processing correctly *** flex handles `[[' and `]]' correctly *** flex no longer generates non-ANSI code *** more compilation warnings were squashed in generated scanners *** prevented a buffer overflow that could occur when input buffers were the exact wrong size ** test suite *** input filenames on MSWindows are now calculated correctly *** general code cleanups in a number of tests now make the test suite compile much more cleanly ** build system *** the xz archive has been replaced with an lzip archive *** a new option to configure --enable-warnings to encapsulate passing of warning-related flags which is useful in testing flex *** make indent now works for out of source builds *** Portability warnings when generating Makefile.in files are now suppressed; they were just noise and the use of GNU extensions in Makefile.{am,in,} was intentional and well known. ** bugs *** resolved gh#67 ** new sv translation from the translation project * version 2.6.1 released 2016-03-01 ** flex resources *** The flex project is now hosted at github. Consider this a "period of transition". In particular, you should start at https://github.com/westes/flex for the flex codebase, issue tracking and pull requests. *** New releases of flex are to be found at https://github.com/westes/flex/releases. ** flex internals *** Flex now uses more modern and more standard names for variable types. There's more work to be done on that front yet, though. *** A number of compiler warnings have been remedied. *** Line directives should now work as expected and be absent when that is expected. ** test suite *** When running the test suite, c++ files are compiled with the c++ header inside the flex distribution, rather than relying on the build system's flex header , which might not be installed yet or which might be out of date with respect to what flex tests expect. *** Some portability fixes in the test suite such as opening files for reading in binary mode ** Building flex *** The file src/scan.c asdistributed with flex source is now built with the current version of flex. Occasionally this had to be done manually to pick up new flex features. It's now just a part of flex's build system. *** The pdf version of the manual is no longer distributed with flex, although if you have the texinfo package installed, you can still build it. *** lots of general build system cleanup *** the build system tries a bit harder to find libtoolize and texi2dvi. *** When help2man and texi2dvi are missing, the error messages are now much more helpful. ** bug fixes *** resolved github issues TritonDataCenter#53, TritonDataCenter#54, TritonDataCenter#55, TritonDataCenter#61. *** Resolved sf bugs TritonDataCenter#128, TritonDataCenter#129, TritonDataCenter#155, TritonDataCenter#160, TritonDataCenter#184, TritonDataCenter#187, TritonDataCenter#195.
jperkin
pushed a commit
that referenced
this issue
Jan 23, 2017
0.9.4 improved PEP8 compliance (#53) improved Python 3 compatibility (#55) improved encoding/decoding (#49, #58) - thanks @pbiering! correct handling of pytz timezones (#45) - thanks @Achimh3011! 0.9.3 Fixed use of doc in setup.py for -OO mode (#19) - thanks @dsanders11! Added python3 compatibility for base64 encoding (#21) - thanks @prauscher! Fixed ORG fields with multiple components (#23) - thanks @untitaker! Removed stray HTML entity in README (#26) - thanks @inglesp! Updated README.md to show example of adding "ORG" to a vCard (#28) - thanks @Tamerz! Handle pytz timezones in iCalendar serialization (#33) - thanks @medmunds! Use logging instead of printing to stdout (#35) - thanks @lucc!
jperkin
pushed a commit
that referenced
this issue
Mar 20, 2017
jperkin
pushed a commit
that referenced
this issue
Apr 10, 2017
0.3.7 * Fix issue #84: check if stream has 'closed' attribute before testing it * Fix issue #74: objects might become None at exit 0.3.6 * Fix issue #81: fix ValueError when a closed stream was used 0.3.5 * Bumping version to re-upload a wheel distribution 0.3.4 * Fix issue #47 and #80 - stream redirection now strips ANSI codes on Linux * Fix issue #53 - strip readline markers * Fix issue #32 - assign orig_stdout and orig_stderr when initialising * Fix issue #57 - Fore.RESET did not reset style of LIGHT_EX colors. Fixed by Andy Neff * Fix issue #51 - add context manager syntax. Thanks to Matt Olsen. * Fix issue #48 - colorama didn't work on Windows when environment variable 'TERM' was set. * Fix issue #54 - fix pylint errors in client code. * Changes to readme and other improvements by Marc Abramowitz and Zearin 0.3.3 * Fix Google Code issue #13 - support changing the console title with OSC escape sequence * Fix Google Code issue #16 - Add support for Windows xterm emulators * Fix Google Code issue #30 - implement \033[nK (clear line) * Fix Google Code issue #49 - no need to adjust for scroll when new position is already relative (CSI n A\B\C\D) * Fix Google Code issue #55 - erase_data fails on Python 3.x * Fix Google Code issue #46 - win32.COORD definition missing * Implement \033[0J and \033[1J (clear screen options) * Fix default ANSI parameters * Fix position after \033[2J (clear screen) * Add command shortcuts: colorama.Cursor, colorama.ansi.set_title, colorama.ansi.clear_line, colorama.ansi.clear_screen * Fix issue #22 - Importing fails for python3 on Windows * Thanks to John Szakmeister for adding support for light colors * Thanks to Charles Merriam for adding documentation to demos
jperkin
pushed a commit
that referenced
this issue
Apr 10, 2017
---------------------------------------------- 1.049 2017-03-28 16:02:10-05:00 America/Chicago [Fixed] - Fixed failing tests on Windows because of path separator interpolation. Thanks @nanis [Github #56] - Added explicit core dependency on Sys::Syslog in case of Perls with non-standard core libraries. Thanks @nanis [Github #57] 1.048 2017-03-27 15:16:12-05:00 America/Chicago - No changes since 1.047 trial release 1.047 2017-03-22 20:22:47-05:00 America/Chicago (TRIAL RELEASE) [Fixed] - Fixed backwards-compatibility with users using the Unix::Syslog macros in Log::Any::Adapter::Syslog. This requires that the user have Unix::Syslog installed (which Log::Any does not explicitly depend on). - Log level aliases are now case-insensitive to match the regular log levels. Prior to this, "WARNING", "Warning", and "warning" would all work, but "WARN", and "Warn" would not, only "warn". Thanks to @0x62ash for reporting this issue. [Github #55] - Invalid log levels for the File, Stderr, and Stdout adapters now result in a warning, and the default level of "trace" is used. Previously, no warning would be issued and no logs would be generated. Thanks to @0x62ash for reporting this issue. [Github #55] 1.046 2017-01-11 21:22:57-06:00 America/Chicago (TRIAL RELEASE) [Added] - The Syslog adapter is now part of the core distribution, since it relies only on core Perl modules.
jperkin
pushed a commit
that referenced
this issue
Apr 20, 2017
chardet 3.0.2 Fixes an issue where detect would sometimes return None instead of a dict with the keys encoding, language, and confidence (Issue #113, PR #114). chardet 3.0.1 This bugfix release fixes a crash in the EUC-TW prober when it encountered certain strings (Issue #67). chardet 3.0.0 This release is long overdue, but still mostly serves as a placeholder for the impending 4.0.0 release, which will have retrained models for better accuracy. For now, this release will get the following improvements up on PyPI: Added support for Turkish ISO-8859-9 detection (PR #41, thanks @queeup) Commented out large unused sections of Big5 and EUC-KR tables to save memory (8bc4b89) Removed Python 3.2 from testing, but add 3.4 - 3.6 Ensure that stdin is open with mode 'rb' for chardetect CLI. (PR #38, thanks @lpsinger) Fixed chardetect crash with non-ascii file names (PR #39, thanks @nkanaev) Made naming conventions more Pythonic throughout (no more mTypicalPositiveRatio, and instead typical_positive_ratio) Modernized test scripts and infrastructure so we've got Travis testing and all that stuff Rename filter_without_english_words to filter_international_words and make it match current Mozilla implementation (PR #44, thanks @rsnair2) Updated filter_english_letters to match C implementation (c665459) Temporarily disabled Hungarian ISO-8859-2 and Windows-1250 detection because it is very inaccurate (da6c0a0) Allow CLI sub-package to be importable (PR #55) Add a hypotheis-based test (PR #66, thanks @DRMacIver) Strip endianness from UTF with BOM predictions so that the encoding can be passed directly to bytes.decode() (PR #73, thanks @snoack) Fixed broken links in docs (PR #90, thanks @roskakori) Added early exit to chardetect when encoding is detected instead of looping through entire file (PR #103, thanks @jpz) Use bytearray objects internally instead of wrap_ord calls, which provides a nice performance boost across the board (PR #106) Add language property to probers and UniversalDetector results (PR #180) Mark the 5 known test failures as such so we can have more useful Travis build results in the meantime (d588407)
jperkin
pushed a commit
that referenced
this issue
May 19, 2017
- NEW: type coercion (#55) - FIX: quotes in quotes and double quotes at begin of string (#47) - FIX: catch null value in assignmen (#46) - NEW: support for key:=file.json for reading object values from a file (#43) - NEW: PPA contributed by Ross Duggan in #32 - FIX: "null" is now handled like we handle "true" and "false"; disable with -B - NEW: more tests in the test suite
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2013Q1 on SmartOS 13.1.0 image.
mysql-server-5.5 fails to install and run with mysql-client-5.6.
Show server versions
Show client versions
Show pkgin intending to install 5.6 client as dependency for 5.5 server
Several problems were encountered under this senario. Simply installing the 5.5 client before the 5.5 server was the work around.
Symptoms experienced were.
A. pkgin in mysql-server-5.5 reported missing my-default.cnf file.
pkgin in mysql-server-5.5.30 complains with
after resolving A by copying my-small.cnf to my-default.cnf the following also happened.
B. mysql failed to start due to missing 'mysql.host' table.
as well as mysql entering maintenance mode.
Possible Recommendation:
Exclude 5.6 and higher from mysql-server-5.5 and mysql-client-5.5 compatible pkgin versions.
The text was updated successfully, but these errors were encountered: