[Python-Dev] Re: Announcing the new Python triage team on GitHub

2019-08-23 Thread Giampaolo Rodola'
If the concern is pruning old/stale/invalid issues/PRs, I think the
proposal to add a specific "awaiting-close" (or similar) label should work.
These issues can periodically be handled by a core-dev who can click on the
label, then evaluate and bulk-close them in one shot if necessary. Also, it
seems to me that including "devguide" and "core-workflow" repos is
unnecessary since they are low-traffic administrative repos related to our
internal workflow, they are attended by a small portion of the core-dev
team only and labels don't play a central role as in the cpython repo.
Please let's keep in mind that this role implies higher responsibilities
than a usual contributor, and since the bar for being promoted is
considerably lower than a core-dev's, triager permissions should reflect
that and remain minimal. For instance, I don't think a triager should be
able to edit other users' comments or lock conversations, but I'm afraid
GitHub doesn't provide that level of granularity (correct?).

-- 
Giampaolo - http://grodola.blogspot.com
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/2YYB6MAJ55U2U4KTKINFDSB4USJ3NMZY/


[Python-Dev] Summary of Python tracker Issues

2019-08-23 Thread Python tracker

ACTIVITY SUMMARY (2019-08-16 - 2019-08-23)
Python tracker at https://bugs.python.org/

To view or respond to any of the issues listed below, click on the issue.
Do NOT respond to this message.

Issues counts and deltas:
  open7153 (-18)
  closed 42529 (+72)
  total  49682 (+54)

Open issues with patches: 2891 


Issues opened (47)
==

#26680: Incorporating float.is_integer into the numeric tower and Deci
https://bugs.python.org/issue26680  reopened by robert_smallshire

#37531: Fix regrtest timeout for subprocesses: regrtest -jN --timeout=
https://bugs.python.org/issue37531  reopened by vstinner

#37585: Comparing PyDictValues does not give expected results
https://bugs.python.org/issue37585  reopened by aeros167

#37878: Sub-Interpreters : Document PyThreadState_DeleteCurrent()
https://bugs.python.org/issue37878  opened by nanjekyejoannah

#37879: Segfaults in C heap type subclasses
https://bugs.python.org/issue37879  opened by eelizondo

#37880: For argparse add_argument with action='store_const', const sho
https://bugs.python.org/issue37880  opened by nanjekyejoannah

#37881: __text_signature__ parser doesn't handle globals in extension 
https://bugs.python.org/issue37881  opened by Antony.Lee

#37883: threading.Lock.locked is not documented
https://bugs.python.org/issue37883  opened by remi.lapeyre

#37885: venv: Don't produce unbound variable warning on deactivate
https://bugs.python.org/issue37885  opened by danabr

#37886: PyStructSequence_UnnamedField not exported
https://bugs.python.org/issue37886  opened by je...@livedata.com

#37888: Sub-interpreters : Confusing docs about state after calling Py
https://bugs.python.org/issue37888  opened by nanjekyejoannah

#37890: Modernize several tests in test_importlib
https://bugs.python.org/issue37890  opened by aeros167

#37891: Exceptions tutorial page does not mention raise from
https://bugs.python.org/issue37891  opened by Niels Albers

#37892: IDLE Shell: isolate user code input
https://bugs.python.org/issue37892  opened by terry.reedy

#37894: [win] shutil.which can not find the path if 'cmd' include dire
https://bugs.python.org/issue37894  opened by seahoh

#37895: test_logging hangs on an IPv6-only host
https://bugs.python.org/issue37895  opened by gregory.p.smith

#37896: test_multiprocessing_fork hangs on an IPv6-only host
https://bugs.python.org/issue37896  opened by gregory.p.smith

#37897: test_asyncio hangs on an IPv6-only host
https://bugs.python.org/issue37897  opened by gregory.p.smith

#37898: test_httpservers hangs on an IPv6-only host
https://bugs.python.org/issue37898  opened by gregory.p.smith

#37899: test_xmlrpc hangs on an IPv6-only host
https://bugs.python.org/issue37899  opened by gregory.p.smith

#37900: [urllib] proxy_bypass_registry doesn't handle invalid proxy ov
https://bugs.python.org/issue37900  opened by kwojniak_box

#37901: 21 tests fail when run on an IPv6-only host
https://bugs.python.org/issue37901  opened by gregory.p.smith

#37902: Add scrolling for IDLE browsers
https://bugs.python.org/issue37902  opened by GeeVye

#37903: IDLE Shell sidebar.
https://bugs.python.org/issue37903  opened by terry.reedy

#37904: Suggested edit to Python Tutorial - Section 4
https://bugs.python.org/issue37904  opened by lrnor...@gmail.com

#37905: Improve docs for NormalDist
https://bugs.python.org/issue37905  opened by Christoph.Deil

#37906: FreeBSD: test_threading: test_recursion_limit() crash with SIG
https://bugs.python.org/issue37906  opened by vstinner

#37907: speed-up PyLong_As*() for large longs
https://bugs.python.org/issue37907  opened by sir-sigurd

#37908: Add some examples of ArgumentParser.exit()
https://bugs.python.org/issue37908  opened by shihai1991

#37909: Thread pool return ref hold memory
https://bugs.python.org/issue37909  opened by Tianshu Gao

#37910: argparse wrapping fails with metavar="" (no metavar)
https://bugs.python.org/issue37910  opened by sjfranklin

#37911: Minor error in PEP567 code example
https://bugs.python.org/issue37911  opened by MarSoft

#37913: Document that __length_hint__ may return NotImplemented
https://bugs.python.org/issue37913  opened by jdemeyer

#37914: class timedelta, support the method hours and minutes in field
https://bugs.python.org/issue37914  opened by elinaldosoft

#37916: distutils: allow overriding of the RANLIB command on macOS (da
https://bugs.python.org/issue37916  opened by Jakub Piotr Cłapa

#37918: What about an enum for open() modes?
https://bugs.python.org/issue37918  opened by Marco Sulla

#37919: nntplib throws spurious NNTPProtocolError
https://bugs.python.org/issue37919  opened by msapiro

#37921: Improve zipfile: add support for symlinks
https://bugs.python.org/issue37921  opened by zaphodef

#37922: inspect.getsource returns wrong class definition when multiple
https://bugs.python.org/issue37922  opened by lennyt

#37923: Combining typing.get_type_hints and inspect.signature
https://bugs.python.org/issue37923  opened by dmontague

#379

[Python-Dev] Re: Announcing the new Python triage team on GitHub

2019-08-23 Thread Kyle Stanley
> For instance, I don't think a triager should be able to edit other users'
comments or lock conversations, but I'm afraid GitHub
> doesn't provide that level of granularity (correct?).

You are correct in that GitHub does not allow customization of the
permissions, but those with the  "Triage" permission are unable to edit
comments or lock conversations. In order to do either of those, the "Write"
permission is required. Compared to a normal contributor, triagers are only
able to add labels, close, reopen, and assign PRs/Issues.

On Fri, Aug 23, 2019 at 2:01 PM Giampaolo Rodola' 
wrote:

> If the concern is pruning old/stale/invalid issues/PRs, I think the
> proposal to add a specific "awaiting-close" (or similar) label should work.
> These issues can periodically be handled by a core-dev who can click on the
> label, then evaluate and bulk-close them in one shot if necessary. Also, it
> seems to me that including "devguide" and "core-workflow" repos is
> unnecessary since they are low-traffic administrative repos related to our
> internal workflow, they are attended by a small portion of the core-dev
> team only and labels don't play a central role as in the cpython repo.
> Please let's keep in mind that this role implies higher responsibilities
> than a usual contributor, and since the bar for being promoted is
> considerably lower than a core-dev's, triager permissions should reflect
> that and remain minimal. For instance, I don't think a triager should be
> able to edit other users' comments or lock conversations, but I'm afraid
> GitHub doesn't provide that level of granularity (correct?).
>
> --
> Giampaolo - http://grodola.blogspot.com
>
>
>
> ___
> Python-Dev mailing list -- python-dev@python.org
> To unsubscribe send an email to python-dev-le...@python.org
> https://mail.python.org/mailman3/lists/python-dev.python.org/
> Message archived at
> https://mail.python.org/archives/list/python-dev@python.org/message/2YYB6MAJ55U2U4KTKINFDSB4USJ3NMZY/
>
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/ZR6STQ3FCSKPS5BRJRTVEZ637NDDYTX5/