Python binding for Project Tox.
PyTox provides a Pythonic binding, i.e Object-oriented instead of C style, raise exception instead of returning error code. A simple example is as follows:
class ToxOptions():
def __init__(self):
self.ipv6_enabled = True
self.udp_enabled = True
self.proxy_type = 0 # 1=http, 2=socks
self.proxy_host = ''
self.proxy_port = 0
self.start_port = 0
self.end_port = 0
self.tcp_port = 0
self.savedata_type = 0 # 1=toxsave, 2=secretkey
self.savedata_data = b''
self.savedata_length = 0
class EchoBot(Tox):
def __init__(self, opts):
super(EchoBot, self).__init__(opts)
def loop(self):
while True:
self.iterate()
time.sleep(0.03)
def on_friend_request(self, pk, message):
print 'Friend request from %s: %s' % (pk, message)
self.friend_add_norequest(pk)
print 'Accepted.'
def on_friend_message(self, friendId, message):
name = self.self_get_name(friendId)
print '%s: %s' % (name, message)
print 'EchoBot: %s' % message
self.friend_send_message(friendId, Tox.MESSAGE_TYPE_NORMAL, message)
As you can see callbacks are mapped into class method instead of using it the the c ways. For more details please refer to examples/echo.py.
To get started, a Makefile is provided to run PyTox inside a docker container:
make test
: This will launch tests in a container.make run
: This will launch an interactive container with PyTox installed.make echobot
: This will launch the example echobot in a container.
- echo.py: A working echo bot that wait for friend requests, and than start echoing anything that friend send.
Full API documentation can be read here.
- Complete API binding (use tools/apicomplete.py to check)
- Unittest for ToxAV
- Fork it
- Create your feature branch (
git checkout -b my-new-feature
) - Commit your changes (
git commit -am 'Add some feature'
) - Push to the branch (
git push origin my-new-feature
) - Create new Pull Request