Bug summary
__
Summary for 2009-08-09 through 2009-08-16
Bugs opened: 15Bugs closed: 3 Total open bugs: 1152 (+12)
|== Type Changes |== Priority Changes |== Component Changes
|Defect: +10 |Highest: -1 |Conch: +1
|Enhancement: +2 |H
I've noticed some behavior when negotiating TLS using startTLS(). I'm
starting TLS on both sides of the connection at the same time to validate
peer certificates using a custom callback. If I call startTLS() without
any subsequent writes to the socket the negotiation never completes.
However,
For some arcane reason, GMail (or maybe FireGPG) decided to mangle the
stuff in between commas. *sigh*
http://paste.pocoo.org/show/134450/
Laurens
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Not really a direct reply, but the following is big enough progress
that it warrants a minireport of its own. An excerpt from my test
suite running:
test_GSVSentences ...
, , , }>
, , , }>
, , }>
... meaning GSV sentences are now correctly parsed! :
Hi everyone,
for a project I'm working on I wanted to create a helper program which
can spawn an instance of itself as a separate process, slaving itself to
the spawner, and speaking PB to it.
The idea is that the master can spawn processes which will run code that
might segfault or otherwise beh
