See the release procedure section for more details on version numbering and how releases are made.
- 2.0.1 (2016-03-17) [Download]
Remove incorrect calls to old (pre-2.0.0) logging API. Thanks to Tim-Oliver Husser & Tim Staley.
Reformat documentation to add Acknowledgements.
- 2.0.0 (2016-01-31) [Download]
$TMPDIRenvironment variable, if set, to store the event database. Otherwise, fall back to
Drop support for Python 2.6, following the same change made in Twisted.
Improve checking for valid IVORNs.
Some extremely old versions of Comet (dating from before the 1.0.0 release) used a different format for the database of seen events. All released versions through 1.2.2 automatically update old-style databases to the new format when run. As of this release, this support for legacy databases has been dropped. It is necessary to use a previous Comet release to update the database format before upgrading to this version.
Refactor the codebase caused a minor API change: logging facilities are now available from the
comet.logmodule. End user code — notably event handling plugins — should replace statements to the effect of
from comet.utility import logwith
import comet.log as log. The convenience aliases
log.warninghave been removed: use
- 1.2.2 (2015-04-20) [Download]
Disable XML entity expansion for documents received from the network. This eliminates a class of potential resource exhaustion attacks.
Update documentation to request citation of the paper in published work which makes use of Comet.
- 1.2.1 (2014-09-02) [Download]
- Correctly check that the (required)
--local-ivocommand line option was provided (GitHub #35).
- 1.2.0 (2014-08-26) [Download]
When subscribing to a remote broker, we wait for a short period after the initial connection is made before marking it as successful. This means that if the broker rapidly drops the connection (e.g. due to an authentication failure), we retry the connection with an exponential back-off rather than an immediate reconnection (GitHub #29).
iamalivemessages are marked as being in UTC.
authenticatemessages which specify XPath filters are schema compliant (GitHub #31).
Subscriber refuses to start if an XPath
--filteris specified with invalid syntax (GitHub #33).
Require that a valid IVOA identifier (IVORN) be supplied by the end user when starting Comet rather than relying on a default.
Require that events submitted to the broker by authors have valid IVORNs.
- 1.1.2 (2014-08-26) [Download]
- Fix a bug which could result in malformed event IVORNs exhausting the available resources and ultimately rendering Comet unable to process more events (GitHub #34).
- 1.1.1 (2014-07-08) [Download]
Fix a bug which could result in the same VOEvent message being processed multiple times (GitHub #30).
Add compatibility with DBM-style databases which do not provide an
- 1.1.0 (2014-02-26) [Download]
Interval between broadcast test events is user configurable, and they may be disabled. See the
Test events now include details of the version of Comet used to generate them.
Event handler plugin system reworked. Plugins may now take command line options. See the event handler documentation for details. Note that the syntax for invoking the
print-eventhandler has changed (now
Plugin which writes events received to file (
- 1.0.4 (2013-11-13) [Download]
comet-sendvowill choose its Python interpreter based on the environment.
- 1.0.3 (2013-11-12) [Download]
requirements.txtis included in the distribution. This changes nothing on an installed system.
- 1.0.2 (2013-11-12) [Download]
- Add a
requirements.txtfile and specify the installation requirements in
setup.py. This makes installation easier, but changes nothing on an installed system.
- 1.0.1 (2012-08-28) [Download]
- Fix for badly formed XML
- 1.0.0 (2012-08-27) [Download]
- Initial public release
- Cryptographic authentication of VOEvent messages and subscribers.
- Port to Python 3.