Pyaxon

1. Date/time/datetime values should have prefix ``^``.
2. Move ``hsize`` argument of dumping functions and of Dump class __init__ method to the end.
3. Remove support for python ``3.2``.

1. Now date/time/datetime values have prefix ``^`` in order to be more explicit
(``12:00`` --> ``^12:00``, ``2010-12-31`` --> ``^2010-12-31``).
This change is important for adding support for more wider range of simple type values
for keys in dicts in the next version ``0.10``.
In 0.9.x loading of old notation of date/time/datetime values are allowed.
In ``0.10`` old notation will be removed.
In order to convert ``pyaxon`` text in safe mode to new date/time/datetime notation ``0.9``::

axon.dumps(axon.loads(text))
axon.dump(path, axon.load(path, text))

2. Add syntax reprsenting sets. For example::

{1 2 3}
{"a" "b" "c" "d"}

1. Fix dump of toplevel dict when sort=1.

1. Now node objects support access to subnodes using attribute access.
2. Now pyaxon support continues integration via appveyor.

1. Now name of complex value in formatted form without {} hasn't suffix ':'. For example::

person
name: "Alex"
age: 36

instead of::

person:
name: "Alex"
age: 36

2. Introduce used defined constants using ``defname(name, value)`` function.
Such names in ``AXON`` message always have ``$`` prefix (for example, ``$one``, ``$PI``).
3. Attributes of the ``Node`` objects are ``axon.OrederDict`` instance now to preserve order
of attributes.
4. Introduce new syntax for oredered dict: ``[... key:val ...]`` and ``[:]`` for empty ordered dict.
Later ``<>``-syntax for ordered dicts will be removed.
5. Extend ``AXON`` for converting text into ``axon.OrderedDict`` object
and dumping instances of ``collections.MutableMapping`` to text containing sequence
of ``key:val`` pairs.
For example::

name: "Alex"
age: 32
email: "mailexample.com"

will converted to ``axon.OrderedDict([('name','Alex'), ('age',32), ('email','mailexample.com')])``.

6. ``pyaxon`` now builds with MSVC.

1. Safe mode loading/dumping on named complex values are based on general ``Node`` objects.
2. Attributes in safe mode are represented as ``Attribute`` objects.
3. Named complex values are now sensitive to an order of containing values and attributes.
4. The protocol for unsafe loading/dumping of named complex values is changed.
5. Old safe mode loading/dumping are still here in the ``mode='safe_old'``