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.
______ __ __ _____ _ _
| ____ | \_/ |_____] |_____|
|_____| |_____ | | | |
@ t w i s t e d m a t r i x . c o m
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
I plan to act as a release manager for the next release and follow the plan
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.
While the release candidate documentation in only published on Read The
at least for the next release I plan to also publish the documentation to:
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:
Do you know any other release blocker issues?
Since we have good continuous testing, maybe we can stop doing release
The only thing blocking a release would be a "release blocket" ticket and
truck CI checks not being green.
I started a separate discussion to confirm the goal for a future
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.
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.
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
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
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
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
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
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?
Does anyone have anything against applying so that Twisted can be on the
waitlist of the GitHub Sponsors ?
As far as I know, the money for the Twisted project is managed by the
Software Freedom Conservancy organization and they are already approved
hosts for GitHub Sponsors.
At this point, we only need to press the green button.
The bank account and other administrative issues are already sorted out.
If there are no complaints , I plan to press the green button in 1 week.
We will then have to see how to access those funds via Software Freedom
Conservancy... but that is part 2.