www/nginx: segfault when sendfile is enabled [spdy module] #201

bsdhsr · 2014-06-08T15:03:04Z

nginx version: nginx/1.6.0
TLS SNI support enabled
configure arguments: --user=nginx --group=nginx --with-ld-opt='-L/opt/local/lib -Wl,-R/opt/local/lib' --prefix=/opt/local --sbin-path=/opt/local/sbin --conf-path=/opt/local/etc/nginx/nginx.conf --pid-path=/var/run/nginx.pid --lock-path=/var/db/nginx/nginx.lock --error-log-path=/var/log/nginx/error.log --http-log-path=/var/log/nginx/access.log --http-client-body-temp-path=/var/db/nginx/client_body_temp --http-proxy-temp-path=/var/db/nginx/proxy_temp --http-fastcgi-temp-path=/var/db/nginx/fstcgi_temp --add-module=../naxsi-0.53-2/naxsi_src --with-debug --with-mail_ssl_module --with-http_ssl_module --with-pcre-jit --with-http_spdy_module --without-http_memcached_module --with-http_realip_module --with-ipv6 --add-module=../headers-more-nginx-module-0.25 --with-http_stub_status_module

Reading symbols from /opt/local/sbin/nginx...(no debugging symbols found)...done.
[New LWP 1]
[Thread debugging using libthread_db enabled]
[New Thread 1 (LWP 1)]
Core was generated by `/opt/local/sbin/nginx -c /opt/local/etc/nginx/nginx.conf'.
Program terminated with signal 11, Segmentation fault.
#0 0x00000000004512e0 in ngx_writev_chain ()

(gdb) bt
#0 0x00000000004512e0 in ngx_writev_chain ()
#1 0x0000000000455718 in ngx_solaris_sendfilev_chain ()
#2 0x0000000000496422 in ngx_http_spdy_send_output_queue ()
#3 0x0000000000499f43 in ?? ()
#4 0x0000000000471e51 in ngx_http_write_filter ()
#5 0x0000000000485df6 in ?? ()
#6 0x000000000048c36c in ?? ()
#7 0x000000000048fc3b in ?? ()
#8 0x0000000000492d93 in ?? ()
#9 0x0000000000436dfa in ngx_output_chain ()
#10 0x0000000000472402 in ?? ()
#11 0x0000000000465c38 in ngx_http_output_filter ()
#12 0x00000000004851f4 in ?? ()
#13 0x00000000004660ec in ngx_http_core_content_phase ()
#14 0x0000000000460975 in ngx_http_core_run_phases ()
#15 0x000000000046c943 in ngx_http_process_request ()
#16 0x000000000049851f in ?? ()
#17 0x0000000000496a2a in ?? ()
#18 0x0000000000456014 in ?? ()
#19 0x000000000044c3cc in ngx_process_events_and_timers ()
#20 0x0000000000453689 in ?? ()
#21 0x00000000004520fa in ngx_spawn_process ()
#22 0x0000000000454b17 in ngx_master_process_cycle ()
#23 0x00000000004c10d2 in main ()

Turning off sendfile in the nginx configuration avoids the segfault.

Let me know if any more information is needed.

mamash · 2014-06-09T09:46:00Z

Hm, I haven't followed Nginx progress in the past years, but its sendfile support has a long history of problems on SunOS in general, which is why we have always recommended turning it off. Again, this might have had changed and the above is an entirely unrelated issue.

Out of curiosity, did you enable SPDY in your configuration?

bsdhsr · 2014-06-09T10:20:27Z

Yes, the segfault is triggered only when accessing the website over SPDY.

Sendfile was on pre-spdy and didn't cause any issues, hence my assertion that this is a sendfile+spdy problem (and also #1 0x0000000000455718 in ngx_solaris_sendfilev_chain ()).

solarus-1.0.4 (2013-06-26) Bug fixes for the 1.0 release. Solarus changes: * Don't die if a script tries so show a missing string (TritonDataCenter#237). * Don't die if a treasure has a variant unexistent in the item sprite. * Fix customization of joypad commands. solarus-1.0.3 (2013-06-25) Bug fixes for the 1.0 release. Solarus changes: * Fix blocks not completely moved since Solarus 1.0.2. solarus-1.0.2 (2013-06-22) Bug fixes for the 1.0 release. Solarus changes: * Fix a crash when a treasure callback changes the hero's state (TritonDataCenter#224). * Fix a crash when a victory callback changes the hero's state. * Fix a crash due to invalid sprite frame when animation is changed (TritonDataCenter#26). * Fix an assertion error with FollowMovement of pickables. * Fix the fullscreen mode not working on Mac OS X 10.7+ (TritonDataCenter#213, TritonDataCenter#220). * Fix pickable treasures that could be obtained twice sometimes. * Fix fade-in/fade-out effects on sprites that did not work (TritonDataCenter#221). * Fix sol.audio.play_music() that failed with "none" or "same" (TritonDataCenter#201). * Fix item:set_sound_when_brandish() that did not work. * Fix diagonal movement that could bypass sensors since Solarus 1.0.1. * Fix circle movement not working after entity:set_enabled(true). * Fix detection of movement finished for NPCs. * Fix memory issues with menus (TritonDataCenter#210). * Fix handling of nil parameter in boolean setters (TritonDataCenter#225). * Fix hangling the default language. * Correctly suspend timers when set_suspended_with_map is called. * When a sprite is suspended, suspend its transitions (TritonDataCenter#226). * Don't die if a music or a sound cannot be found. * Don't die if an image cannot be found. * Don't die if running a savegame without starting location specified. * Don't die if a script refers to a non-existing equipment item. * Don't die if the self parameter is missing when calling a method (TritonDataCenter#219). * Fix dangling pointers after removing some kind of entities. Solarus Quest Editor changes: * Editor: allow to create map entities from the quest tree (TritonDataCenter#208). * Editor: fix a typo in the bomb flower sprite (TritonDataCenter#214). * Editor: fix a possible NullPointerException when opening an invalid map. Documentation changes: * Documentation: add the syntax specification of maps and tilesets.

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)

* Release 0.6.5 (12-Aug-2014) ** Compatibility Fixes This release is compatible with Twisted-14.0.0. Foolscap no longer claims compatability with python-2.4.x or 2.5.x . These old versions might still work, but there are no longer automated tests to ensure this. Future versions will almost certainly *not* work with anything older than python-2.6.x . Foolscap remains incompatible with py3, sorry. ** Forward Compatibility When parsing FURLs, the connection hints can now use TCP sockets described with the Twisted Endpoints syntax (e.g. "tcp:host=127.0.0.1:port=9999"), in addition to the earlier host:port "127.0.0.1:9999" form. Foolscap-0.6.5 ignores any hint that is not in one of these two forms. This should make it easier to introduce new hint types in the future. ** Minor Changes The "ChangeLog" file is no longer updated. Violation reports now include the method name. (#201) The "flappserver" tool explicitly rejects unicode input, rather than producing hard-to-diagnose errors later. (#209)

What's new in psycopg 2.5.4 ^^^^^^^^^^^^^^^^^^^^^^^^^^^ - Added :sql:`jsonb` support for PostgreSQL 9.4 (🎫`#226`). - Fixed segfault if COPY statements are passed to `~cursor.execute()` instead of using the proper methods (:ticket:`#219`). - Force conversion of pool arguments to integer to avoid potentially unbounded pools (:ticket:`#220`). - Cursors :sql:`WITH HOLD` don't begin a new transaction upon move/fetch/close (🎫`#228`). - Cursors :sql:`WITH HOLD` can be used in autocommit (🎫`#229`). - `~cursor.callproc()` doesn't silently ignore an argument without a length. - Fixed memory leak with large objects (:ticket:`#256`). - Make sure the internal ``_psycopg.so`` module can be imported stand-alone (to allow modules juggling such as the one described in 🎫`#201`).

Version 2.0 ----------- (released Nov 9, 2014) - Default lexer encoding is now "guess", i.e. UTF-8 / Locale / Latin1 is tried in that order. - Major update to Swift lexer (pull request #410). - Multiple fixes to lexer guessing in conflicting cases: * recognize HTML5 by doctype * recognize XML by XML declaration * don't recognize C/C++ as SystemVerilog - Simplified regexes and builtin lists. Version 2.0rc1 -------------- (released Oct 16, 2014) - Dropped Python 2.4 and 2.5 compatibility. This is in favor of single-source compatibility between Python 2.6, 2.7 and 3.3+. - New website and documentation based on Sphinx (finally!) - Lexers added: * APL (#969) * Agda and Literate Agda (pull request #203) * Alloy (pull request #355) * AmbientTalk * BlitzBasic (pull request #197) * ChaiScript (pull request #24) * Chapel (pull request #256) * Cirru (pull request #275) * Clay (pull request #184) * ColdFusion CFC (pull request #283) * Cryptol and Literate Cryptol (pull request #344) * Cypher (pull request #257) * Docker config files * EBNF (pull request #193) * Eiffel (pull request #273) * GAP (pull request #311) * Golo (pull request #309) * Handlebars (pull request #186) * Hy (pull request #238) * Idris and Literate Idris (pull request #210) * Igor Pro (pull request #172) * Inform 6/7 (pull request #281) * Intel objdump (pull request #279) * Isabelle (pull request #386) * Jasmin (pull request #349) * JSON-LD (pull request #289) * Kal (pull request #233) * Lean (pull request #399) * LSL (pull request #296) * Limbo (pull request #291) * Liquid (#977) * MQL (pull request #285) * MaskJS (pull request #280) * Mozilla preprocessors * Mathematica (pull request #245) * NesC (pull request #166) * Nit (pull request #375) * Nix (pull request #267) * Pan * Pawn (pull request #211) * Perl 6 (pull request #181) * Pig (pull request #304) * Pike (pull request #237) * QBasic (pull request #182) * Red (pull request #341) * ResourceBundle (#1038) * Rexx (pull request #199) * Rql (pull request #251) * Rsl * SPARQL (pull request #78) * Slim (pull request #366) * Swift (pull request #371) * Swig (pull request #168) * TADS 3 (pull request #407) * Todo.txt todo lists * Twig (pull request #404) - Added a helper to "optimize" regular expressions that match one of many literal words; this can save 20% and more lexing time with lexers that highlight many keywords or builtins. - New styles: "xcode" and "igor", similar to the default highlighting of the respective IDEs. - The command-line "pygmentize" tool now tries a little harder to find the correct encoding for files and the terminal (#979). - Added "inencoding" option for lexers to override "encoding" analogous to "outencoding" (#800). - Added line-by-line "streaming" mode for pygmentize with the "-s" option. (pull request #165) Only fully works for lexers that have no constructs spanning lines! - Added an "envname" option to the LaTeX formatter to select a replacement verbatim environment (pull request #235). - Updated the Makefile lexer to yield a little more useful highlighting. - Lexer aliases passed to ``get_lexer_by_name()`` are now case-insensitive. - File name matching in lexers and formatters will now use a regex cache for speed (pull request #205). - Pygments will now recognize "vim" modelines when guessing the lexer for a file based on content (pull request #118). - Major restructure of the ``pygments.lexers`` module namespace. There are now many more modules with less lexers per module. Old modules are still around and re-export the lexers they previously contained. - The NameHighlightFilter now works with any Name.* token type (#790). - Python 3 lexer: add new exceptions from PEP 3151. - Opa lexer: add new keywords (pull request #170). - Julia lexer: add keywords and underscore-separated number literals (pull request #176). - Lasso lexer: fix method highlighting, update builtins. Fix guessing so that plain XML isn't always taken as Lasso (pull request #163). - Objective C/C++ lexers: allow "@" prefixing any expression (#871). - Ruby lexer: fix lexing of Name::Space tokens (#860) and of symbols in hashes (#873). - Stan lexer: update for version 2.4.0 of the language (pull request #162, PR#255, PR#377). - JavaScript lexer: add the "yield" keyword (pull request #196). - HTTP lexer: support for PATCH method (pull request #190). - Koka lexer: update to newest language spec (pull request #201). - Haxe lexer: rewrite and support for Haxe 3 (pull request #174). - Prolog lexer: add different kinds of numeric literals (#864). - F# lexer: rewrite with newest spec for F# 3.0 (#842), fix a bug with dotted chains (#948). - Kotlin lexer: general update (pull request #271). - Rebol lexer: fix comment detection and analyse_text (pull request #261). - LLVM lexer: update keywords to v3.4 (pull request #258). - PHP lexer: add new keywords and binary literals (pull request #222). - external/markdown-processor.py updated to newest python-markdown (pull request #221). - CSS lexer: some highlighting order fixes (pull request #231). - Ceylon lexer: fix parsing of nested multiline comments (#915). - C family lexers: fix parsing of indented preprocessor directives (#944). - Rust lexer: update to 0.9 language version (pull request #270, PR#388). - Elixir lexer: update to 0.15 language version (pull request #392). - Fix swallowing incomplete tracebacks in Python console lexer (#874).

kramdown 1.7.0 released Published on Monday, 27 April 2015 This release brings among other things support for the ‘minted’ syntax highlighter for LaTeX and a new math engine based on MathJax-Node that outputs to MathML. Changes * 4 minor changes: - The syntax highlighter ‘minted’ for the LaTeX converter is now available (fixes issue #93, initial patch #242 by l3kn) - A new math engine based on MathJax-Node that outputs to MathML is now available (patch #240 by Tom Thorogood) - Fixed #244, #246: Fenced code blocks now allow a dash in the code language name (requested and patched by Dennis Günnewig) - The option list in the man page as well in the output of kramdown --help is now sorted. * 2 bug fixes: - Fixed #230: Warning message for method in lib/kramdown/utils/configurable.rb will not show anymore (reported by Robert A. Heiler) - Fixed #239: Handling of single/double quotes in reference style links now follows the same rules as with inline links (reported by Josh Davis) kramdown 1.6.0 released Published on Saturday, 28 February 2015 This release contains many fixes and minor enhancements as well as one major goodie that comes with a small caveat: block IALs can now be applied to link and abbreviation definitions! It may not sound like much but allowing block IALs to be applied to link definitions alleviates the problem that additional attributes could only be specified via span IALs. Now such attributes can be stored together with the URL and title at the link definition, for example: This is a ![resized image]. [resized image]: some_image.jpg "with a title" {: height="36px" width="36px" style="border: 1px solid green"} There is one small caveat, though. Regard the following construct: [linkdef]: http://example.com {:.block-ial} block element, e.g. a paragraph The block IAL would have been applied to the paragraph in previous versions but now it is applied to the link definition. However, such a construct is not very likely encountered in the real world. Changes * 7 minor changes: - Block IALs can now be applied to link and abbreviation definitions (inspired by issue #194 from cabo) - The syntax highlighting engine for Rouge now allows custom formatter classes to be used (issue #214, requested by BackOrder) - The MathJax math engine now allows adding previews (issue #225, requested by jethrogb) - The “toc_levels” option can now also take a Range object (pull request #210 by Jens Krämer) - The generated table of contents of the HTML converter now contains ID attributes on the links so that back-references can be used (issue #195, requested by Ciro Santilli) - A warning is now generated when duplicate HTML attributes are detected (issue #201, requested by winniehell) - Updated used version of prawn to 2.0.0 8 bug fixes: - Fixed #192: Emphasis by using underscore sometimes wrongly worked within a word (reported by Michael Franzl) - Fixed #198: Empty alt attributes on <img> tags are now correctly handled by the kramdown converter (reported by winniehell) - Fixed #200: Trailing whitespace is now really removed in paragraphs (reported by winniehell) - Fixed #220: HTML blocks with attributes weren’t correctly detected when directly after another block (reported by Bill Tozier) - Fixed #199: Empty title attributes are now ignored for images when using the kramdown converter (reported by and pull request #206 from winniehell) - Leading and trailing white space from math statements is now stripped as the whitespace sometimes lead to LaTeX conversion errors - Fixed #226: Class names may now start with a dash in IALs/ALDs (reported by Adam Hardwick) - Multiple consecutive block IALs before an element are now correctly processed

@ixti

pkgsrc change: allow build on Ruby 2.2. ## 0.8.12 (2015-05-26) * Fix `HTTP.timeout` API (was loosing previously defined options). (@ixti) ## 0.8.11 (2015-05-22) * SNI support for HTTPS connections. See #229. (@tarcieri) * Use "http.rb" in the User-Agent string. See #227. (@tarcieri) ## 0.8.10 (2015-05-14) * Fix cookie headers generation. (@ixti) ## 0.8.9 (2015-05-11) * Add cookies support. (@ixti) * Enforce stringified body encoding. See #219. (@Connorhd) ## 0.8.8 (2015-05-09) * Fix CONNECT header for proxies. See #217. (@Connorhd) ## 0.8.7 (2015-05-08) * Fix `HTTP.timeout` API with options only given. (@ixti) ## 0.8.6 (2015-05-08) * Reset global timeouts after the request finishes. See #215. (@zanker) ## 0.8.5 (2015-05-06) * Add simple timeouts configuration API. See #205. (@ixti) * Deprecate `Request#request_header`. Use `Request#headline` instead. (@ixti) ## 0.8.4 (2015-04-23) * Deprecate `#default_headers` and `#default_headers=`. (@ixti) * Deprecate chainable methods with `with_` prefix. See #207. (@ixti) * Add support of HTTPS connections through proxy. See #186. (@Connorhd) ## 0.8.3 (2015-04-07) * Fix request headline. See #206. (@ixti) * Remove deprecated `Request#__method__`. (@ixti) ## 0.8.2 (2015-04-06) * Fix Celluloid::IO compatibility. See #203. (@ixti) * Cleanup obsolete code. (@zanker) ## 0.8.1 (2015-04-02) * Add missing `require "resolv"`. See #202. (@ixti) * Add block-form `#persistent` calls. See #200, #201. (@ixti) ## 0.8.0 (2015-04-01) * Properly handle WaitWritable for SSL. See #199. (@zanker) * Add support for non-ASCII URis. See #197. (@ixti) * Add configurable connection timeouts. See #187, #194, #195. (@zanker) * Refactor requests redirect following logic. See #179. (@ixti) * Support for persistent HTTP connections (@zanker) * Add caching support. See #77 and #177. (@Asmod4n, @pezra) * Improve servers used in specs boot up. Issue was initially raised up by @olegkovalenko. See #176. (@ixti) * Reflect FormData rename changes (FormData -> HTTP::FormData). (@ixti) * `HTTP::Headers` now raises `HTTP::InvalidHeaderNameError` in case of (surprise) invalid HTTP header field name (e.g.`"Foo:Bar"`). See #173. (@ixti)

# Changelog ## 1.0.8 (August 6, 2015) * fix kqueue assertion failed, postpone ArmKqueueWriter until all events are processed [#51, #176, #372, #401, #619] * fix Rubinius GC, crank the machine from Ruby space when running Rubinius [#201, #202, #617] * test to show that LineText2 preserves whitespace and newlines [#32, #622] * bump up compiler warnings and resolve them [#616] * fix Windows x64 use uintptr_t instead of unsigned long for binding pointers [#612, #615] * fix linetext2 unroll tail recursion to avoid stack level too deep [#609] * fix for compilation with SSL on windows [#601] * open file descriptors and sockets with O_CLOEXEC where possible [#298, #488, #591] * fix SmtpClient: send second EHLO after STARTTLS. [#589] * fix nul-terminated strings in C, use StringValueCStr instead of StringValuePtr

Pkgsrc changes: - use ${PREFIX} for icon path in example.jwmrc - rename patch files per new format - add patch comments - take maintainership Upstream changes list from http://joewing.net/projects/jwm/release-2.3.shtml JWM v2.3 Release Notes This is a collection of major changes between JWM v2.2 and JWM v2.3. Version 2.3.0 was released 20150618. You can download the latest snapshot of JWM here: jwm-1356.tar.xz. New Features * Added support for client requested XRaiseWindow (issue #117). * Added native language support for the confirm dialog. * Added support for _NET_RESTACK_WINDOW (issue #118). * Added key binding to send the current window to a different desktop (issue #119). * Support the specification of an alternate configuration file (patch from Brian Bidulock) * Added Corner option to configure the roundedness of windows. * Updated the look of borders around menus and trays. * Add support for _NET_WM_MOVERESIZE (issue #142). * Add the fullscreen group option (patch from George Shaw). * Made window style configuration more consistent (may break old configuration files). * Add scale background type. * Added group options: nomin, nomax, noclose, nomove, noresize (issue #152), and nofullscreen (issue #163). * Added the Outline tag to MenuStyle to specify the color of menu outlines (issue #31). * Added the Outline tag to TrayStyle to specify the color of tray outlines. * To conform with GNU standards, running "make install" no longer strips the executable. To strip the executable, "make install?strip" can be used instead. * Added the ability to swallow the same client into a tray multiple times. * Added the ability to specify where the tray is hidden when auto-hide is enabled (issue #34). * Menu Includes are now loaded dynamically when a menu is shown rather than when JWM starts. * Added the sendu, sendd, sendl and sendr key bindings to send a window to a different desktop (issue #119). * Added the maxh, maxv, maxtop, maxbottom, maxleft and maxright key bindings (issues #120 and #157). * Added the ability to have separate actions per mouse button for tray buttons (issue #171). This is accomplished using the Button tag. For example: <TrayButton label="My Button"> <Button mask="1"> exec:program_for_left_click </Button> <Button mask="45"> exec:program_for_scroll_wheel </Button> </TrayButton> The Button tags are optional. By default the action will use mouse button mask 123. * Add the ability to have separate actions per mouse button for clock tray components (issue #171) and the ability to have clock tray components run actions like tray buttons (issue #172). * Add support for more than 10 menus. Now 26 additional menus can be defined using the letters a through z. Configuration Changes The following XSLT is available to update JWM v2.2 configuration files for use with JWM v2.3: jwm-2.3.xslt. To convert an existing v2.2 configuration file using xsltproc, run: cp ~/.jwmrc ~/.jwmrc.old xsltproc jwm-2.3.xslt ~/.jwmrc.old > ~/.jwmrc If you have multiple configuration files, it may be necessary to apply the XSLT to some or all of them depending on what configuration options are stored in the file. A summary of configuration changes follows. * The ActiveBackground and ActiveForeground tags have been replaced by Background and Foreground under the Active tag. This applies to TrayStyle, TaskListStyle, TrayButtonStyle, PagerStyle, and MenuStyle. * The Inactive tag under WindowStyle has been removed. The tags that used to go within this tag now go directly under the WindowStyle tag. * The autohide attribute in Tray now determines where the tray should be hidden (left, right, top, bottom, or off) instead of true or false. * Now actions in the Clock tag must be prefixed with exec: to run an external program. See the configuration documentation for documentation on all configuration options. Bug Fixes * ICCCM 2.0 WM_S selection compliance (patch from Brian Bidulock). * Fixed client window position after maximize/restore (issue #115, patch from Biran Bidulock). * Fixed window mapping bug with show desktop (issue #114). * Give focus to the top-most window after show desktop (issue #64). * Fix uninitialized memory when loading images (patch from Brian Bidulock). * Fix overlapping string issue with FriBidi (patch from Brian Bidulock). * Fixed non-UTF8 locales (issue #56). * Fixed transparency issue with some applications (issue #130). * Fixed focus after key events (patch from Brian Bidulock). * Fixed loss of focus after restoring windows (issue #131). * Fix setting of _NET_WM_STATE_HIDDEN when a window is minimized (issue #133, patch from Brian Bidulock). * Grab input focus at startup if not already set (issue #148). Updated Translations * Russian (Aleksandr Samusenko) * French (Pierrick) * Italian (Flavio aka Man from Mars) * Spanish (Pablo Lezaeta) Changes in 2.3.1 (20150628) * Added an option to group windows by class in the task bar. (the group attribute of the TrayStyle tag). * Fixed an issue with menus showing up across monitors when Xinerama is enabled. * Added the ability to show Motif-style handles on windows (the decorations attribute of WindowStyle). * Fixed an issue where the next/prev key bindings would not advance past a window that does not accept input focus. * Fixed the behavior of the Include tag within menus so that it no longer creates a submenu. * Menus included using Include are no longer loaded each time the menu is accessed. * Added a Dynamic submenu that will re-load its menu contents each time it is accessed. Changes in 2.3.2 (20150913) * Restored the ability to specifiy that windows should not have an icon (using the "icon:" group option). * JWM will now try several common extensions when loading icons. * Fixed the height and default label for dynamic menus (issue #188). * Improved handling of colormaps for pseudo-color displays. * Fixed handling of WM_STATE on big-endian machines. * Fixed an issue with menus getting stuck open. * Removed the TaskListStyle, TrayButtonStyle, and ClockStyle configuration options. These options are now set from TrayStyle. * Added the Hungarian translation (from Hermit). * Added the ability to give a 3D look to menus and trays by specifying decorations="motif" in MenuStyle and TrayStyle respectively. * Fixed an issue where JWM key bindings would not be available to applications (issue #201). * JWM now highlights the first menu item when opening a menu with the keyboard (issue #102). * Add the ability to selectively enable popups (issue #189). * Various other fixes. Changes in 2.3.3 (20151118) * JWM windows now set _NET_WM_WINDOW_TYPE (issue #223). * Added the Chinese translation (from Christopher Meng). * Added the height attribute to TaskList (issue #227). * Fixed tray button mouse bindings for the scroll wheel buttons (issue #229). * Added the restore key binding (issue #233). * Made middle-click on a task list item close the window (issue #232). * Added support for tooltips in menus (issue #111). * Added Portuguese (Brazil) translation (from Holmes). * Fixed an issue where the dock would change size if its size was not explicitly set (issue #238). * Fixed the height calculation of vertical trays (issue #228). Changes in 2.3.4 (20151122) * Now a negative tray width/height can be specified to subtract from the screen width/height (issue #250). * Added the list configuration option to TrayStyle to allow displaying windows from all desktops (all) or only the current desktop (the default, desktop) in task lists. * Improved scaling of JPEG and SVG images (issue #253). * Fixed the rendering of fixed-aspect background images. * Added the drag group option (issue #235). * Fixed rendering of window borders without a title bar.

@DennisPS

v0.8.1 Added localization support with translations for Czech, German and Slovak languages. Fixes: - Syncthing version of remote node not shown - Missing definition causing UI problems and Appreport madness on Ubuntu (thanks @Newman101) Other: - Added --portable parameter to syncthing-gtk.exe on Windows. - Updated syncthing-inotify version to 0.6.7 - Added support for download placeholders in Nautilus plugin v0.8.0.0.1 Prelease for localization testing. May work. Probably. Added localization support with translations for Czech, German and Slovak languages. Fixes: - Syncthing version of remote node not shown - Missing definition causing UI problems and Appreport madness on Ubuntu (thanks @Newman101) v0.8.0.1 Linux-only release. If you are on Windows, please, use v0.8 Fixes: - Syncthing version of remote node not shown - Missing definition causing UI problems, inotify bugs and Appreport madness on Ubuntu (thanks @Newman101) v0.8 For Syncthing 0.12 and above Additional fixes: - No 'ignore' button on Unknown device message. - Better support for non-ascii characters in user's home path on Windows v0.7.6.2 Prerelease to test with Syncthing v0.12. Most likely working. v0.7.6.1 Fixes: - Typo in Windows installer description (thanks @DennisPS) - Missing image definition causes crash with some GLib versions v0.7.6 Fixes: - window border disappearing (again) on Windows - crash on too recent glib (#198) - crash on too old glib (#201) - inotify (filesystem watcher) not being aware of created directories - Nautilus plugin ignoring some files until view is refreshed

protobuf-c (1.2.1) [ Robert Edmonds ] * Release 1.2.1. [ Paolo Borelli ] * protoc-c: Generate code that uses the universal zero initializer {0} when initializing a oneof union (#187, #205). protobuf-c (1.2.0) [ Robert Edmonds ] * Release 1.2.0. [ Ilya Lipnitsky ] * Implement the "optimize_for = CODE_SIZE" option (#183). * Eliminate undefined behavior in zigzag functions (#198). * Pack negative enum values correctly (#199). [ Peter Leschev ] * Fix protobuf_c_message_get_packed_size() on 16-bit systems (#196, #197). [ Diego Elio Pettenò ] * Update link to Autotools Mythbuster to canonical site (#201). [ Zex Li ] * Skip test suite when cross-compiling (#184).

- Fix compatibility for 4.03 (#227) - Various documentation fixes (#199,#200,#210,) - Improve wildcard detection in the ppx (#198) - Fix Lwt_stream: bounded_push#close wake the reader (#201) - Fix infinite loop with Lwt_stream.choose (#214) - Fix lazyness failure with Lwt_io.common#close (#207)

------------------------------------------------ Version 1.5.1 Bugfix release - Allow using versions of oauth2client < 2.0.0. (#197) - Check both current and new API discovery URL. (#202) - Retry http requests on connection errors and timeouts. (#218) - Retry http requests on rate limit responses. (#201) - Import guards for ssl (for Google App Engine). (#220) - Use named loggers instead of the root logger. (#206) - New search console example. (#212)

@savraj

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.

@chrisroos

## 1.2.1 * Fixed #272. Workaround Ruby bug 12832 which caused interpreter to hang. See https://bugs.ruby-lang.org/issues/12832. Thanks to @chrisroos & @petems (6f1c8b9b, #273). ## 1.2.0 * Always use prepended module to stub class & instance methods for Ruby v2+ - thanks to @grosser & @chrisroos (43d56671, #244) * Always use prepended module to stub AnyInstance methods in Ruby v2+ - thanks to @chrisroos (#262) * Always set visibility of stub method to match stubbed method on included module - thanks to @grosser & @chrisroos (e87c03b0, #248) * Always set visibility to stub method to match stubbed method on superclass - thanks to @chrisroos (38d902ad) * Allow stubbing of method to which any instance responds (#200) * Allow `includes` matcher to take matcher arguments - thanks to @lazyatom (#217) * Avoid exception in older version of Rubygems - thanks to @chrisroos (78d930a7) * Add licenses to gemspec as requested by @coreyhaines (#201) * Fix typo in README - thanks to @jaredbeck (6119460d) * Added section about using Mocha with RSpec & Rails to README (#221) * Fix documentation for Mocha::API#stub method - thanks to @raeno (599b1dcd) * Added backers and sponsors from OpenCollective - thanks to @piamancini (#253) * Fix typo in docs for equals - thanks to @alexcoco (#254) * Add known issue for Ruby v1.8 to README - thanks to @chrisroos (2c642096)

@cristen

This upgrade fixes compatibility with new lxml. Upstream changelog ================== 2.3.1 _This is a micro release and I have very little time on my hands right now sorry_ Fix crash with no values when the print_values_position param is set (thanks @cristen) 2.3.0 New call API: chart = Line(fill=True); chart.add('title', [1, 3, 12]); chart.render() can now be replaced with Line(fill=True)(1, 3, 12, title='title').render() Drop python 2.6 support 2.2.3 Fix bar static value positioning (#315) Add stroke_opacity style (#321) Remove useless js in sparklines. (#312) 2.2.2 Add classes option. Handle ellipsis in list type configs to auto-extend parent. (Viva python3) 2.2.0 Support interruptions in line charts (thanks @piotrmaslanka #300) Fix confidence interval reactiveness (thanks @chartique #296) Add horizontal line charts (thanks @chartique #301) There is now a formatter config option to format values as specified. The formatter callable may or may not take chart, serie and index as argument. The default value formatting is now chart dependent and is value_formatter for most graph but could be a combination of value_formatter and x_value_formatter for dual charts. The human_readable option has been removed. Now you have to use the pygal.formatters.human_readable formatter (value_formatter=human_readable instead of human_readable=True) New chart type: SolidGauge (thanks @chartique #295) Fix range option for some Charts (#297 #298) Fix timezones for DateTimeLine for python 2 (#306, #302) Set default uri protocol to https (should fix a lot of "no tooltips" bugs). 2.1.1 Import scipy as a last resort in stats.py (should workaround bugs like #294 if scipy is installed but not used) 2.1.0 Bar print value positioning with print_values_position. Can be top, center or bottom (thanks @chartique #291) ci doc Confidence intervals (thanks @chartique #292) data doc 2.0.12 Use custom xml_declaration avoiding conflict with processing instructions 2.0.11 lxml 3.5 compatibility (#282) 2.0.10 Fix transposable_node in case all attributes are not there. (thanks @yobuntu). 2.0.9 Add dynamic_print_values to show print_values on legend hover. (#279) Fix unparse_color for python 3.5+ compatibility (thanks @felixonmars, @sjourdois) Process major labels as labels. (#263) Fix labels rotation > 180 (#257) Fix secondary axis Don't forget secondary series in table rendering (#260) Add defs config option to allow adding gradients and patterns. 2.0.8 Fix value overwrite in map. (#275) 2.0.7 Fixing to checks breaking rendering of DateTimeLine and TimeDeltaLine (#264) (thanks @mmrose) Fix render_in_browser. (#266) (#268) (thanks @waixwong) 2.0.6 Avoid x label formatting when label is a string 2.0.5 Fix x label formatting 2.0.4 Fix map coloration 2.0.3 Fix label adaptation. (#256) Fix wrong radar truncation. (#255) 2.0.2 Fix view box differently to avoid getting a null height on huge numbers. (#254) Fix broken font_family default Fix non namespaced svg (without embed) javascript by adding uuid in config object. (config is in window.pygal now). 2.0.1 Fix the missing title on x_labels with labels. Auto cast to str x labels in non dual charts (#178) Add print_labels option to print label too. (#197) Add value_label_font_family and value_label_font_size style options for print_labels. Default print_zeroes to True (Re)Add xlink in desc to show on tooltip Activate element on tooltip hovering. (#106) Fix radar axis behaviour (#247) Add tooltip support in metadata to add a title (#249). Take config class options in account too. 2.0.0 Rework the ghost mechanism to come back to a more object oriented behavior, storing all state in a state object which is created on every render. (#161) Refactor maps Add world continents Add swiss cantons map (thanks @sergedroz) Add inverse_y_axis options to reverse graph (#24) Fix DateTimeLine time data loss (#193) Fix no data for graphs with only zeroes (#148) Support value formatter for pie graphs (#218) (thanks @never-eat-yellow-snow) Add new Box plot modes and outliers and set extremes as default (#226 #121 #149) (thanks @djezar) Add secondary_range option to set range for secondary values. (#203) Maps are now plugins, they are removed from pygal core and moved to packages (pygal_maps_world, pygal_maps_fr, pygal_maps_ch, ...) (#225) Dot now supports negative values Fix dot with log scale (#201) Fix y_labels behaviour for lines Fix x_labels and y_labels behaviour for xy like Improve gauge a bit Finally allow call chains on add Transform min_scale and max_scale as options mode option has been renamed to a less generic name: box_mode fix stack_from_top for stacked lines Add flake8 test to py.test in tox Remove stroke style in style and set it as a global / serie configuration. Fix None values in tables Fix timezones in DateTimeLine Rename in Style foreground_light as foreground_strong Rename in Style foreground_dark as foreground_subtle Add a render_data_uri method (#237) Move font_size config to style Add font_family for various elements in style Add googlefont:font support for style fonts Add tooltip_fancy_mode to revert to old tooltips Add auto print_value color + a configurable value_colors list in style Add guide_stroke_dasharray and guide_stroke_dasharray in style to customize guides (#242) (thanks @cbergmiller) Refactor label processing in a _compute_x_labels and _compute_y_labels method. Handle both string and numbers for all charts. Create a Dual base chart for dual axis charts. (#236) Better js integration in maps. Use the normal tooltip.

Version 0.14.2 -------------- Released 2017-01-10 - Fix bug where ``FlaskForm`` assumed ``meta`` argument was not ``None`` if it was passed. (`#278`_) .. _#278: pallets-eco/flask-wtf#278 Version 0.14.1 -------------- Released 2017-01-10 - Fix bug where the file validators would incorrectly identify an empty file as valid data. (`#276`_, `#277`_) - ``FileField`` is no longer deprecated. The data is checked during processing and only set if it's a valid file. - ``has_file`` *is* deprecated; it's now equivalent to ``bool(field.data)``. - ``FileRequired`` and ``FileAllowed`` work with both the Flask-WTF and WTForms ``FileField`` classes. - The ``Optional`` validator now works with ``FileField``. .. _#276: pallets-eco/flask-wtf#276 .. _#277: pallets-eco/flask-wtf#277 Version 0.14 ------------ Released 2017-01-06 - Use itsdangerous to sign CSRF tokens and check expiration instead of doing it ourselves. (`#264`_) - All tokens are URL safe, removing the ``url_safe`` parameter from ``generate_csrf``. (`#206`_) - All tokens store a timestamp, which is checked in ``validate_csrf``. The ``time_limit`` parameter of ``generate_csrf`` is removed. - Remove the ``app`` attribute from ``CsrfProtect``, use ``current_app``. (`#264`_) - ``CsrfProtect`` protects the ``DELETE`` method by default. (`#264`_) - The same CSRF token is generated for the lifetime of a request. It is exposed as ``g.csrf_token`` for use during testing. (`#227`_, `#264`_) - ``CsrfProtect.error_handler`` is deprecated. (`#264`_) - Handlers that return a response work in addition to those that raise an error. The behavior was not clear in previous docs. - (`#200`_, `#209`_, `#243`_, `#252`_) - Use ``Form.Meta`` instead of deprecated ``SecureForm`` for CSRF (and everything else). (`#216`_, `#271`_) - ``csrf_enabled`` parameter is still recognized but deprecated. All other attributes and methods from ``SecureForm`` are removed. (`#271`_) - Provide ``WTF_CSRF_FIELD_NAME`` to configure the name of the CSRF token. (`#271`_) - ``validate_csrf`` raises ``wtforms.ValidationError`` with specific messages instead of returning ``True`` or ``False``. This breaks anything that was calling the method directly. (`#239`_, `#271`_) - CSRF errors are logged as well as raised. (`#239`_) - ``CsrfProtect`` is renamed to ``CSRFProtect``. A deprecation warning is issued when using the old name. ``CsrfError`` is renamed to ``CSRFError`` without deprecation. (`#271`_) - ``FileField`` is deprecated because it no longer provides functionality over the provided validators. Use ``wtforms.FileField`` directly. (`#272`_) .. _`#200`: pallets-eco/flask-wtf#200 .. _`#209`: pallets-eco/flask-wtf#209 .. _`#216`: pallets-eco/flask-wtf#216 .. _`#227`: pallets-eco/flask-wtf#227 .. _`#239`: pallets-eco/flask-wtf#239 .. _`#243`: pallets-eco/flask-wtf#243 .. _`#252`: pallets-eco/flask-wtf#252 .. _`#264`: pallets-eco/flask-wtf#264 .. _`#271`: pallets-eco/flask-wtf#271 .. _`#272`: pallets-eco/flask-wtf#272 Version 0.13.1 -------------- Released 2016/10/6 - Deprecation warning for ``Form`` is shown during ``__init__`` instead of immediately when subclassing. (`#262`_) - Don't use ``pkg_resources`` to get version, for compatibility with GAE. (`#261`_) .. _`#261`: pallets-eco/flask-wtf#261 .. _`#262`: pallets-eco/flask-wtf#262 Version 0.13 ------------ Released 2016/09/29 - ``Form`` is renamed to ``FlaskForm`` in order to avoid name collision with WTForms's base class. Using ``Form`` will show a deprecation warning. (`#250`_) - ``hidden_tag`` no longer wraps the hidden inputs in a hidden div. This is valid HTML5 and any modern HTML parser will behave correctly. (`#217`_, `#193`_) - ``flask_wtf.html5`` is deprecated. Import directly from ``wtforms.fields.html5``. (`#251`_) - ``is_submitted`` is true for ``PATCH`` and ``DELETE`` in addition to ``POST`` and ``PUT``. (`#187`_) - ``generate_csrf`` takes a ``token_key`` parameter to specify the key stored in the session. (`#206`_) - ``generate_csrf`` takes a ``url_safe`` parameter to allow the token to be used in URLs. (`#206`_) - ``form.data`` can be accessed multiple times without raising an exception. (`#248`_) - File extension with multiple parts (``.tar.gz``) can be used in the ``FileAllowed`` validator. (`#201`_) .. _`#187`: pallets-eco/flask-wtf#187 .. _`#193`: pallets-eco/flask-wtf#193 .. _`#201`: pallets-eco/flask-wtf#201 .. _`#206`: pallets-eco/flask-wtf#206 .. _`#217`: pallets-eco/flask-wtf#217 .. _`#248`: pallets-eco/flask-wtf#248 .. _`#250`: pallets-eco/flask-wtf#250 .. _`#251`: pallets-eco/flask-wtf#251

bsdhsr closed this as completed Mar 13, 2021

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

www/nginx: segfault when sendfile is enabled [spdy module] #201

www/nginx: segfault when sendfile is enabled [spdy module] #201

bsdhsr commented Jun 8, 2014

mamash commented Jun 9, 2014

bsdhsr commented Jun 9, 2014

www/nginx: segfault when sendfile is enabled [spdy module] #201

www/nginx: segfault when sendfile is enabled [spdy module] #201

Comments

bsdhsr commented Jun 8, 2014

mamash commented Jun 9, 2014

bsdhsr commented Jun 9, 2014