Mailman 3 March 2016 - Twisted

[Twisted-Python] how to implement login form logic with twisted.cred checkers, credentials and portal
by snailcoder 27 Mar '16

27 Mar '16

2 3

[Twisted-Python] where can I find twisted.application.internet.ClientService?
by Gelin Yan 26 Mar '16

26 Mar '16

Hi All In twisted doc, I noticed there is a class called "twisted.application.internet.ClientService" but the link https://twistedmatrix.com/documents/16.0.0/api/twisted.application.internet… is invalid. I couldn't find it out in twisted src (16.0.0) also. I want to know its availability. Regards gelin yan

2 2

[Twisted-Python] Twisted 16.1.0 Prerelease 1 Announcement
by Amber "Hawkie" Brown 25 Mar '16

25 Mar '16

Hi everyone, Another Twisted release is upon us -- this one is small, but has some nice to haves. In this release is: - twisted.application.internet.ClientService, a service that maintains a persistent outgoing endpoint-based connection -- a replacement for ReconnectingClientFactory that uses modern APIs; - A large (77% on one benchmark) performance improvement when using twisted.web's client on PyPy; - A few conch modules have been ported, in preparation for further porting of the SSH functionality; - Full support for OpenSSL 1.0.2f and above; - t.web.http.Request.addCookie now accepts Unicode and bytes keys/values; - `twistd manhole` no longer uses a hard-coded SSH host key, and will generate one for you on the fly (this adds a 'appdirs' PyPI dependency, installing with [conch] will add it automatically); - Over eighteen tickets overall closed since 16.0. As usual, you can get the NEWS file at https://twistedmatrix.com/Releases/pre/16.1.0pre1/NEWS.txt and download the tarball from https://twistedmatrix.com/Releases/pre/16.1.0pre1/. Please test this release with your applications, and let me know if all goes smoothly. If there's no reported issues, the release will occur in roughly a week. - Amber

1 0

[Twisted-Python] Ticket #8244 (old-style decorator)
by L. Daniel Burr 23 Mar '16

23 Mar '16

Hi all, I tried to comment on the ticket, but SpamBayes rejected it as spam. As a person who runs twisted apps via Pypy whenever possible, I wanted to point out that this ticket may result in a performance regression: according to http://pypy.org/performance.html, "Classes that inherit from both new- and old-style classes are extremely slow; avoid at all costs." Thanks, Daniel -- L. Daniel Burr ldanielburr(a)me.com (312) 656-8387

4 8

[Twisted-Python] Sending disconnect messages to clients
by Chris Norman 22 Mar '16

22 Mar '16

Hi all, I'm sure I asked this question before, but I can't find any answers on google, and I've changed my work flow a bit now, so thought it was worth re-asking. So on my server's protocol, I have a send method. This allows me to pass arguments which get sent off to the client in the right format. The send method looks something like this: def send(self, command, **kwargs): """Cause the client to issue getattr(connection, command)(**kwargs). If disconnect evaluates to True, disconnect the client after the message is sent.""" disconnect = kwargs.get('disconnect', False) try: del kwargs['disconnect'] except KeyError: pass # Argument not found. d = defer.Deferred() d.addCallback(self.prepare_command) Convert the command and kwargs to json. d.addCallback(self.deferred_write) # Write the json to the transport. if disconnect: d.addCallback(self.deferred_disconnect) # Issue self.transport.loseConnection(). reactor.callFromThread(d.callback, [command, kwargs]) # Call the deferred's callback chain. return d # Return the deferred. If I try something like: protocol.send('alert', message = '*** Disconnected. ***', disconnect = True) the client gets disconnected, but never sees the "*** Disconnected. ***" message. I guess I could do a reactor.callLater and just wait for the transport to get the message, but that seems sloppy, and I can't help thinking there must be something I'm missing. Any ideas welcome! Cheers all,

2 4

[Twisted-Python] pyOpenSSL 16.0.0 released
by Hynek Schlawack 19 Mar '16

19 Mar '16

On behalf of PyCA – the Python Cryptography Authority – I’m anxious to announce that after almost a year since the 0.15.1 release of pyOpenSSL we’ve released the brand new 16.0.0. A few organizational notes: 1. The pyopenssl-users mailing list and #pyopenssl IRC channel are deprecated. Please use cryptography-dev <https://mail.python.org/pipermail/cryptography-dev/> and #cryptography-dev on Freenode where you’re much more likely to get help. 2. The version scheme switched to CalVer because a 0.x version for a 15 years old project is rather odd and calling it 1.0 although we don’t expect a 2.0 to ever happen didn’t make any sense. pyOpenSSL is a long-running project with strict backward-compatibility requirements and is hence better served with a calendar-based version scheme. 3. Please note that some of us will be doing a TLS/HTTPS workshop at PyCon US 2016 so if you always wanted to learn about these things first hand, make sure to sign up: <https://us.pycon.org/2016/schedule/presentation/1786/>. We've opted to receive no compensation and asked the organizers to send them to PyLadies instead. So you’ll be doing good while learning something! *** Release details: While the list of changes looks short, a lot internal work happened: 72 files changed, 15511 insertions(+), 15063 deletions(-) We’ve done our best to not break any existing applications; including by making the urllib3 and Twisted test suites part of our CI. The full changelog can be found at <https://pyopenssl.readthedocs.org/en/stable/changelog.html>. This is the first release under full stewardship of PyCA. We have made many changes to make local development more pleasing. The test suite now passes both on Linux and OS X with OpenSSL 0.9.8, 1.0.1, and 1.0.2. It has been moved to py.test, all CI test runs are part of tox and the source code has been made fully flake8 compliant. We hope to have lowered the barrier for contributions significantly but are open to hear about any remaining frustrations. Backward-incompatible changes: • Python 3.2 support has been dropped. It never had significant real world usage and has been dropped by our main dependency cryptography. Affected users should upgrade to Python 3.3 or later. Deprecations: • The support for EGD has been removed. The only affected function OpenSSL.rand.egd() now uses os.urandom() to seed the internal PRNG instead. Please see pyca/cryptography#1636 for more background information on this decision. In accordance with our backward compatibility policy OpenSSL.rand.egd() will be removed no sooner than a year from the release of 16.0.0. Please note that you should use urandom for all your secure random number needs. • Python 2.6 support has been deprecated. Our main dependency cryptography deprecated 2.6 in version 0.9 (2015-05-14) with no time table for actually dropping it. pyOpenSSL will drop Python 2.6 support once cryptography does. Changes: • Fixed OpenSSL.SSL.Context.set_session_id, OpenSSL.SSL.Connection.renegotiate, OpenSSL.SSL.Connection.renegotiate_pending, and OpenSSL.SSL.Context.load_client_ca. They were lacking an implementation since 0.14. #422 • Fixed segmentation fault when using keys larger than 4096-bit to sign data. #428 • Fixed AttributeError when OpenSSL.SSL.Connection.get_app_data() was called before setting any app data. #304 • Added OpenSSL.crypto.dump_publickey() to dump OpenSSL.crypto.PKey objects that represent public keys, and OpenSSL.crypto.load_publickey() to load such objects from serialized representations. #382 • Added OpenSSL.crypto.dump_crl() to dump a certificate revocation list out to a string buffer. #368 • Added OpenSSL.SSL.Connection.get_state_string() using the OpenSSL binding state_string_long. #358 • Added support for the socket.MSG_PEEK flag to OpenSSL.SSL.Connection.recv() and OpenSSL.SSL.Connection.recv_into(). #294 • Added OpenSSL.SSL.Connection.get_protocol_version() and OpenSSL.SSL.Connection.get_protocol_version_name(). #244 • Switched to utf8string mask by default. OpenSSL formerly defaulted to a T61String if there were UTF-8 characters present. This was changed to default to UTF8String in the config around 2005, but the actual code didn't change it until late last year. This will default us to the setting that actually works. To revert this you can call OpenSSL.crypto._lib.ASN1_STRING_set_default_mask_asc(b"default"). #234 *** For PyCA, Hynek Schlawack

1 0

[Twisted-Python] Crossbar.io / AutobahnPython 0.13.0
by Tobias Oberstein 18 Mar '16

18 Mar '16

Hi, we've released Crossbar.io and AutobahnPython 0.13.0, running on Twisted 16.0.0 and PyPy 5.0. Get it here: Source: * https://github.com/crossbario/crossbar * https://github.com/crossbario/autobahn-python Python Packages: * https://pypi.python.org/pypi/crossbar * https://pypi.python.org/pypi/autobahn Binary Packages (recommended) * http://crossbar.io/docs/Local-Installation/ The binary packages contain a complete, self-contained, optimized Crossbar.io with everything - including PyPy 5.0, and of course based on Twisted 16.0.0! These packages are available for Ubuntu, FreeBSD and CentOS. (thanks to Hawkie, Miss Amber Brown - she made that happen;) ) Cheers, /Tobias

1 0

[Twisted-Python] Client Application service.Service
by Tim Hughes 17 Mar '16

17 Mar '16

Hi all, I am looking into twisted for writing a client application (bot style) and most of the examples I find are for server style applications. Looking at the finger example and https://github.com/jdavisp3/twisted-intro/blob/master/twisted-server-3/fast… I am just wondering where is best to put my application logic. The protocol is basically a ascii line style application It feels to me that my Service should be the core and the protocol should just be something like def send_mesage(message): Tim Hughes mailto:thughes@thegoldfish.org

2 3

[Twisted-Python] Cannot perform IPv6 Link-Local Multicast on Twisted
by Shantanoo Desai 16 Mar '16

16 Mar '16

I am trying to use the .joinGroup() by passing the IPv6 link-local multicast add. ff02::1 but get DNS lookup failure error. I am trying to use the UDP multicast example on the twistedmatrix.com website and simply replacing the IPv4 multicast address with the IPv6 one. I have also posted a query on StackOverflow: http://stackoverflow.com/questions/36034258/ipv6-link-local-multicast-on-tw… I am newbie on Twisted and some suggestions would be appreciated. Thanks a lot Shan Shantanoo Desai (Shan Desai)

2 1

[Twisted-Python] How to get the class of the wrapped fget/fset property methods
by Adi Roiban 16 Mar '16

16 Mar '16

The @deprecated decorator (at leas on py2.7) does not work when paired @property For deprecated instance variables, our deprecation policy recommend converting them into properties and emitted the warning from there. It would be nice if we could use the standard @deprecated decorator here. The problem is that when property are used the fget/fset are received by the @deprecated wrapper as functions and not as methods Is there a way to get the class in which a property is defined... or there is no way to use the @deprecated decorator with the @property .. and we should create a dedicated deprecatedMember method which is called as a normal method. Thanks! -- Adi Roiban

2 5