Mailman 3 November 2015 - Twisted

[Twisted-Python] Buildbot downtime
by Tom Prince March 3, 2022

March 3, 2022

I am plannig to upgrade twisted's buildbot in the near future. In preperation for that, I am going to take down the production buildbot on Tuesday, June 26, around 1600 UTC[1]. During that time, the result of any builds done will be lost. Thus, I'd ask that people avoid committing to trunk during that time. I will send a reminder before I take down the buildbot both here, and on #twisted and #twisted-dev. Tom [1] http://timeanddate.com/worldclock/meetingtime.html?iso=20120626&p1=80&p2=22…

2 8

[Twisted-Python] Twisted Python 0.7.0 Prerelease Testing
by Glyph Lefkowitz Aug. 5, 2021

Aug. 5, 2021

hi there, folks: I'd really like to release 0.7.0 but I would like it to be at least a little bit tested before I do so. Could those of you with CVS trees check everything out and see if it performs as advertised? Deeper bugs than that will have to wait for the next release, but I'd at least like to know if it works for someone other than me. Thanks. ______ __ __ _____ _ _ | ____ | \_/ |_____] |_____| |… [View More]

4 5

[Twisted-Python] Real Viagra Professional - for real sex pros
by Tamika May 1, 2019

May 1, 2019

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <center> <a href="http://rqf.entercompassion.com"><img src="http://mediapix.ru/pics/685207b3dd437eff7f15c0744b5c1d3a.gif"> <title> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <link rel="stylesheet" href="http://gfx8.nnt.com/mail/12.0.1187.0824/positioning.css" /> </head> <body style="overflow:auto;"… [View More]> <div id="PrintShellToolbar"> <div class="ContainerPadding"> <span class="FloatRight"> <a href= > <img alt="" src="http://gfx1.nfi.com/mail/w2/pr02/ltr/glyph_close_rest.gif" /> <Close window> <a href= > <img alt="" src="http://gfx2.czb.com/mail/w2/pr02/ltr/i_print.gif" /> <Print> </a> </span> </div> </div> <div> <div class="BorderContainerOutline ContainerPadding"> <div class="ClearBoth"> <span class="HeaderData" style="font-size:large;"> <TuPostal.com Cambia de nombre?> </span> </div> <div class="ClearBoth"> <span class="HeaderLabel"> <From:> </span> <span class="HeaderData"> <b><TuPostal.com></b> </span> </div> <div class="ClearBoth"> <span class="HeaderLabel"> <Sent:> </span> <span class="HeaderData"> <div class="ClearBoth"> <span class="HeaderLabel"> To: </span> <span class="HeaderData"> Mikelelliott (mikelelliott(a)rlo.com) </span> </div> <br /> </div> </div> <div class="MessageBody" style=""> <br /> <div id="MessageBodyText" class="ExternalClass" style="border: 1px solid #fff ;"> <pre>Hola!<br> <br>Tupostal es ahora parte de Sonico!<br> <br>Para conocer nuestro nuevo sitio, haz clic en el siguiente link:<br><a href='http://www.gwpcom/index1.php' target='_blank'>http://www.bjncom/index1.php</a><br> <br>Sonico es un sitio donde puedes...<br>- Guardar fotos ilimitadas<br>- Re encontrarte con viejos amigos<br>- Recibir novedades de tus amigos.<br> <br>Te Esperamos! Ya somos mas de 21 millones de usuarios!!<br> <br>Sonico - Amigos Conectados<br> <br> <br>PD: Ahora tambien podras guardar tus postales<br> <br> <br>------------------------------------------<br>Haz recibido este email porque te encuentras registrado en fdm.com.<br>Si no deseas recibir mas mensajes como este, por favor haz clic en el siguiente link:<br><a href='http://www.cehcom/unsubscribe.php?type=2' target='_blank'>http://www.fyocom/unsubscribe.php?type=2</a><br> <br></pre> </div> </div> </div> </body> </html> [View Less]

8 10

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

March 16, 2016

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 … [View More]

2 5

[Twisted-Python] Suggested plan for GitHub migration
by Craig Rodrigues Dec. 16, 2015

Dec. 16, 2015

On Tue, Nov 17, 2015 at 8:57 AM, Adi Roiban <adi(a)roiban.ro> wrote: > > For now, the funds were raised to migrate to GitHub, so we can not use > them to do other things. > > We will stay on Trac for issues... at least for now. > > I have no idea how we can migrate to any issue tracker without losing > data if we don't have full access to the database. > It is possible to migrate to another issue tracker and not lose data. I've done Trac -> Redmine, and it … [View More]works, but there was an existing migration script I could use. For migrating to a cloud based bug tracker, you would need to take every user in the existing Trac database, and see if there would be a way to map the existing users to the cloud database, such as GitHub. It's a lot of work, but possible. However, for the scope of this project, if staying with Trac for issues is what is required, that is fine. > We don't plan to migrate to GitHub Issues / GitHub Wiki / GitHub Pages > > OK. So based on what you have listed, I would say that most of the work will be working with Git post commit hooks. I would say the plan should be something like this. A.1 https://github.com/twisted/twisted will be the "repository of truth" for Twisted. -> Twisted releases will be done from GitHub -> the Twisted developers who are now "core committers" for SVN, must be given access to be "core committers" to https://github.com/twisted/twisted A.2 On the Trac server, a local git mirror of the GitHub must be set up. Every bug tracker I've seen that integrates with git needs a local mirror of the repo in order to parse the git history in order to update the bug database. This mirror should be read-only, and the only thing updating this repo should be the Trac GitHub plugin. A.3 On the Trac server, this plugin must be installed: https://github.com/trac-hacks/trac-github A.4 On the GitHub server, a post-commit web hook must be configured. The workflow will be this: [core committer does push to https://github.com/twisted/twisted] -> [post commit GitHub hook will be called to poke the Trac GitHub plugin] -> [Trac GitHub plugin will update the local git repo on the Trac server] -> [Trac GitHub will parse the git history for new commits and update tickets] I would recommend that steps (1) - (4) be made to work in a staging environment, with a separate GitHub repo, and a separate copy of the Trac database. That way, you can test things out without derailing Twisted developers. When you are confident that this workflow works, then the transition plan will be something like the following. B.1 Send an e-mail to the mailing list and pick one day for the maintenance window. This will warn folks when they should take a holiday from Twisted work. :) B.2 When maintenance is about to begin, send a [HEADSUP] mail saying that repo will be unavailable. B.3 Create Subversion pre-commit hook to disable all commits to Subversion: http://stackoverflow.com/questions/2411122/how-to-freeze-entire-svn-reposit… B.4 Set up steps A.1 - A.4 B.5 Verify that B.4 works. Have someone (Glyph?) do a commit to https://github.com/twisted/twisted, and make sure that Trac works. B.6 Once the Twisted core team are satisified that everything works, send an e-mail to the mailing list that the maintenance window is over, and GitHub is now where the action is! B.7 Update all wiki documentation to change all references to getting code from Subversion, to getting code from GitHub. B.8 Update all systems which used Subversion to use GitHub. For example, buildbots. -- Craig -- Craig [View Less]

7 13

[Twisted-Python] incompatible change - need revert before release
by Glyph Lefkowitz Dec. 7, 2015

Dec. 7, 2015

Tom Prince discovered a regression on https://twistedmatrix.com/trac/ticket/7016#comment:14 <https://twistedmatrix.com/trac/ticket/7016#comment:14> - I think that this was introduced after 15.4, so it needs to be rolled back (or fixed, if someone can get to it before the revert) in 15.5. -glyph

3 7

[Twisted-Python] Streaming HTTP
by Cory Benfield Dec. 7, 2015

Dec. 7, 2015

Folks, # Problem Statement Thanks for your feedback on my HTTP/2 questions. I’ve started work implementing a spike of a HTTP/2 protocol for twisted.web. I’m aiming to have something that works in at least some cases by the end of the day. As part of my dive into twisted.web, I noticed something that surprised me: it seems to have no support for ‘streaming’ request bodies. By this I mean that the Request.requestReceived() method is not actually called until the complete request body has been … [View More]received. This is a somewhat unexpected limitation for Twisted: why should I have to wait until the entire body has been uploaded to start doing things with it? This problem is thrown into sharp relief with HTTP/2, which essentially always chunks the body, even if a content-length is provided. This means that it is now very easy to receive data in delimited chunks, which an implementation may want to have semantic meaning. However, the request is unable to access this data in this way. It also makes it impossible to use a HTTP/2 request/response pair as a long-running communication channel, as we cannot safely call requestReceived until the response is terminated (which also terminates the HTTP/2 stream). Adi pointed me at a related issue, #6928[0], which itself points at what appears to be an issue tracking exactly this request. That issue is issue #288[1], which is 12 years old(!). This has clearly been a pain point for quite some time. Issue #6928 has glyph suggesting that we come to the mailing list to discuss this, but the last time it was raised no responses were received[2]. I believe that with HTTP/2 on the horizon, this issue is more acute than it was before, and needs solving if Twisted is going to continue to remain relevant for the web. It should also allow people to build more performant web applications, as they should be able to handle how the data queues up in their apps. This does not immediately block my HTTP/2 work, so we can take some time and get this right. # Proposed Solution To help us move forward, I’m providing a proposal for how I’d solve this problem. This is not necessarily going to be the final approach, but is instead a straw-man we can use to form the basis of a discussion about what the correct fix should be. My proposal is to deprecate the current Request/Resource model. It currently functions and should continue to function, but as of this point we should consider it a bad way to do things, and we should push people to move to a fully asynchronous model. We should then move to an API that is much more like the one used by Go: specifically, that by default all requests/responses are streamed. Request objects (and, logically, any other object that handles requests/responses, such as Resource) should be extended to have a chunkReceived method that can be overridden by users. If a user chooses not to override that method, the default implementation would continue to do what is done now (save to a buffer). Once the request/response is complete (marked by receipt of a zero-length chunk, or a frame with END_STREAM set, or when the remaining content-length is 0), request/responseComplete would be called. For users that did not override chunkReceived can now safely access the content buffer: other users can do whatever they see fit. We’d also update requestReceived to ensure that it’s called when all the *headers* are received, rather than waiting for the body. A similar approach should be taken with sending data: we should assume that users want to chunk it if they do not provide a content-length. An extreme position to take (and I do) is that this should be sufficiently easy that most users actually *accidentally* end up chunking their data: that is, we do not provide special helpers to set content-length, instead just checking whether that’s a header users actually send, and if they don’t we chunk the data. This logic would make it much easier to work with HTTP/2 *and* with WebSockets, requiring substantially less special-case code to handle the WebSocket upgrade (when the headers are complete, we can spot the upgrade easily). What do people think of this approach? Cory [0]: https://twistedmatrix.com/trac/ticket/6928 [1]: https://twistedmatrix.com/trac/ticket/288 [2]: https://twistedmatrix.com/pipermail/twisted-python/2014-February/028069.html [View Less]

8 19

[Twisted-Python] Writing a low-level network debugging tool
by Jonathan Ballet Dec. 3, 2015

Dec. 3, 2015

Hi all, I'm trying to toubleshoot network connectivity issues we have in one of our office and I would like to monitor some metrics which seems to be relevant for us, especially when trying to open TCP connections towards external endpoints. In particular, I'm looking for a way to get the following information (let's say I want to monitor the connectivity towards the swisscom.com, port 80 using TCP): * how long does it take to resolv the domain name to (at least) one of its IP address … [View More]

2 3

[Twisted-Python] twisted.web response.py questions
by peter Nov. 29, 2015

Nov. 29, 2015

hi, looking over: https://twistedmatrix.com/documents/14.0.2/_downloads/response.py im not really sure why one would use the line: self.remaining = 1024 * 10 this suggest to me that one knew what kind of page size was expected...but what if you dont? wouldnt it make more sense to use someting like this: def dataReceived(self, bytes): self.page_content = self.page_content + bytes this would sum up all the data until connectionLost is called. and in connectionLost(): def … [View More]

1 0

[Twisted-Python] Implementing server ESMTP extensions in Twisted
by Adi Roiban Nov. 29, 2015

Nov. 29, 2015

So, We have patch for review which works towards allowing the current STMP/ESTMP server implementation to be sublcassed in order to implement ESMTP extensions. Here is the ticket https://twistedmatrix.com/trac/ticket/8128 If you care about SMTP/ESMTP please send your feedback, here or on the ticket. I am not an SMTP/ESMTP expert and I need help in reviewing this ticket. ------- My main questions regarding ESTMP extensions are : 1. Do we really want to implement them using sublcassing or … [View More]

1 0