version 4.18

git-svn-id: svn://svn.razorvine.net/Pyro/Pyro4/trunk@801 08cfa0ad-1c00-4aa0-9110-f4b10de7e716
remove hmac warning
add @oneway decorator

It doesn't work when creating a proxy directly in the client. It needs to get the object as a return from a call to the server.
add support for real async calls

Methods decorated with @isasync must return a Future.
The future is handled over the network efficiently.
The Future of the client gets called as soon as the Future in the server is finished, and
then the connection is automatically closed.
allow the user to define its own proxy for any type of object

This is done by adding entries to the Daemon.serializers dict:
Daemon.serializers[mytype] = myserializer

Where myserializer is a callable as defined by copyreg.
In practice, if you want your object to be remotely callable, the proxy should extend Pyro.Proxy
expose the oneway and isasync decorators direcly in Pyro4 module
add method on DaemonObject to obtain a remote object by ID

By using the daemon object obtained from Pyro4.Proxy("PYRO:Pyro.Daemon@localhost"),
it is now possible to receive an object with the proxy completely filled in for
oneways and asyncs.
add support for copying oneways and asyncs when doing a copy of a proxy
allow to change the default object provided by the daeamon
proxy: copy oneway and asyncs via state (instead of init)

This allows much clean extention. The init is almost empty, and duplicating a proxy or creating one is done via state
proxy: fix failure to unpickle when cyclic-depency

the unpiclker might call __hash__() before even initialising an object (in case of cyclic-dependency).
in such case __pyroUri doesn't exist, so __hash__() would fail, which is a pity.