Re: [Twisted-Python] How to determine whether transport.write() succeed?

2013-04-03 Thread Todong Ma
Ok, will try AMP thank you very much! On Mon, Apr 1, 2013 at 3:49 PM, Glyph wrote: > > On Mar 31, 2013, at 6:09 PM, Todong Ma wrote: > > I wrote a simple client and server to get system information (e.g. cpu, > memory, etc.) > Client send 'cpu' to the server, then server will return cpu's inf

[Twisted-Python] Twisted 13.0.0 released

2013-04-03 Thread Thomas Hervé
On behalf of Twisted Matrix Laboratories, I am pleased to announce the release of Twisted 13.0. Among the 70 tickets closed, we can see: * A new "Introduction to Deferreds" document that you can find here: http://twistedmatrix.com/documents/13.0.0/core/howto/defer-intro.html * A fix in twisted

Re: [Twisted-Python] Current callback best practices

2013-04-03 Thread Hynek Schlawack
Am 02.04.2013 um 16:32 schrieb Glyph : >> My question can be simplified to: Closures yes or no? > "As appropriate". I had that coming. :) […] Thanks for your verbose explanations! >> If “yes, closures”: Still using cb/eb prefixes? I don’t see them very often >> in recent examples. What about

Re: [Twisted-Python] twisted.cred interface deficiences

2013-04-03 Thread Kevin Horn
On Tue, Apr 2, 2013 at 6:04 PM, Glyph wrote: > > On Apr 1, 2013, at 2:34 PM, Shell wrote: > > I propose that IUsernamePassword should be split into at least two > interfaces: > > * IUsernamePassword, with only username and password, no methods, > which allows password to be used in any way > * A

[Twisted-Python] Release questions

2013-04-03 Thread Thomas Hervé
Hey everyone, During the latest release process, I was left with several things to clarify, so now that it's done I think it's time: * We started building wheels for Windows. What do we do with me, should we upload it to pypi? What happens when users try them? * Glyph mumbled something about s

Re: [Twisted-Python] Release questions

2013-04-03 Thread Laurens Van Houtven
On Wed, Apr 3, 2013 at 6:14 PM, Thomas Hervé wrote: > * Glyph mumbled something about sha sums of the release files, instead > of md5. Should we pursue that? We may need to update some trac > integration code. > Depends, what's the goal of the checksums? If it's "we want people to be able to ch

Re: [Twisted-Python] Release questions

2013-04-03 Thread byr sa
On Wed, Apr 3, 2013 at 9:14 AM, Thomas Hervé wrote: > * Glyph mumbled something about sha sums of the release files, instead > of md5. Should we pursue that? We may need to update some trac > integration code. > > +1 for SHA-256 or SHA-512. High profile collision attacks against MD5 have happene

Re: [Twisted-Python] Release questions

2013-04-03 Thread exarkun
On 04:36 pm, _...@lvh.cc wrote: >On Wed, Apr 3, 2013 at 6:14 PM, Thomas Hervé wrote: >> * Glyph mumbled something about sha sums of the release files, >>instead >>of md5. Should we pursue that? We may need to update some trac >>integration code. > >Depends, what's the goal of the checksums? If i

Re: [Twisted-Python] Twisted 13.0.0 released

2013-04-03 Thread Glyph
On Apr 3, 2013, at 4:11 AM, Thomas Hervé wrote: > On behalf of Twisted Matrix Laboratories, I am pleased to announce the > release of Twisted 13.0. Thank you Thomas for managing yet another excellent release! > Among the 70 tickets closed, we can see: > > * A new "Introduction to Deferreds" do

Re: [Twisted-Python] Current callback best practices

2013-04-03 Thread Glyph
On Apr 3, 2013, at 4:25 AM, Hynek Schlawack wrote: > So you’re cool with calling callbacks after the event that triggered? That > would’ve been my second question but I didn’t want it to divert the > discussion. I kind of like `onData` et al too but the Twisted examples rather > shun it. The

Re: [Twisted-Python] Release questions

2013-04-03 Thread Glyph
On Apr 3, 2013, at 9:14 AM, Thomas Hervé wrote: > Hey everyone, > > During the latest release process, I was left with several things to > clarify, so now that it's done I think it's time: > > * We started building wheels for Windows. What do we do with me, should > we upload it to pypi? What

Re: [Twisted-Python] Release questions

2013-04-03 Thread Laurens Van Houtven
On Wed, Apr 3, 2013 at 10:51 PM, wrote: > The question relates to step 4 beneath "Cut the tarballs & installers": > > http://twistedmatrix.com/trac/wiki/ReleaseProcess#Cutthetarballsinstallers > > The checksums are intended to let people verify their download was > neither accidentally corrupted

Re: [Twisted-Python] Twisted 13.0.0 released

2013-04-03 Thread Laurens Van Houtven
Yay! Thanks, Thomas and everyone who contributed to this release :) On Wed, Apr 3, 2013 at 1:11 PM, Thomas Hervé wrote: > On behalf of Twisted Matrix Laboratories, I am pleased to announce the > release of Twisted 13.0. > > Among the 70 tickets closed, we can see: > > * A new "Introduction to

Re: [Twisted-Python] Release questions

2013-04-03 Thread Glyph
On Apr 3, 2013, at 1:51 PM, exar...@twistedmatrix.com wrote: > On 04:36 pm, _...@lvh.cc wrote: >> On Wed, Apr 3, 2013 at 6:14 PM, Thomas Hervé wrote: >>> * Glyph mumbled something about sha sums of the release files, >>> instead >>> of md5. Should we pursue that? We may need to update some trac

Re: [Twisted-Python] Release questions

2013-04-03 Thread Laurens Van Houtven
On Thu, Apr 4, 2013 at 12:04 AM, Glyph wrote: > The release manager already _does_ sign something. Since PyCon, we do > have much better trust web integration, which is great, but that's not > really relevant to this discussion, which is just about changing what we > sign and how it gets signed.

Re: [Twisted-Python] Release questions

2013-04-03 Thread Glyph
On Apr 3, 2013, at 3:23 PM, Laurens Van Houtven <_...@lvh.cc> wrote: > On Thu, Apr 4, 2013 at 12:04 AM, Glyph wrote: > The release manager already _does_ sign something. Since PyCon, we do have > much better trust web integration, which is great, but that's not really > relevant to this discu

Re: [Twisted-Python] Release questions

2013-04-03 Thread Tristan Seligmann
On Wed, Apr 3, 2013 at 11:58 PM, Laurens Van Houtven <_...@lvh.cc> wrote: > Is the accidental corruption thing a real risk? I thought that was the > point of, say, TCP checksums :) Perhaps I'm just mistaken as to how often > his happens in the wild... > TCP checksums don't protect you against cor