Mailman 3 March 2011 - Twisted

[Twisted-Python] prerelease preview predocumentation
by Glyph Lefkowitz March 30, 2011

March 30, 2011

Dear Twistizens, Unfortunately, the Sphinx documentation didn't quite officially make the cut for the 11.0 release. Our release toolchain still needs updating, someone needs to review the rst sources, etc. Until all that's done, all documentation changes will still need to be Lore patches. Plus, I kinda hope that someone manages to get <http://tm.tl/2443> merged before we pull the trigger. However, we've been generating Sphinx output for quite a while, and quite a lot of work has gone into its presentation. It seems a pity to let that go to waste. So, while our official documentation remains at <http://twistedmatrix.com/documents/current/> (and that is the URL that will be updated when the release goes out), I've decided to host some un-official documentation with all the snazzy styling that Kevin Horn prepared for us here, to go with the pre-release that Jessica McKellar just announced: <http://twistedmatrix.com/~glyph/sphinx-preview-11.0pre1/> I know that there's some extraneous spacing; that will be fixed after the ReST sources make it to trunk, unless someone feels like fixing it in <https://bitbucket.org/khorn/lore2sphinx>. (Also, API documentation links for new features will be broken until the 11.0 API documentation is pushed to <http://twistedmatrix.com/documents/current/api/>.) However, this documentation snapshot should be otherwise usable, and I'm contemplating linking to it from the front page. Please be aware that this is not a stable URL, and any links to it will break after a while; I have no fixed schedule for taking it down, but it will definitely go away when the final documentation branch is merged. Otherwise, though, read documentation to your hearts' content. Share and Enjoy, -glyph

9 14

[Twisted-Python] EuroPython Call for Presentations
by Valentino Volonghi March 28, 2011

March 28, 2011

Introduction ------------------------ We're looking for proposals on every aspects of Python: programming from novice to advanced levels, applications and frameworks, or how you have been involved in introducing Python into your organisation. **First-time speakers are especially welcome**; EuroPython is a community conference and we are eager to hear about your experience. If you have friends or colleagues who have something valuable to contribute, twist their arms to tell us about it! Please also forward this Call for Papers to anyone that you feel may be interested. Important Deadlines ------------------- - April 6th, 2011: End of Call for Presentations. - April 11th, 2011: Start of community voting of talks. - April 17th, 2011: End of community voting of talks. - June 20th, 2011: EuroPython Conference Keynote Day. The end of the Call for Presentations is approaching. There is now only a little more than 1 week left before we stop accepting new presentation proposals for EuroPython. Don't wait the last minute to formalize a proposal for a presentation! Presenting at EuroPython ------------------------ We will accept a broad range of presentations, from reports on academic and commercial projects to tutorials and case studies. As long as the presentation is interesting and potentially useful to the Python community, it will be considered for inclusion in the programme. Can you show the conference-goers something new and useful? Can you show attendees how to: use a module? Explore a Python language feature? Package an application? If so, consider submitting a talk. Unfortunately, since EuroPython is a not-for-profit community conference, it is not possible to reward speakers (but what price on glory!). However, **speakers will benefit from a reduced conference fee**. Talks and hands-on trainings ---------------------------- There are two different kind of presentations that you can give as a speaker at EuroPython: * **Regular talk**. These are standard "talk with slides", allocated in slots of 45, 60 or 90 minutes, depending on your preference and scheduling constraints. A Q&A session is held at the end of the talk. * **Hands-on training**. These are advanced training sessions for a smaller audience (10-20 people), to dive into the subject with all details. These sessions are 4-hours long, and audience will be strongly encouraged to bring a laptop to experiment. They should be prepared with less slides and more source code. If possible, trainers will also give a short "teaser talk" of 30 minutes the day before the training, to tease delegates into attending the training. In the talk submission form, we assume that you intend to give a regular talk on the subject, but you will be asked if you are available for also doing a hands-on training on the very same subject. Speakers that will give a hands-on training are rewarded with a **free entrance** to EuroPython to compensate for the longer preparation required, and might also be eligible for a speaking fee (which we cannot confirm at the moment). Topics and goals ---------------- Specific topics for EuroPython presentations include, but are not limited to: - Core Python - Other implementations: Jython, IronPython, PyPy, and Stackless - Python libraries and extensions - Python 3.x migration - Databases - Documentation - GUI Programming - Game Programming - Network Programming - Open Source Python projects - Packaging Issues - Programming Tools - Project Best Practices - Embedding and Extending - Science and Math - Web-based Systems Presentation goals usually are some of the following: - Introduce audience to a new topic they are unaware of - Introduce audience to new developments on a well-known topic - Show audience real-world usage scenarios for a specific topic (case study) - Dig into advanced and relatively-unknown details on a topic - Compare different options in the market on a topic Inappropriate language and imagery ---------------------------------- EuroPython strongly believes in building a truly diverse community, and fully supports the official Python diversity statement[1]. Given a trail of negative experiences at previous tech conferences, all partecipants will be asked to agree to a code of conduct[2] that explicitly bans verbal and physical harassment at the conference, including talks. Speakers are thus required to avoid any kind of sexual, racist, or religious language or imagery in the talks, to avoid offending a diverse group that might be under-represented at the conference. Consider that EuroPython is a conference with a audience from a broad geographical area which spans countries and regions with vastly different cultures. What might be considered a "funny, inoffensive joke" in a region might be really offensive (if not even unlawful) in another. If you want to add humour, references and images to your talk, avoid any choice that might be offensive of a group which is diverse from yours. Italian Track ------------- Italy is home to a vibrant Python community that gathers together each year at the local PyCon Italia event (up to 400 delegates!). To acknowledge this reality in EuroPython and to encourage Italian pythoneers who suffer from the language barrier, we will hold an additional Italian track at EuroPython, containg only talks delivered in Italian. The talk submission form lets you choose the language you want to give the talk in. If you speak Italian and want to submit a talk for this special track, please go ahead and submit the talk title and abstract directly in Italian. If instead you are available to give the talk twice during EuroPython, in both languages, please make two different submissions for the same talk: one in Italian, and one in English. Community-based talk voting --------------------------- This year, for the first time in EuroPython history, the talk voting process is fully public. Every partecipant gains the right to vote for talks submitted during the Call For Papers, as soon as they commit to their presence at the conference by buying a ticket. See all the details in the talk voting[3] page. Contacts -------- For any further question, feel free to contact the organizers at info(a)pycon.it. Thank you! [1]: http://www.python.org/community/diversity/ [2]: http://ep2011.europython.eu/code-of-conduct [3]: http://ep2011.europython.eu/talk-voting -- Valentino Volonghi aka Dialtone Now Running MacOSX 10.6 http://www.adroll.com/

1 0

[Twisted-Python] TestCase methods names
by Facundo Batista March 27, 2011

March 27, 2011

Hello! The TestCase class, historically, provided several ways to do the same (I guess because we inherited the semantics from Java). For example, to check equality, In Python2 we have: * assertEquals * assertEqual * failUnlessEqual However, note that "assertEquals" was never documented (not in Python's TestCase, neither in Trial's one). In Python 3, the "There should be one-- and preferably only one --obvious way to do it" rule was applied, and now the preferred way to do that is: * assertEqual Furthermore, assertEquals and failUnlessEqual are *deprecated* in Python 3: >>> unittest.TestCase.assertEquals <function deprecated_func at 0xb73795ec> >>> unittest.TestCase.failUnlessEqual <function deprecated_func at 0xb73795ec> (I'm showing examples here using assertEqual, but the same happens for all the functionalities there) So, I propose to stick to the same method names than Python; this way we'll be more consistent and easy to learn than keep providing all variants. In concrete, I say that we should: - Deprecate those names that are deprecated in Python 3 (I mean, still provide the functionality, but with a DeprecationWarning) - Stop using them in internal code. - Fix documentation to explain all this and show the chosen methods. What do you think? Regards, -- . Facundo Blog: http://www.taniquetil.com.ar/plog/ PyAr: http://www.python.org/ar/

5 7

[Twisted-Python] Old-class-only support in manhole
by Facundo Batista March 27, 2011

March 27, 2011

Hello! Creating a test case for a change in twisted/manhole/explorer.py, I found these lines in CRUFT_WatchyThingie.watchObject: if type(object) is not types.InstanceType: raise TypeError, "Sorry, can only place a watch on Instances." Always talking in Python 2, if you pass an instance of an old style class as the "object", it will be ok; but if you pass a new style class, it will raise TypeError. So, I wanted just to ask if this is on purpose, should I open a bug about it, or what. Thank you! -- . Facundo Blog: http://www.taniquetil.com.ar/plog/ PyAr: http://www.python.org/ar/

3 4

[Twisted-Python] Weekly Bug Summary
by exarkun＠twistedmatrix.com March 26, 2011

March 26, 2011

1 0

[Twisted-Python] AMP Client disconnecting from server on high memory usage
by Dan-Cristian Bogos March 24, 2011

March 24, 2011

Hey Guys, Some issue I've met recently when experimenting with AMP. Have created an AMP client connecting to a server and stay there connected (using tap services). The issues I am getting is that as soon as I load some more serious data into twisted process (about 700MB on a virtual machine with 3GB of ram available) the AMP Client does not longer stay connected to the server. The data is loaded at startup using another service (loading data by simulating it - adding random strings to some tuple). I am using twisted 10.2 out of pypi packages. I should mention that with small amount of data in memory the connection stays stable just fine. In logs there is nothing except seeing the client connecting and disconnecting in the same second. Any of you know any memory configuration somewhere in the code? Thanks in advance for any kind of tip! DanB

2 1

[Twisted-Python] Windows build slaves
by Michael Tharp March 24, 2011

March 24, 2011

Greetings, I hear that Twisted needs some new/better/more reliable Windows build slaves. My employer has plenty of ESX capacity, and I know that a few other people are interested in helping out as well, so perhaps this a good time to clarify the requirements: Which platforms: XP and 7? 32bit and 64bit? Any interest in the server editions? Per-machine requirements: how much HDD and RAM? Any weird stuff like serial ports? Connectivity: Is NAT OK, or are inbound connections required? Do maintainers need access to the hypervisor, or is it adequate to have a watchdog to reboot crashed slaves? Contingent on employer approval, I can donate 4 VMs (one of each flavor) with 2GiB of RAM and tens of GB storage each, including MSDN licenses. The limitations are that they would be on a NAT-only subnet with no possibility of inbound ports, and that there would be no hypervisor access. However, I can provide a watchdog to deal with crashed slaves and a VPN could be arranged if there's a public endpoint I can direct it to. I'm also "generally pretty accessible" although Glyph unsurprisingly indicates that people have failed to live up to that promise in the past :P The offer is flexible, I'm just trying to start small to feel out the requirements. -- Michael Tharp rPath, Inc.

2 1

[Twisted-Python] Announcing Twisted 11.0.0pre1!
by Jessica McKellar March 23, 2011

March 23, 2011

Intrepid Twisted developers and users: from Cambridge, Massachusetts I am pleased to announce the arrival of Twisted 11.0.0 pre-release 1. Tarballs for the pre-release are available at: http://twistedmatrix.com/~jesstess/11.0.0pre1/ Highlights include: * a new templating system in Twisted Web, "twisted.web.template", derived from Divmod Nevow. * improved behavior of subprocess spawning on FreeBSD. * an API for constructing endpoints from descriptive strings. * twisted.plugin no longer emits a confusing traceback when it can't write a cache file. For more information, see the NEWS file. Download the tarballs and test away! Thanks, Jessica

7 9

Re: [Twisted-Python] Deferred documentation.
by Jasper St. Pierre March 22, 2011

March 22, 2011

(I screwed up my mailman preferences accidentally, so this is formatted a bit haphazard from copy/paste) > Thank you for tackling the impossible. Thank you for the encouragement. I'm curious if you read both documents, and if you had a preference toward one or the other. I hopefully only want to have one "definitive deferred brief" in the end, so a consensus on which road I should take would be would be helpful: * -Rewrite has a personal style: first-person perspective, relaxed language, to-the-point-but-silly examples. * -Fixup is a sort of gentler working of the current deferred doc that tries to be a bit more gentle about what the user knows: I don't shove the user full of an example involving some intricate intertwining of Deferred.callback and reactor.callLater to introduce them to callbacks, I instead opt to showcase the built-in HTTP client. > I remember when reading the old docs the first time that one thing > bothered me most and this was 'if I get a deferred back, then I'm kind > of responsible for that beast' so what do I do with it besides adding > call/errbacks'? I had a hard time and quite a few hours with the > debugger to figure out the life cycle of a deferred. I also read > gendefer.html over and over again while trying to figure out the > relation of a deferred to the reactor, because somehow it must be that > reactor.run() loop which in the end triggers either call- or errbacks. > > This might be typical questions from someone who grew up without garbage > collection. My problem is, that for coding in a confident way I have to > have a grasp of the innards of the system. > > Summed up > - How does the life cycle of a deferred look like? > - Who is responsible for a deferred? > - If deferreds are related to the reactor, then how are they related? An alternate goal of my efforts is to have a "rule list". Important things about the guarantees Deferreds should be documented: *If* you add more than one callback, *then* the return value of the last callback will be used as the result for the next callback. *If* you return a Deferred from a callback, *then* the callback chain waits until the second Deferred is complete. > Reading your two docs answers those questions I had back then, > definitely an improvement. > > Minor glitches: > > link to node.js is >> http://nodejs.org/ I'm going to have to find new libraries anyway: gevent takes an eventum-style approach that uses monkey-patches on urllib. I've seen the callback approach before in a lot of other, different JavaScript libs, hell, even the DOM-based addEventListener uses this a lot. I just need to find a Python-based strawman to knock down. > Thanks again, Werner Thank you so much for the encouragement.

1 0

[Twisted-Python] Weekly Bug Summary
by exarkun＠twistedmatrix.com March 19, 2011

March 19, 2011

2 1