I am plannig to upgrade twisted's buildbot in the near future. In
preperation for that, I am going to take down the production buildbot
on Tuesday, June 26, around 1600 UTC.
During that time, the result of any builds done will be lost. Thus, I'd
ask that people avoid committing to trunk during that time.
I will send a reminder before I take down the buildbot both here, and on
#twisted and #twisted-dev.
hi there, folks:
I'd really like to release 0.7.0 but I would like it to be at least a
little bit tested before I do so. Could those of you with CVS trees check
everything out and see if it performs as advertised? Deeper bugs than
that will have to wait for the next release, but I'd at least like to know
if it works for someone other than me.
______ __ __ _____ _ _
| ____ | \_/ |_____] |_____|
|_____| |_____ | | | |
@ t w i s t e d m a t r i x . c o m
I would like to announce txZMQ, ZeroMQ bindings for Twisted. txZMQ is based
on pyzmq and requires recent ØMQ version (>=2.1).
txZMQ uses ØMQ APIs to get file descriptor that is used to signal pending
actions from ØMQ library IO thread running in separate thread. txZMQ should
be usable with any Twisted reactor.
* The socket library that acts as a concurrency framework.
* Carries messages across inproc, IPC, TCP, and multicast.
* Connect N-to-N via fanout, pubsub, pipeline, request-reply.
* Fast enough for clustered products and supercomputing.
* Asynch I/O for scalable multicore message-passing apps.
Bridging ØMQ and Twisted makes a nice match: fast simple messaging between
Twisted instances solving complex problems :)
* PyPi: http://pypi.python.org/pypi/txZMQ/
* Source code: https://github.com/smira/pyzmq
* pyzmq: http://pypi.python.org/pypi/pyzmq
* ØMQ: http://www.zeromq.org/
Qik Web Team Lead
I would like to announce the first release of txThings. It is a simple
for Constrained Application Protocol (CoAP). CoAP is a relatively new
designed for "Internet of Things" and M2M communications.
txThings currently implements a subset of CoAP features:
- standard messaging based on draft-ietf-core-coap-13 (no proxying support
- blockwise transfers based on draft-ietf-core-block-12
- limited suport for RFC6690 Core Link Format (for servers only)
I hope to add new features like Observe (draft-ietf-core-observe-09) soon.
TxThings is my first Twisted project, so the code quality can probably be
also better unit testing is necessary. However I decided to release the code
in its current form to discover, if there is any interest in it.
Internet of Things is currently very interesting field of development. It
a phase where many opportunities for both large and small players. I think
well suited for development of IoT apps:
- it's stable
- it's Python based and portable
- it has good support for UDP and TCP, which makes it ideal for proxying
IoT protocols to HTTP
In my opinion in the next three years, at least 20% of Twisted apps will be
(educated guess, no hard data :) )
There are many new protocols out there designed for IoT, in my opinion
CoAP and MQTT have the biggest chance of adoption. CoAP is developed by
and backed by companies like ARM.
You can download txThings from Github:
Few more remarks:
- txThings works on RaspberryPi (tested)
- txThings plays well with Kivy Python GUI Library http://kivy.org
Kivy is new GUI library that supports Twisted, and allows building apps for
Android and iOS - I've ran a few tests, and it's very promising :)
I need to limit the ciphers offered for an ssh/sftp connection.
"""Main local proxy class for file transfer access.
Many methods are overriden to support file encryption and
encrypted file name mappings.
def __init__(self, avatar):
"""Initialize class with avatar representing user information"""
I'm unclear as to how to restrict which ciphers to use at this level.
Ray Cote, President Appropriate Solutions, Inc.
We Build Software
I have raised the question of Windows XP support in Twisted earlier
today in #twisted-dev. Since the Microsoft "extended support" cut-off is
within six or so months, and there is continuing trouble with the
XP-based buildslave, I think it would be a good idea to get a figure of
how many Windows XP users there are currently using Twisted, so informed
decisions can be made in regards to supporting it.
If you use Twisted on Windows XP, please comment on ticket #6798 , so
we can get an idea of the usage numbers.
I'm working on #6749 for porting t.p.logfile to python3. I'm dealing with
some test failures, which you can see from the buildbot here:
I have pasted the relevant bit into a gist here:
I think what's happening is that LogFile.write should take native strings
(since that's what log.msg takes). However, I'm opening all files in binary
mode, since that's on the reviewer checklist (point 8) for the Python 3
Should I not open the files in binary mode?