[python-committers] Co-maintainer(s) for contextlib, dis and/or runpy?
Nick Coghlan
ncoghlan at gmail.com
Sat Jun 27 06:47:50 CEST 2015
More information about the python-committers mailing list
Sat Jun 27 06:47:50 CEST 2015
- Previous message (by thread): [python-committers] Weak SSH keys
- Next message (by thread): [python-committers] Co-maintainer(s) for contextlib, dis and/or runpy?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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 at gmail.com | Brisbane, Australia
- Previous message (by thread): [python-committers] Weak SSH keys
- Next message (by thread): [python-committers] Co-maintainer(s) for contextlib, dis and/or runpy?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the python-committers mailing list