Twisted December 2020

twisted@python.org

14 participants
18 discussions

[Twisted-Python] Buildbot downtime
by Tom Prince 03 Mar '22

03 Mar '22

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] Weekly Bug Summary
by trac＠twistedmatrix.com 27 Oct '21

27 Oct '21

5 5

[Twisted-Python] Twisted Python 0.7.0 Prerelease Testing
by Glyph Lefkowitz 05 Aug '21

05 Aug '21

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. ______ __ __ _____ _ _ | ____ | \_/ |_____] |_____| |_____| |_____ | | | | @ t w i s t e d m a t r i x . c o m http://www.twistedmatrix.com/~glyph/

4 5

[Twisted-Python] code contribution/participation policy
by Boris Epstein 10 Mar '21

10 Mar '21

Hi all, I have started working with Twisted and found it to be a very powerful package. That said, some modules are not documented very thoroughly (big surprise in the world of software, right?) and I also found some questionable code, too. If I were to contribute fixes/improvements, what is the submission procedure? Thanks. Boris.

4 8

[Twisted-Python] Upcoming Twisted Release
by Adi Roiban 02 Feb '21

02 Feb '21

Hi, I plan to act as a release manager for the next release and follow the plan documented at https://docs.twistedmatrix.com/en/latest/core/development/policy/release-pr… --------- The plan is to push the release candidate only on PyPI and to host the release candidate documentation (including pydoctor generated API docs) only on Read the Docs site. The Twisted Wiki Download page was updated to inform that PyPI is the only server where we publish the latest versions. So release candidates and final releases will be pushed only to PyPI. https://twistedmatrix.com/trac/wiki/Downloads While the release candidate documentation in only published on Read The Docs, at least for the next release I plan to also publish the documentation to: * https://twistedmatrix.com/documents/current/ * https://twistedmatrix.com/documents/VERSION/ After the release we can see if we can redirect them to Read The Docs. ---------------- For now, the only release blocker are the missing intersphinx API links on Read The Docs between the narrative docs and apidocs, but that is on track to be solved by next week. So no other tickets are in the blocker queue: https://twistedmatrix.com/trac/report/26 ------ Do you know any other release blocker issues? Since we have good continuous testing, maybe we can stop doing release candidates. The only thing blocking a release would be a "release blocket" ticket and truck CI checks not being green. Cheers -- Adi Roiban

5 17

[Twisted-Python] Plan/Goal for GitHub Sponsors
by Adi Roiban 04 Jan '21

04 Jan '21

Hi, I started a separate discussion to confirm the goal for a future fundraising. Top priority - Pay someone to help with the review queue Nice to have - Move server/services to Azure VM - We have at least $100 monthly allowance for Azure.... not sure if we still have the huge $2000 allowance on rackspace. Nice to have - Migrate Trac wiki to GitHub Wiki Nice to have - Migrate Trac Ticket to GitHub Issues That is all..but first we should solve the release queue. Cheers -- Adi Roiban

5 10

[Twisted-Python] Logging and SpawnProcess
by Robert DiFalco 31 Dec '20

31 Dec '20

Can anyone point me to some sample code for handling logging with SpawnProcess? Right now I'm using an EchoProtocol that takes stdout and resends it to the log. But it's kludgy because some sub-processes use stdin/stderr for marshaling data. What I'd most like to do is separate data transfer from log output in a clean way.

3 3

[Twisted-Python] Updating the project leadership committee
by Adi Roiban 29 Dec '20

29 Dec '20

Hi, Based on a comment from Glyph > The current "project leadership committee" is more than half made up of people who are a. no longer affiliated with the project and b. never answer their email at this point, I started this discussion to see if we can update / refresh the project leadership committee. I remember that in 2015 I read the same comment. Glypy, do you know the required number of members for the committee? My suggestion is to try to arrange for a committee that is updated every 2 years... or maybe every year. I can organize the communication and project management stuff. Here is the list of committers for the last to years https://github.com/twisted/twisted/graphs/contributors?from=2018-12-16&to=2… This is a quantitative approach... and does not imply quality or dedication, but I think that is a good starting point for searching for candidates for the committee. I can also volunteer to be part of the committee. Maybe we can create a new list of members for the commitee and then see if this list will be accepted by theSoftware Freedom Conservancy. I can also volunteer to do a bit of noise and see if we can raise more money. I will not apply for the fellowship, so I hope that in this way we will not have any complaints about my intentions :) PS: I have many patches for Twisted that are not commited. I could just hire another person to "review" them, but I don't think that this is fair. In fact, all the patches already passed an internal review, done by I person paid by my company. So, I hope that we can hire an independent reviewer -- Adi Roiban

3 5

[Twisted-Python] Weekly Bug Summary
by trac＠twistedmatrix.com 27 Dec '20

27 Dec '20

1 0

[Twisted-Python] Unjellying and circular references?
by Jasper Phillips 26 Dec '20

26 Dec '20

I'm using perspective broker to transfer objects in a networked game, which I'm having trouble unjellying -- the remote versions wind up with dangling twisted.persisted.crefutil._Dereference instances, so don't match the original objects. I'm seeing this for objects that have circular references to each other. I've refactored things to mostly avoid circular references and sidestep this, but have one remaining case where I find circular references mean clearer code that I'm reluctant to refactor. Is there some trick I'm missing to avoid _Dereferences?

3 3

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

Twisted December 2020