Add python 3 support

This release adds support for python 3. Python 2.7 still works, but should not be used anymore and is unlikely to be supported in further versions.

Note that pika must now be 1.0.1 or 1.1.0. Older pika is not supported anymore.

(The last versions were only released on pypi, and not here.)

esgf-pid 0.7.11

• pins pika to v0.11.2
• adapted connector behaviour and tests to reflect changes in pika API

Beta release 0.7.8

Changes since 0.7.7:

Functional improvements:

• None (release 0.7.8 was only necessary, as there was some changes that got lost on their way from the devel to the releases branch, and it is not possible to submit a fixed 0.7.7 to pypi, so we had to increase the version number).

Changes since 0.7.6:

Fixes

• Fixed a missing argument that caused a problem in very rare error cases (i.e. if the first RabbitMQ instance lacks the correct exchange, and the library then tries to reconnect to another one), which led to a stacktrace being printed, and which might have lead to lost messages if the config if the next RabbitMQ lacks the fallback exchange. All this is very unlikely to happen.

Note: There is no release for 0.7.7, which was only released on pypi/via pip.

Beta release 0.7.6

Changes since 0.7.5:

Functional improvements:

• Command line tool now also supports specifying ports and virtual hosts.

Usability improvements:

• The exceptions thrown if the library gives up connecting now specifies which were the problems that occurred whith the particular RabbitMQ nodes.

Fixes for very unlikely, very unexpected situations:

• Prevent sending messages to fallback exchange in a very unlikely situation: If sending messages to the normal and to the fallback exchange fails, messages are now sent to the normal exchange after reconnecting to the next host (before, it would stick to retrying the fallback exchange on the next host).
• Prevent infinite reconnection attempts (until publisher close) in a very unlikely situation: If none of the RabbitMQ nodes offered the correct exchange or fallback exchange.

Changes since 0.7.3:

Functional improvements/fixes:

• SSL can now be used.
• Virtual hosts can now be used.
• Ports can now be specified.
• For all these optional RabbitMQ options: Passing None leads to using the pika defaults (as before), passing an empty string equals to passing None. The arguments are checked for proper types before used.
• Command line tool now can handle special chars in passwords.
• Sychronous connection is now supported. Asynchronous connection stays the default.
• Detail bug fixes for uncommon situations

Usability improvements:

• Unit tests: Slow tests may be skipped using -ls

Note: There is no release for 0.7.4 and 0.7.5, which were only released on pypi/via pip.

Beta release 0.7.3

Changes since 0.7.1:

• Throw PIDException to publisher on reconnection failure even if publisher has called close in the meantime.
• Make sure that force finish interrupts the cycle of reconnection attempts.
• Gentle-closing algorithm stops after force-finish.
• Make sure that enough publishes are triggered, even if events are not processed correctly during reconnect.

Note: There is no release for 0.7.2, which is technically the same as 0.7.3.

Beta release 0.7.1

Changes since 0.7.0:

• If the exchanges do not exist on one host, try to connect to the next one, instead of failing completely.

Beta release 0.7.0

Changes since 0.6.3:

Functionality:

• Added reconnection in case of authentication and other problems.
• Raise an exception if we give up connecting, because all hosts failed.
• Decreased the number of times we try connecting.

Bug fixes:

• Avoid to continue trying to reconnect if the publisher has closed the library

Beta release 0.6.3

Changes since 0.6.2.:

• Fixed bug in priorities (they were not passed on from to the esgfpid.rabbit module).
• Some documentation and unit test improvement

Beta release 0.6.2

This release fixes some bugs in dealing with various RabbitMQ instances.

Beta-release 0.6.0

This release fixes a problem that occurs with data carts in case there is only one dataset in a cart. In that case, prior versions created the same handle string for the cart as for the dataset itself.