Co-maintainer(s) for contextlib, dis and/or runpy?
Hi folks,
My available time for the fundamentals of stdlib module maintenance is unfortunately pretty limited these days, which means even reviewed patches for modules where I'm the sole maintainer aren't necessarily getting applied in a timely fashion (Serhiy quite rightly nudged me about this recently in relation to a languishing contextlib patch).
Would anyone be interesting in taking up co-maintainership of one or more of the affected modules? Timely reviews I can generally manage (especially for other core developers), it's timely patch application and new module level development work that I struggle to find the time for :(
The affected modules:
- contextlib
- dis
- runpy
Regards, Nick.
P.S. In the specific case of contextlib, I'm also interested in finding someone willing to take up maintenance of the contextlib2 backport: https://pypi.python.org/pypi/contextlib2
-- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
I'm happy to provide on demand reviews. I an take on the backporting easily enough. On 27 Jun 2015 4:47 pm, "Nick Coghlan" ncoghlan@gmail.com wrote:
Hi folks,
My available time for the fundamentals of stdlib module maintenance is unfortunately pretty limited these days, which means even reviewed patches for modules where I'm the sole maintainer aren't necessarily getting applied in a timely fashion (Serhiy quite rightly nudged me about this recently in relation to a languishing contextlib patch).
Would anyone be interesting in taking up co-maintainership of one or more of the affected modules? Timely reviews I can generally manage (especially for other core developers), it's timely patch application and new module level development work that I struggle to find the time for :(
The affected modules:
- contextlib
- dis
- runpy
Regards, Nick.
P.S. In the specific case of contextlib, I'm also interested in finding someone willing to take up maintenance of the contextlib2 backport: https://pypi.python.org/pypi/contextlib2
-- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers
On 27 June 2015 at 15:08, Robert Collins robertc@robertcollins.net wrote:
I'm happy to provide on demand reviews. I an take on the backporting easily enough.
Thanks, I added you to the PyPI project as a co-owner. The source repo for the contextlib2 backport is currently at https://bitbucket.org/ncoghlan/contextlib2/, but the main problem with it is that it's old CI service went away, and I never got around to finding a replacement.
Regards, Nick.
-- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
On Sat, Jun 27, 2015 at 2:29 PM, Nick Coghlan ncoghlan@gmail.com wrote:
On 27 June 2015 at 15:08, Robert Collins robertc@robertcollins.net wrote:
I'm happy to provide on demand reviews. I an take on the backporting easily enough.
Thanks, I added you to the PyPI project as a co-owner. The source repo for the contextlib2 backport is currently at https://bitbucket.org/ncoghlan/contextlib2/, but the main problem with it is that it's old CI service went away, and I never got around to finding a replacement.
I can help set contextlib2 up with CI, if you like.
Would you prefer using a github mirror and Travis CI, or a CI service which support BitBucket directly?
- Tal
On 28 Jun 2015 8:57 pm, "Tal Einat" taleinat@gmail.com wrote:
On Sat, Jun 27, 2015 at 2:29 PM, Nick Coghlan ncoghlan@gmail.com wrote:
On 27 June 2015 at 15:08, Robert Collins robertc@robertcollins.net
wrote:
I'm happy to provide on demand reviews. I an take on the backporting easily enough.
Thanks, I added you to the PyPI project as a co-owner. The source repo for the contextlib2 backport is currently at https://bitbucket.org/ncoghlan/contextlib2/, but the main problem with it is that it's old CI service went away, and I never got around to finding a replacement.
I can help set contextlib2 up with CI, if you like.
Would you prefer using a github mirror and Travis CI, or a CI service which support BitBucket directly?
I'll defer answering that to Robert - if he's going to take over the backports, then whatever is most convenient for him would make sense (which may include migrating away from BitBucket entirely).
Regards, Nick.
- Tal
Hi Nick,
I've added myself to dis & contextlib modules on the experts list.
Yury
On 2015-06-27 12:47 AM, Nick Coghlan wrote:
Hi folks,
My available time for the fundamentals of stdlib module maintenance is unfortunately pretty limited these days, which means even reviewed patches for modules where I'm the sole maintainer aren't necessarily getting applied in a timely fashion (Serhiy quite rightly nudged me about this recently in relation to a languishing contextlib patch).
Would anyone be interesting in taking up co-maintainership of one or more of the affected modules? Timely reviews I can generally manage (especially for other core developers), it's timely patch application and new module level development work that I struggle to find the time for :(
The affected modules:
- contextlib
- dis
- runpy
Regards, Nick.
P.S. In the specific case of contextlib, I'm also interested in finding someone willing to take up maintenance of the contextlib2 backport: https://pypi.python.org/pypi/contextlib2
On 27 June 2015 at 20:42, Yury Selivanov yselivanov.ml@gmail.com wrote:
Hi Nick,
I've added myself to dis & contextlib modules on the experts list.
Thanks! I also added you to the nosy list for the contextlib issue that Serhiy originally pinged me about :)
Cheers, Nick.
-- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
On 27.06.15 14:35, Nick Coghlan wrote:
I also added you to the nosy list for the contextlib issue that Serhiy originally pinged me about :)
The patch already was approved by you. I reviewed the patch and it LGTM too. I pinged you only because the issue is assigned to you. If you trust me, just reassign the issue to me and I'll commit the patch.
On 28 June 2015 at 00:47, Serhiy Storchaka storchaka@gmail.com wrote:
On 27.06.15 14:35, Nick Coghlan wrote:
I also added you to the nosy list for the contextlib issue that Serhiy originally pinged me about :)
The patch already was approved by you. I reviewed the patch and it LGTM too. I pinged you only because the issue is assigned to you. If you trust me, just reassign the issue to me and I'll commit the patch.
That's a good point - I had a range of issues assigned to me where I'd been telling myself "I'll get to that soon" for months, and instead kept finding other tasks to work on that I considered higher priority. That's a bad thing for me to be doing, as it ends up blocking other people from deciding they're interested in working on those issues and moving them forward.
I've now reset the assignee on all such issues to accurately reflect the fact I'm not currently working on them. (A couple of those are test suite refactorings with patches already submitted, so mentors willing to pick them up would be greatly appreciated! If anyone has more time available than I do, http://bugs.python.org/issue9517 would a good place to start for that specific aspect)
I also dropped myself from the issue assignment list in the triaging guide - while I'm happy to help out with reviews, actually assigning me issues that aren't work or PEP 432 related is currently a good way to see them languish indefinitely :(
Regards, Nick.
-- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
On Fri, Jun 26, 2015 at 11:47 PM, Nick Coghlan ncoghlan@gmail.com wrote:
Hi folks,
My available time for the fundamentals of stdlib module maintenance is unfortunately pretty limited these days, which means even reviewed patches for modules where I'm the sole maintainer aren't necessarily getting applied in a timely fashion (Serhiy quite rightly nudged me about this recently in relation to a languishing contextlib patch).
Would anyone be interesting in taking up co-maintainership of one or more of the affected modules? Timely reviews I can generally manage (especially for other core developers), it's timely patch application and new module level development work that I struggle to find the time for :(
The affected modules:
- contextlib
- dis
I am spinning back up on Python volunteer time and am interested in helping out with 'dis'.
-- Meador
participants (6)
-
Meador Inge -
Nick Coghlan -
Robert Collins -
Serhiy Storchaka -
Tal Einat -
Yury Selivanov