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
A few months ago, the question of an official process for obtaining commit access was raised.
The discussion lead to this proposal - https://twistedmatrix.com/trac/wiki/Proposal/ContributorAdvancementPath <https://twistedmatrix.com/trac/wiki/Proposal/ContributorAdvancementPath>. I like that proposal, but it is still incomplete: to wit, it defines a template for how roles might be defined but does not actually define any roles. It also seems to be a bit overly ambitious, just from the observed reaction of nobody having the time to implement it :).
So I have a proposal for a scaled back process that nevertheless would give us something official-ish:
Not all committers are actively involved in the project at all times, so we should form a "committer committee" of people who are interested in evaluating candidates. If you would like to do that and you're already a committer, please contact me and I'll add you to the list. I want to do this so there's somewhere to apply to which isn't just a public mailing list or discussion, since public discussions can create social pressure to grant someone commit just to be nice, and rejections might be perceived as mean.
Candidates should submit an application to this new list, commit(a)twistedmatrix.com <mailto:email@example.com> which is a list of links to at least 10 tickets, at least 5 of which are patches they've submitted, and at least 5 of which are code reviews they've done which have been accepted by a committer. At least 2 of their authored patches should have gone all the way through the process to be landed.
As with the other parts of our process, if there is at least one sponsor, and no objections from anyone on the committee within 7 days, any member of the committee may add the committer.
New committers should then be announced on the mailing list.
This is not really an ideal process - particularly, it lacks a good way to give contributors something specific and useful to do - but it's something at least. If there is general assent that this is an improvement, I'll go make a wiki page and a mailing list.
Are there any major disadvantages of using pymongo with callInThread
instead of txmongo? I'd like to take advantage of some newer features in
pymongo (unfortunately not available in txmongo) and it's certainly easier
to maintain feature parity using callInThread.
I am sure everyone understands that the Twisted community would love more
diversity. While it is hard to achieve, it should be easy to remove one of
the obvious blockers -- making underrepresented groups feel more welcome.
I think, and hope, that our IRC channel, our issue system and mailing list
have been a friendly, pleasant place. This is an attempt to clarify what we
mean by a "friendly, pleasant place".
After some discussion on IRC, I volunteered to write up a Code of Conduct
for Twisted. It is mostly an adaptation of Django's CoC -- I think Django
has a nice track record of commitment to diversity, and, of course, we
expect our communities to overlap.
My current draft, including instructions on how to build it, is in
https://github.com/moshez/twisted-coc . I have intentionally not made the
built documents available, in an attempt to avoid someone picking them up
before they're approved by us.
Please respond if there are any concerns about the wording, anything that I
missed and anything you think does not belong there. I hope we can achieve
consensus, and have the Project Leadership Committee approve this
(including approving the current committee -- I've volunteered to chair it,
and Glyph and Amber (HawkOwl) have graciously agreed to be on it.)
This is an automatic reply. I am away from the office for the summer, returning on Tuesday, August 25, 2015. I will be happy to get back to you then.
Enjoy your summer!
This email and any files transmitted with it may be confidential and are intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. If you are not
the named addressee you should not disseminate, distribute or copy this email.
When I tried to run a simple twisted program and noticed there was an
error as following:
File "C:\Python34\lib\site-packages\twisted\python\lockfile.py", line 52,
_open = file
NameError: name 'file' is not defined
simply replace file as open like
_open = open
can run the program.
Is it a bug?
Help me please.
Tell me how to wrap in Defer dataReceived.
For example, I need to execute a command and send receive data in
callback. The only yet I found - to use the session number sent commands
and replies received
Can one example.
Thanks in advance!
PyPI + pip has supported uploading prereleases for a long while, and this would be a much better way for you, the Twisted user, to get the prereleases, rather than messing about with tarballs.
Pip 1.4+ (which according to https://caremad.io/2015/04/a-year-of-pypi-downloads/ constitutes 80%+ of pips) supports prereleases on PyPI.
So, the question is, do people think we should start putting them on PyPI? Is it worth some users on ancient pips inadvertantly getting (admittedly quite stable) prereleases? Would you use it, and would you be more likely to test Twisted prereleases if they were distributed like this (in addition to the tarball)?
Amber "Hawkie" Brown