python-raet-0.6.4-bp151.3.1

- Updated to 0.6.4
  - Fixed issue with windows errno Minor corrections Fixed imports of ioflo
  to be compat with ioflo 1.2.3 Removed unused imports and normalized some imports
  - fixed the date in the copyright

- Updated to 0.6.3
  - Changed imports ioflo.base.nonblocking to be compat with ioflo 1.2.1

- Updated to 0.6.1
  - Updated tutorial fixed log message
  - Added enum support using python 3.4 enums via backport enum34 raeting.py NamedTuples replaced with enums
  - Added tutorial documents Fixed merge error Fixed bugs
  - Updated setup.py dependencies
  - Added python-argparse as depency for python < 2.7
  - Windows impossible file check More coverage tests
  - Python3 support
  - Added support for burst size limits in the Message transaction to deal with limits on UDP receive buffers
    on some hosts. Significant changes to how the Messenger and Messagent transactions work.
  - Added more units tests for messaging.

- Updated to 0.4.6
  - Changed semantics for initial alived state. As soon as estate completes initial bootstrap
  to allowed state it is also alived instead of waiting for manage alive transactions to complete.
  This enables messaging to commence immediately upon allowed.
  - Compatibility with ioflo 1.1.5
  - Support for simultaneous vacuous joins between same two estates Correctly terminates
  one of the joins and allows other to complete Bugfixes More tests
  - Silently handles errno.ECONNRESET on transmit in Stack._handleOneTx for windows

- Updated to 0.4.2
  - Changed the allow transaction to bigendian structs not little endian.\
    This will break interoperability with older versions of raet.
    Msgpack is already bigendian and future binary packet header for raet should be big endian.
  - fixed windows compat for autoaccept yard

- Updated to 0.3.6
  - Made default timeout for Messenger and Messengent transaction to be 0.0, that is, never
  - Added timout parameter to RoadStack.transmit() so timeout can be set on a message transaction by transaction basis
  - Added timeout to txMsgs deque triple for RoadStack that is, (msg, uid, timeout)
  - Fixed bug in RoadKeep.loadRemoteRoleData()
  - Added socket error handling for additional failure modes in Stack._handleOneTx for sending
  - Fixed Python3 incompatabilities

- Major update to 0.3.2
  - Fixed bug in allow transaction that prevented allow on restart Fixed issue with unicode fqdn on debian
  - New support for peer RAET channel. Changed semantics of how Join transactions works.
    This will allows peer to peer joining

- Updated to 0.2.12
  0.2.11 release:
  - Lookup remote in stack handleOneRx by using packet.index since it already substitutes
    ha if se is zero. Then also lookup remote in haRemotes if not found in .uidRemotes
  - Update joinent transaction
  - Change the way persistence reaping is handled. Instead of removing remote from memory,
    mark it with .reaped attribute. This avoide problematic use case of having to restoreRemote
    from disk when doing lookup in Joinent. Update .manage
  - Also unreap anytime a packet is received from a remote
  0.2.10 release:
  - Transactions now referenced and processed per remote not at stack.transactions sets
    stage for later doing broadcast transactions
  0.2.9 release:
  - Finished support for role keep files in Road
  0.2.8 release:
  - Support for msgpack in Keep files more support for role in Road estates fixes in join transaction
  0.2.7 release:
  - bugfix
  0.2.6 release:
  - If verify keep fails then clear the keep file. This autoclears cache when upgrading format of
    keep file. Also more support for role.
  0.2.5 release:
  - Refactored odicts indexing access attributes for remotes so can now access by uid, by name, or by ha.
  - Updated associated accessors Provides more consistent view onto Stack Road or Lane Prepatory to adding
    remote.role for key management

- Updated to 0.2.4
  - Fixed race condition in Yarding makedirs
  - Road Keep files are now stored by name not uid

- Updated to 0.2.3
- Added parameter to verify keep to allow passing in verify fields
- 0.2.2 release:
- refactor nack handling refactor moveRemote, removeRemote, renameRemote

- Updated to 0.2.1
- Change rsMsgs queue for LaneStack to be duple of (msg, name)
  where msg is message body dict and name is name of remote that sent the message
  this will enable authoization at the application layer
- 0.2.0 release:
- Ephemeral Lane Yards Yards now use a uuid for the session id so that there is no
  need to persist any Lane data in order to resolve ambiguous multi-page messages
  should one side restart in the middle of a multi-page message. No more keep for LaneStack.

- Updated to 0.1.2
  - Fixed bug in nacling catching wrong exception on verify
  Changed rxMsgs queue to be duple of (msg, name) so that application layer has access to remote name that sent the msg.
  - Added nacling.uuid function to allow unique yard names

- Major release 0.1.0
  - Minor fixup prepping for release with SaltStack Release Candidate

- Updated to version 0.0.31:
  - Fixed roadstack .manage method to used aliveds
- From versions in between
  - No longer removes rejected remotes out of band or future presence expire mechanism is needed to
  remove rejected remotes 0.0.30
  - Fixed a bug on renew in Joiner transaction 0.0.29
  - Fixed some race conditions 0.0.28
  - Support for reaping and restoring dead remotes on main estate road stack Support for saving and
  resending stale messages when session changes on rejoin or reallow Some other fixes 0.0.27
  - RoadStack.manage now provide underlying support needed for presence events and filtering of remote
  targets based on availabilty (allowed) status 0.0.26

- Updated to version 0.0.25
  fix install_requirements error

- updated to version 0.0.23

- Update to version 0.0.19

- Initial package version 0.0.18