Mailman 3 October 2014 - Twisted

[Twisted-Python] Weekly Bug Summary
by trac＠twistedmatrix.com 12 Oct '14

12 Oct '14

1 0

[Twisted-Python] INCOMPATIBLE CHANGE: twisted.python.threadpool - time to test!
by Glyph 12 Oct '14

12 Oct '14

Again as per <https://twistedmatrix.com/trac/wiki/CompatibilityPolicy#ProcedureforExcepti…>, in order to conclude this discussion, I need to provide Twisted users with a branch to test their code against. Well, now you have it - and as per the policy you have a week from the sending of this message to register any objections :). The ticket <https://twistedmatrix.com/trac/ticket/2673> is in review now, and the branch is <desynchronize-2673-2>. Many of the existing tests used some of the compatibility features that we discussed previously, so I just left the existing tests intact. However, if you need any more compatibility features, please let me know and I can implement them in the branch. Feel free to reply here, or comment there. -glyph

2 2

[Twisted-Python] client logic
by Benjamin Schollnick 10 Oct '14

10 Oct '14

I’m sorry if this is a duplicate? I sent this earlier, but I don’t see it in the archives? Folks, I’m writing an client using twisted, and I’m basing it off the Poetry client from http://krondo.com/wp-content/uploads/2009/08/twisted-intro.html. I am porting a previous pyserial based client, so I’m running into new territory here. And it’s working fine, there are two “issues" that I am running into. class WT_Protocol(Protocol): tag = '' def to_bytes(self, seq): """convert a sequence to a bytes type""" # # from pyserial.util if isinstance(seq, bytes): return seq elif isinstance(seq, bytearray): return bytes(seq) elif isinstance(seq, memoryview): return seq.tobytes() else: b = bytearray() for item in seq: b.append(item) # this one handles int and str for our emulation and ints for Python 3.x return bytes(b) def connectionMade(self): print "Reseting the network" reset = self.to_bytes(packets.network_reset() ) self.transport.write ( reset ) self.transport.write ( self.to_bytes(packets.Set_SiteCode(NodeID=255, SC1=0, SC2=0, SC3=0) )) self.transport.write ( self.to_bytes(packets.Set_Gain_Packet(NodeID=255, Gain=1) )) # high gain self.transport.write ( self.to_bytes(packets.Set_Protocol_No_Nulls (NetworkID=0, ReceiverID=0, NodeID=1) )) # high gain time.sleep (.5) Now the client works right now, but I’m concerned that I can’t figure out how to immediately read for a reply packet from the server. For example, when I send the Set_SiteCode packet, I may receive a reply. But how would that occur in the Twisted framework? In my testing the dataReceived function is not being called, so I can’t trap it there, plus I’m not sure how I would figure that logic. Can anyone suggest a method to do this? The second question, as far as I can tell, isn’t very solvable. I’d like to add a “Press Q to quit” type logic to the code. But I don’t see a way to do this easily in twisted? (platform unspecific, but it’s running Mac OS X / Unix right now). - Ben

2 2

[Twisted-Python] a review to speed up other reviews?
by Glyph 09 Oct '14

09 Oct '14

<https://twistedmatrix.com/trac/ticket/7633> is keeping one of the buildbots persistently red. It's in review. There's some discussion on the ticket, If anyone has some free time to review it, this would make other code-reviews go just a little bit faster, since reviewers wouldn't need to keep looking at the logs for that builder to make sure that the failures are the "expected" ones; all the builders should be consistently green except for the pesky windows XP one. -glyph

3 6

[Twisted-Python] Boston Area Twisted Sprint
by exarkun＠twistedmatrix.com 08 Oct '14

08 Oct '14

Hello all, I'm happy to invite you to a Twisted sprint on Saturday, November 1st in Cambridge, Massachusetts. ClusterHQ will be hosting up to twenty (20) Twisted sprinters at the Cambridge Innovation Center ("Coronet City" room) in Kendall Square from 10AM until 11PM. The sprint topics are attendee choice - hacking on any part of Twisted is welcome. A large part of the ClusterHQ team will be taking part in the sprint. ClusterHQ is developing Flocker, a data management tool for use with Docker written in Python and based on Twisted. Follow us on Github: https://github.com/clusterhq/flocker ClusterHQ will provide lunch and dinner (something like delivery pizza, comment on the meetup page if you'd like to suggest something!). Find details and chat about sprint topics at the Boston Twisted Python meetup page: http://www.meetup.com/Boston-Twisted-Python/ Early birds, feel free to contact me off-list about meeting up for coffee at around 9AM before the sprint starts. Space at CIC is limited. Please RSVP on the Meetup page! See you there, Jean-Paul

1 0

[Twisted-Python] naming question before we end up committed...
by Glyph 08 Oct '14

08 Oct '14

While working on the package I just brought up in another thread, I realize we have another big new package coming in 14.1, "twisted.python.logger", and I'm wondering what the ".python" part of that package name is doing in there, and what value it adds. It's where "twisted.python.log" used to be, of course, but now I'm just wondering if we're just making the same mistake twice. Does anyone have an opinion on renaming it to "twisted.logger"? Or have a better suggestion? -glyph

5 5

[Twisted-Python] Client Logic
by Benjamin Schollnick 08 Oct '14

08 Oct '14

Folks, I’m writing an client using twisted, and I’m basing it off the Poetry client from http://krondo.com/wp-content/uploads/2009/08/twisted-intro.html. I am porting a previous pyserial based client, so I’m running into new territory here. And it’s working fine, there are two “issues" that I am running into. class WT_Protocol(Protocol): tag = '' def to_bytes(self, seq): """convert a sequence to a bytes type""" # # from pyserial.util if isinstance(seq, bytes): return seq elif isinstance(seq, bytearray): return bytes(seq) elif isinstance(seq, memoryview): return seq.tobytes() else: b = bytearray() for item in seq: b.append(item) # this one handles int and str for our emulation and ints for Python 3.x return bytes(b) def connectionMade(self): print "Reseting the network" reset = self.to_bytes(packets.network_reset() ) self.transport.write ( reset ) self.transport.write ( self.to_bytes(packets.Set_SiteCode(NodeID=255, SC1=0, SC2=0, SC3=0) )) self.transport.write ( self.to_bytes(packets.Set_Gain_Packet(NodeID=255, Gain=1) )) # high gain self.transport.write ( self.to_bytes(packets.Set_Protocol_No_Nulls (NetworkID=0, ReceiverID=0, NodeID=1) )) # high gain time.sleep (.5) Now the client works right now, but I’m concerned that I can’t figure out how to immediately read for a reply packet from the server. For example, when I send the Set_SiteCode packet, I may receive a reply. But how would that occur in the Twisted framework? In my testing the dataReceived function is not being called, so I can’t trap it there, plus I’m not sure how I would figure that logic. Can anyone suggest a method to do this? The second question, as far as I can tell, isn’t very solvable. I’d like to add a “Press Q to quit” type logic to the code. But I don’t see a way to do this easily in twisted? (platform unspecific, but it’s running Mac OS X / Unix right now). - Ben

2 1

[Twisted-Python] from: Cameron Dale
by Cameron Dale 08 Oct '14

08 Oct '14

Hiya http://minakow.ru/iron.php?pull=aqddrmtvcs3630rwfzrcp camrdale(a)gmail.com

1 0

[Twisted-Python] my branches merged by you (itamar)
by Wolfgang Rohdewald 05 Oct '14

05 Oct '14

Thanks for fixing my mistakes! Based on your fixes I started a personal checklist, see below. Is that list correct so far? (it will not include things I already did right) I noticed that you also changed 'x' to b'x' in some places. I did not do that yet because it is not needed for those tickets, I wanted to keep them small and focussed. Instead I am planning tickets for just that: (after minimizing the number of places to be fixed) twisted.spread.banana and tests: literal strings become bytes where appropriate twisted.spread.jelly and tests: define *_atom consistently for all atoms, change them to bytes twisted.spread.pb and tests: literal strings become bytes where appropriate The current checklist: Line length max. 79 *.rst doc: One line per sentence, no length limit fully qualified names in doc and news, twisted.* no __ in Twisted. Everything in a test case is private anyway. if possible __execute__ (not __define__) only one assert per test document changed API like raising more or different exceptions use new print() formatting syntax Document and isolate test code using the private API of the module to be tested. test everything with PY2.6 too did twistedchecker add new warnings? news: most frequent form: Qualified now does ... news about spread belong into twisted/topfiles doc: not pb but PB Epydoc docstring ends with point break docstring lines not sooner than needed avoid the word “test” in test docstrings do not use the “I am” form in docstrings test docstring: describe what happens, including exceptions doc: avoid mentioning the private API -- Wolfgang

2 4

[Twisted-Python] Weekly Bug Summary
by trac＠twistedmatrix.com 05 Oct '14

05 Oct '14

1 0