Pyak47

***********************

* `v1.005 zip <http://multi-mechanize.googlecode.com/files/multi-mechanize_1.005.zip>`_

***********************

* `v1.004 zip <http://multi-mechanize.googlecode.com/files/multi-mechanize_1.004.zip>`_

***********************

* `v1.003 zip <http://multi-mechanize.googlecode.com/files/multi-mechanize_1.003.zip>`_

*************************

* first release of pyak47 (fork of multi-mechanize)
* Github: https://github.com/kakwa/pyak47
* renaming multimech-run and multimech-newproject to pyak47-run pyak47-newproject
* renaming the python module
* fix hard coded path to configuration in rpcserver.py
* documentation on http://pyak47.readthedocs.org

----

Prior release under the name of multi-mechanize

Version 1.?.?, 201?-??-??
*************************

* bug fixes
* tox config
* travis-ci config

***********************

* `v1.002 zip <http://multi-mechanize.googlecode.com/files/multi-mechanize_1.002.zip>`_

*************************

* initial release on PyPI (http://pypi.python.org/pypi/multi-mechanize)
* development moved to GitHub (http://github.com/cgoldberg/multi-mechanize)
* using Git for version control (pull requests welcome)
* new entry-point scripts (``multimech-run``, ``multimech-newproject``)
* new version numbering format
* new setup and packaging
* new documentation (sphinx generated)
* results re-processing (``-r``|``--results`` command line option)
* specify bind address in rpc-server mode (``-b``|``--bind-addr`` command line option)
* specify project directory location (``-d``|``--directory`` command line option)

----

Prior to version 1.2.0, Multi-Mechanize used a different version numbering format and was not packaged on PyPI.