[Twisted-Python] Weekly Bug Summary
Bug summary __ Summary for 2021-01-17 through 2021-01-24 Opened Closed Total Change Enhancements: 0 0 1470 +0 Defects: 2 1 1001 +1 Tasks: 0 0 94 +0 Regressions: 0 0 2 +0 Total: 2 1 2569 +1 |== Type Changes |== Priority Changes |== Component Changes |Defect: +1 |Normal: +0 |Core: +0 |Low: +1 |Website: +1 Total Tickets Open Tickets New / Reopened Bugs __ = Normal = [#10080] Fix or work around stricter pydoctor warnings about __all__ and __doc__ (opened by mthuurne) (CLOSED, fixed) defect core http://twistedmatrix.com/trac/ticket/10080 = Low = [#10081] ZopeInterface FAQ Link Broken (opened by fullbuffer) defect websitehttp://twistedmatrix.com/trac/ticket/10081 Closed Bugs __ = Normal = [#10080] Fix or work around stricter pydoctor warnings about __all__ and __doc__ (opened by mthuurne, closed by Maarten ter Huurne , fixed) defect core http://twistedmatrix.com/trac/ticket/10080 Ticket Lifetime Stats __ Oldest open ticket - [#50] conch command-line client doesn't work in win32 (since 2003-07-12 14:41:06). Newest open ticket - [#10081] ZopeInterface FAQ Link Broken (since 2021-01-19 11:48:33.225591). Mean open ticket age: 3001 days, 23:51:53.666091. Median: 2991 days, 7:54:46.574324. Standard deviation: 1490 days, 20:41:49.299321. Interquartile range: 2187 days, 6:13:24.637437. Mean time between ticket creation and ticket resolution: 613 days, 16:17:55.878880. Median: 58 days, 4:55:49.641954. Standard deviation is 1016 days, 18:46:39.310335. The interquartile range is 807 days, 23:21:23.800562. Mean time spent in review: 101 days, 18:54:32.463611. Median: 4 days, 18:32:05. Standard deviation: 488 days, 5:55:41.864439. Interquartile range: 23 days, 20:13:46.399811. Mean number of times a ticket is reviewed: 1.78806907378. Median: 1 Standard deviation: 1.40982402605. Interquartile range: 1. Contributor Stats __ In the last 4 weeks, 12 unique ticket reporters 2 unique ticket reviewers 1 unique ticket resolvers In the last 24 weeks, 37 unique ticket reporters 10 unique ticket reviewers 13 unique ticket resolvers In the last 48 weeks, 61 unique ticket reporters 12 unique ticket reviewers 26 unique ticket resolvers ___ Twisted-Python mailing list Twisted-Python@twistedmatrix.com https://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
Re: [Twisted-Python] Questions about Project Leadership committee
On January 23, 2021 at 6:10:04 PM, Craig Rodrigues (rodr...@crodrigues.org(mailto:rodr...@crodrigues.org)) wrote: > > > On Sat, Jan 23, 2021 at 4:54 PM Glyph > mailto:gl...@twistedmatrix.com)> wrote: > > > > > > At the time the committee was created, I don’t remember if this was public, > > so I don’t feel comfortable sharing identities publicly because it wasn’t > > part of the deal at the time. This is not the way I’d structure things now, > > but given that several members are unresponsive and don’t seem to want to > > be associated with the project any more, I can’t ask them if it’s OK with > > them. If you can find any old public documentation feel free to share > > though; the issue is that I’m not sure it *has* been public. If it has, it > > can by all means remain public. > > > > > > I can at least share that as I recall there are 6 members and I’m one of > > them. But you’d want to confirm this with the conservancy, so please join > > Adi’s private thread with them for further discussion. > > > > > > > Thanks for the clarification. > Have you recently contacted the 5 other committee members to confirm if they > want to remain on the committee or not, > and either received confirmation (or feedback timeout)? > > > > Not recently although I’ve reached out several times in the past. I have no plans to reach out again until someone has worked out with the SFC what our options are and proposed a concrete plan. > > In this e-mail: > https://twistedmatrix.com/pipermail/twisted-python/2020-December/065364.html > , I mentioned that I > tried to look for documentation about this committee at > https://twistedmatrix.com and could not find any. > > So if you are not aware of any public documentation regarding this committee, > then I think it is reasonable > to assume that such documentation does not exist. > -- > Craig > > > ___ > Twisted-Python mailing list > Twisted-Python@twistedmatrix.com > https://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python ___ Twisted-Python mailing list Twisted-Python@twistedmatrix.com https://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
Re: [Twisted-Python] Questions about Project Leadership committee
On Sat, Jan 23, 2021 at 4:54 PM Glyph wrote: > At the time the committee was created, I don’t remember if this was > public, so I don’t feel comfortable sharing identities publicly because it > wasn’t part of the deal at the time. This is not the way I’d structure > things now, but given that several members are unresponsive and don’t seem > to want to be associated with the project any more, I can’t ask them if > it’s OK with them. If you can find any old public documentation feel free > to share though; the issue is that I’m not sure it *has* been public. If it > has, it can by all means remain public. > > I can at least share that as I recall there are 6 members and I’m one of > them. But you’d want to confirm this with the conservancy, so please join > Adi’s private thread with them for further discussion. > Thanks for the clarification. Have you recently contacted the 5 other committee members to confirm if they want to remain on the committee or not, and either received confirmation (or feedback timeout)? In this e-mail: https://twistedmatrix.com/pipermail/twisted-python/2020-December/065364.html , I mentioned that I tried to look for documentation about this committee at https://twistedmatrix.com and could not find any. So if you are not aware of any public documentation regarding this committee, then I think it is reasonable to assume that such documentation does not exist. -- Craig ___ Twisted-Python mailing list Twisted-Python@twistedmatrix.com https://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
Re: [Twisted-Python] Questions about Project Leadership committee
On January 23, 2021 at 1:36:40 PM, Craig Rodrigues (rodr...@crodrigues.org(mailto:rodr...@crodrigues.org)) wrote: > Hi, > I asked some questions about the Twisted project leadership committee here: > > https://twistedmatrix.com/pipermail/twisted-python/2020-December/065367.html > > but it looks like my questions got lost in the thread, and no one aso I will > ask again. > Who are the current members of the committee? At the time the committee was created, I don’t remember if this was public, so I don’t feel comfortable sharing identities publicly because it wasn’t part of the deal at the time. This is not the way I’d structure things now, but given that several members are unresponsive and don’t seem to want to be associated with the project any more, I can’t ask them if it’s OK with them. If you can find any old public documentation feel free to share though; the issue is that I’m not sure it *has* been public. If it has, it can by all means remain public. I can at least share that as I recall there are 6 members and I’m one of them. But you’d want to confirm this with the conservancy, so please join Adi’s private thread with them for further discussion. > > What are the titles/roles/responsibilities of the current committee members? There are no titles or roles. > > Is there a mailing list, IRC channel, or some other venue which the current > committee members belong to > so that they can communicate amongst themselves, and also with the outside > world, such as the Software Freedom Conservancy? There’s theoretically a mailing list but it hasn’t seen a post in more than 4 years. I’m not even sure if it still works in our new mail service configuration. So functionally, “no”. > > > -- > Craig > ___ > Twisted-Python mailing list > Twisted-Python@twistedmatrix.com > https://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python ___ Twisted-Python mailing list Twisted-Python@twistedmatrix.com https://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
Re: [Twisted-Python] Ldaptor attributes in Python 3
On Sat, 23 Jan 2021, at 22:09, Adi Roiban wrote: > Hi, > > On Fri, 22 Jan 2021 at 11:15, Peter Westlake wrote: >> I'm using Ldaptor for LDAP access because it fits in with Twisted, and the >> results are a bit mystifying. >> ... > > Can you send a full example of how you would like the API to behave ? Or > send a PR ? :) > > I am doing a client-side search like this and I was happy with API > > o = LDAPEntry(client, base_dn) > results = yield o.search( > attributes=[b'objectclass'], > scope=LDAP_SCOPE_wholeSubtree, > filterText='(cn=test)', > ) > for result in results: > print (result['objectclass']) Thanks, Adi! My code looks like this: > o = LDAPEntry(client, base_dn) > results = yield o.search(filterText='(uid=peterw)') > for result in results: > print (result['cn']) I would like this to print: Peter Westlake or b'Peter Westlake' What it actually prints is: JournaledLDAPAttributeSet(b'cn', [b'Peter Westlake]) Having searched the WWW for examples, it looks as though other people have seen it behaving in exactly the way I want, but it's not doing that for me, with Python 3.6.8 on CentOS 7. Peter.___ Twisted-Python mailing list Twisted-Python@twistedmatrix.com https://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
Re: [Twisted-Python] Ldaptor attributes in Python 3
Hi, On Fri, 22 Jan 2021 at 11:15, Peter Westlake wrote: > I'm using Ldaptor for LDAP access because it fits in with Twisted, and the > results are a bit mystifying. The results that come back from a search are > a list of LDAPEntryWithClient. Indexing this, e.g. entry['cn'], gives an > object of type JournaledLDAPAttributeSet, which is a subclass of set. It > contains the name of the attribute and a list containing the value: > > JournaledLDAPAttributeSet(b'cn', [b'Peter Westlake']) > > Getting the value out of that isn't straightforward: I'd have to check the > elements of the set for a list. Is there a better way? > > I've also found that the items() method gives something more tractable: > > >>> entry.items() > [ > (b'cn', b'Peter Westlake'), > ... > ] > > so I can turn that into a dict and index that. But again, this seems like > an odd design for an API. Is there a better way to extract the value of an > attribute from an entry? > > Can you send a full example of how you would like the API to behave ? Or send a PR ? :) I am doing a client-side search like this and I was happy with API o = LDAPEntry(client, base_dn) results = yield o.search( attributes=[b'objectclass'], scope=LDAP_SCOPE_wholeSubtree, filterText='(cn=test)', ) for result in results: print (result['objectclass']) -- Adi Roiban ___ Twisted-Python mailing list Twisted-Python@twistedmatrix.com https://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
[Twisted-Python] Questions about Project Leadership committee
Hi, I asked some questions about the Twisted project leadership committee here: https://twistedmatrix.com/pipermail/twisted-python/2020-December/065367.html but it looks like my questions got lost in the thread, and no one aso I will ask again. Who are the current members of the committee? What are the titles/roles/responsibilities of the current committee members? Is there a mailing list, IRC channel, or some other venue which the current committee members belong to so that they can communicate amongst themselves, and also with the outside world, such as the Software Freedom Conservancy? -- Craig ___ Twisted-Python mailing list Twisted-Python@twistedmatrix.com https://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
