[Python-Dev] Re: Summary of Python tracker Issues
On 17.06.2022 20:48, Patrick Reader wrote:
> As a "temporary" solution to this problem, could the moderators just ban
> sta...@bugs.python.org from the list?
I've set the ML account to discard, so we should not be seeing
these messages anymore.
It would still be good to disable the script. The message headers
say that it's coming from roundup.psfhosted.org. Perhaps I can
ask Ee whether he knows where this is run.
> On 17/06/2022 19:08, Python tracker wrote:
>> ACTIVITY SUMMARY (2022-06-10 - 2022-06-17)
>> 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:
>> open 7146 ( +0)
>> closed 51841 ( +0)
>> total 58987 ( +0)
>>
>> Open issues with patches: 2890
>>
>>
>> Most recent 15 issues with no replies (15)
>> ==
>>
>> #47258: Python 3.10 hang at exit in drop_gil() (due to resource warnin
>> https://bugs.python.org/issue47258
>>
>> #47256: re: limit the maximum capturing group to 1,073,741,823, reduce
>> https://bugs.python.org/issue47256
>>
>> #47253: LOAD_GLOBAL instruction with wrong source position
>> https://bugs.python.org/issue47253
>>
>> #47252: socket.makefile documentation is missing data regarding the 'b
>> https://bugs.python.org/issue47252
>>
>> #47251: Merge BINARY_SUBSCR_LIST_INT with BINARY_SUBSCR_LIST_TUPLE
>> https://bugs.python.org/issue47251
>>
>> #47244: email.utils.formataddr does not respect double spaces
>> https://bugs.python.org/issue47244
>>
>> #47242: Annoying white bar in IDLE (line 457 in sidebar.py)
>> https://bugs.python.org/issue47242
>>
>> #47241: [C API] Move the PyCodeObject structure to the internal C API
>> https://bugs.python.org/issue47241
>>
>> #47238: Python threading.Event().wait() depends on the system time
>> https://bugs.python.org/issue47238
>>
>> #47236: Document types.CodeType.replace() changes about co_exceptionta
>> https://bugs.python.org/issue47236
>>
>> #47228: Document that na??ve datetime objects represent local time
>> https://bugs.python.org/issue47228
>>
>> #47222: subprocess.Popen() should allow capturing output and sending i
>> https://bugs.python.org/issue47222
>>
>> #47219: asyncio with two interpreter instances
>> https://bugs.python.org/issue47219
>>
>> #47218: adding name to lzmafile
>> https://bugs.python.org/issue47218
>>
>> #47217: adding name to BZ2File
>> https://bugs.python.org/issue47217
>>
>>
>>
>> Most recent 15 issues waiting for review (15)
>> =
>>
>> #47256: re: limit the maximum capturing group to 1,073,741,823, reduce
>> https://bugs.python.org/issue47256
>>
>> #47255: Many broken :meth: roles in the docs
>> https://bugs.python.org/issue47255
>>
>> #47254: enhanced dir?
>> https://bugs.python.org/issue47254
>>
>> #47251: Merge BINARY_SUBSCR_LIST_INT with BINARY_SUBSCR_LIST_TUPLE
>> https://bugs.python.org/issue47251
>>
>> #47243: Duplicate entry in 'Objects/unicodetype_db.h'
>> https://bugs.python.org/issue47243
>>
>> #47233: show_caches option affects code positions reported by dis.get_
>> https://bugs.python.org/issue47233
>>
>> #47222: subprocess.Popen() should allow capturing output and sending i
>> https://bugs.python.org/issue47222
>>
>> #47218: adding name to lzmafile
>> https://bugs.python.org/issue47218
>>
>> #47217: adding name to BZ2File
>> https://bugs.python.org/issue47217
>>
>> #47216: adding mtime option to gzip open()
>> https://bugs.python.org/issue47216
>>
>> #47215: Add "unstable" frame stack api
>> https://bugs.python.org/issue47215
>>
>> #47208: Support libffi implementations that cannot support invocations
>> https://bugs.python.org/issue47208
>>
>> #47205: posix.sched_{get|set}affinity(-1) no longer returns ProcessLoo
>> https://bugs.python.org/issue47205
>>
>> #47200: Add ZipInfo.mode property
>> https://bugs.python.org/issue47200
>>
>> #47199: multiprocessing: micro-optimize Connection.send_bytes() method
>> https://bugs.python.org/issue47199
>>
>> ___
>> 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/PNMW3MJ2K6FWBD3EOZOXF6QWEVWARHYM/
>>
>> Code of Conduct: http://python.org/psf/codeofconduct/
> ___
> 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/FEJXQMZMRLJDKL2W2YYFE46C7FIPSMC4/
>
> Code of Conduct: http://python.org/psf/codeofconduct/
--
Marc-Andre Lemburg
eGenix.com
Professional Python Services directly from the Experts (#1, Jun 18 2022)
>>>
[Python-Dev] Re: Summary of Python tracker Issues
As a "temporary" solution to this problem, could the moderators just ban
sta...@bugs.python.org from the list?
On 17/06/2022 19:08, Python tracker wrote:
ACTIVITY SUMMARY (2022-06-10 - 2022-06-17)
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:
open7146 ( +0)
closed 51841 ( +0)
total 58987 ( +0)
Open issues with patches: 2890
Most recent 15 issues with no replies (15)
==
#47258: Python 3.10 hang at exit in drop_gil() (due to resource warnin
https://bugs.python.org/issue47258
#47256: re: limit the maximum capturing group to 1,073,741,823, reduce
https://bugs.python.org/issue47256
#47253: LOAD_GLOBAL instruction with wrong source position
https://bugs.python.org/issue47253
#47252: socket.makefile documentation is missing data regarding the 'b
https://bugs.python.org/issue47252
#47251: Merge BINARY_SUBSCR_LIST_INT with BINARY_SUBSCR_LIST_TUPLE
https://bugs.python.org/issue47251
#47244: email.utils.formataddr does not respect double spaces
https://bugs.python.org/issue47244
#47242: Annoying white bar in IDLE (line 457 in sidebar.py)
https://bugs.python.org/issue47242
#47241: [C API] Move the PyCodeObject structure to the internal C API
https://bugs.python.org/issue47241
#47238: Python threading.Event().wait() depends on the system time
https://bugs.python.org/issue47238
#47236: Document types.CodeType.replace() changes about co_exceptionta
https://bugs.python.org/issue47236
#47228: Document that na??ve datetime objects represent local time
https://bugs.python.org/issue47228
#47222: subprocess.Popen() should allow capturing output and sending i
https://bugs.python.org/issue47222
#47219: asyncio with two interpreter instances
https://bugs.python.org/issue47219
#47218: adding name to lzmafile
https://bugs.python.org/issue47218
#47217: adding name to BZ2File
https://bugs.python.org/issue47217
Most recent 15 issues waiting for review (15)
=
#47256: re: limit the maximum capturing group to 1,073,741,823, reduce
https://bugs.python.org/issue47256
#47255: Many broken :meth: roles in the docs
https://bugs.python.org/issue47255
#47254: enhanced dir?
https://bugs.python.org/issue47254
#47251: Merge BINARY_SUBSCR_LIST_INT with BINARY_SUBSCR_LIST_TUPLE
https://bugs.python.org/issue47251
#47243: Duplicate entry in 'Objects/unicodetype_db.h'
https://bugs.python.org/issue47243
#47233: show_caches option affects code positions reported by dis.get_
https://bugs.python.org/issue47233
#47222: subprocess.Popen() should allow capturing output and sending i
https://bugs.python.org/issue47222
#47218: adding name to lzmafile
https://bugs.python.org/issue47218
#47217: adding name to BZ2File
https://bugs.python.org/issue47217
#47216: adding mtime option to gzip open()
https://bugs.python.org/issue47216
#47215: Add "unstable" frame stack api
https://bugs.python.org/issue47215
#47208: Support libffi implementations that cannot support invocations
https://bugs.python.org/issue47208
#47205: posix.sched_{get|set}affinity(-1) no longer returns ProcessLoo
https://bugs.python.org/issue47205
#47200: Add ZipInfo.mode property
https://bugs.python.org/issue47200
#47199: multiprocessing: micro-optimize Connection.send_bytes() method
https://bugs.python.org/issue47199
___
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/PNMW3MJ2K6FWBD3EOZOXF6QWEVWARHYM/
Code of Conduct: http://python.org/psf/codeofconduct/
___
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/FEJXQMZMRLJDKL2W2YYFE46C7FIPSMC4/
Code of Conduct: http://python.org/psf/codeofconduct/
[Python-Dev] Re: Summary of Python tracker Issues
On 15/05/2022 11:08, Paul Moore wrote: My understanding was that it would be updated to get its information from Github once the transition was complete. Is that not going to happen now? I'm not particularly bothered, as I only really skimmed the weekly email so it wouldn't be a great loss. But I agree, it should either be modified or removed. There has already been some discussion on this at https://github.com/psf/gh-migration/issues/6. ___ 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/VUIRK625UQVYPCYRE5WY73YZ465OQDY4/ Code of Conduct: http://python.org/psf/codeofconduct/
[Python-Dev] Re: Summary of Python tracker Issues
> > My understanding was that it would be updated to get its information > from Github once the transition was complete. Is that not going to > happen now? > There is an open PR to fix the roundup summary script at: https://github.com/python/cpython/pull/91738 It will move the roundup-summary script into the Python repo and have it run as a Github action instead of a cron job. Harry ___ 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/GIPDWV6SLFN6KS5HTQIDFP6BCH25NMYM/ Code of Conduct: http://python.org/psf/codeofconduct/
[Python-Dev] Re: Summary of Python tracker Issues
On 5/15/2022 11:31 AM, Ezio Melotti wrote: I merged a PR (https://github.com/python/psf-salt/pull/234) that was supposed to disable it, but apparently it's not enough. I'll double check with Ee (added to cc). This situation reminds me of the Sorcerer's Apprentice, who starts a magical water carrier but forgets how to turn it off. There is also a new script to replace the old one that is waiting for reviews (see https://github.com/psf/gh-migration/issues/6 and https://github.com/python/cpython/pull/91738). Perhaps the new script could identify itself at the bottom of its output and include instructions on starting and stopping its automatic execution. -- Terry Jan Reedy ___ 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/24M3CZMIWEYMCIMKGD6IH4WR5EJSXYAZ/ Code of Conduct: http://python.org/psf/codeofconduct/
[Python-Dev] Re: Summary of Python tracker Issues
I merged a PR (https://github.com/python/psf-salt/pull/234) that was supposed to disable it, but apparently it's not enough. I'll double check with Ee (added to cc). There is also a new script to replace the old one that is waiting for reviews (see https://github.com/psf/gh-migration/issues/6 and https://github.com/python/cpython/pull/91738). --Ezio On Sun, May 15, 2022 at 12:14 PM Paul Moore wrote: > > On Fri, 13 May 2022 at 19:54, Brett Cannon wrote: > > > > Can we shut this down or unsubscribe the weekly email? > > My understanding was that it would be updated to get its information > from Github once the transition was complete. Is that not going to > happen now? I'm not particularly bothered, as I only really skimmed > the weekly email so it wouldn't be a great loss. But I agree, it > should either be modified or removed. > > Paul > ___ > 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/GU3S32Y23AO2WWQ2OMMBU37GYNGOBL4U/ > Code of Conduct: http://python.org/psf/codeofconduct/ ___ 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/VJLIR5OICUXDNRJEZCFI7IGOKOND5WA5/ Code of Conduct: http://python.org/psf/codeofconduct/
[Python-Dev] Re: Summary of Python tracker Issues
On Fri, 13 May 2022 at 19:54, Brett Cannon wrote: > > Can we shut this down or unsubscribe the weekly email? My understanding was that it would be updated to get its information from Github once the transition was complete. Is that not going to happen now? I'm not particularly bothered, as I only really skimmed the weekly email so it wouldn't be a great loss. But I agree, it should either be modified or removed. Paul ___ 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/GU3S32Y23AO2WWQ2OMMBU37GYNGOBL4U/ Code of Conduct: http://python.org/psf/codeofconduct/
[Python-Dev] Re: Summary of Python tracker Issues
According to my notes, the summary is generated by this Python script:
https://github.com/psf/bpo-tracker-cpython/blob/master/scripts/roundup-summary
But I don't know what runs this script once a week.
Victor
On Fri, May 13, 2022 at 8:56 PM Brett Cannon wrote:
>
> Can we shut this down or unsubscribe the weekly email?
>
> On Fri, May 13, 2022 at 11:13 AM Python tracker
> wrote:
>>
>>
>> ACTIVITY SUMMARY (2022-05-06 - 2022-05-13)
>> 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:
>> open7146 ( +0)
>> closed 51841 ( +0)
>> total 58987 ( +0)
>>
>> Open issues with patches: 2890
>>
>>
>> Most recent 15 issues with no replies (15)
>> ==
>>
>> #47258: Python 3.10 hang at exit in drop_gil() (due to resource warnin
>> https://bugs.python.org/issue47258
>>
>> #47256: re: limit the maximum capturing group to 1,073,741,823, reduce
>> https://bugs.python.org/issue47256
>>
>> #47253: LOAD_GLOBAL instruction with wrong source position
>> https://bugs.python.org/issue47253
>>
>> #47252: socket.makefile documentation is missing data regarding the 'b
>> https://bugs.python.org/issue47252
>>
>> #47251: Merge BINARY_SUBSCR_LIST_INT with BINARY_SUBSCR_LIST_TUPLE
>> https://bugs.python.org/issue47251
>>
>> #47244: email.utils.formataddr does not respect double spaces
>> https://bugs.python.org/issue47244
>>
>> #47242: Annoying white bar in IDLE (line 457 in sidebar.py)
>> https://bugs.python.org/issue47242
>>
>> #47241: [C API] Move the PyCodeObject structure to the internal C API
>> https://bugs.python.org/issue47241
>>
>> #47238: Python threading.Event().wait() depends on the system time
>> https://bugs.python.org/issue47238
>>
>> #47236: Document types.CodeType.replace() changes about co_exceptionta
>> https://bugs.python.org/issue47236
>>
>> #47228: Document that na??ve datetime objects represent local time
>> https://bugs.python.org/issue47228
>>
>> #47222: subprocess.Popen() should allow capturing output and sending i
>> https://bugs.python.org/issue47222
>>
>> #47219: asyncio with two interpreter instances
>> https://bugs.python.org/issue47219
>>
>> #47218: adding name to lzmafile
>> https://bugs.python.org/issue47218
>>
>> #47217: adding name to BZ2File
>> https://bugs.python.org/issue47217
>>
>>
>>
>> Most recent 15 issues waiting for review (15)
>> =
>>
>> #47256: re: limit the maximum capturing group to 1,073,741,823, reduce
>> https://bugs.python.org/issue47256
>>
>> #47255: Many broken :meth: roles in the docs
>> https://bugs.python.org/issue47255
>>
>> #47254: enhanced dir?
>> https://bugs.python.org/issue47254
>>
>> #47251: Merge BINARY_SUBSCR_LIST_INT with BINARY_SUBSCR_LIST_TUPLE
>> https://bugs.python.org/issue47251
>>
>> #47243: Duplicate entry in 'Objects/unicodetype_db.h'
>> https://bugs.python.org/issue47243
>>
>> #47233: show_caches option affects code positions reported by dis.get_
>> https://bugs.python.org/issue47233
>>
>> #47222: subprocess.Popen() should allow capturing output and sending i
>> https://bugs.python.org/issue47222
>>
>> #47218: adding name to lzmafile
>> https://bugs.python.org/issue47218
>>
>> #47217: adding name to BZ2File
>> https://bugs.python.org/issue47217
>>
>> #47216: adding mtime option to gzip open()
>> https://bugs.python.org/issue47216
>>
>> #47215: Add "unstable" frame stack api
>> https://bugs.python.org/issue47215
>>
>> #47208: Support libffi implementations that cannot support invocations
>> https://bugs.python.org/issue47208
>>
>> #47205: posix.sched_{get|set}affinity(-1) no longer returns ProcessLoo
>> https://bugs.python.org/issue47205
>>
>> #47200: Add ZipInfo.mode property
>> https://bugs.python.org/issue47200
>>
>> #47199: multiprocessing: micro-optimize Connection.send_bytes() method
>> https://bugs.python.org/issue47199
>> ___
>> 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/LEYLS2TYSZ4NVDFLTDSQUT25C2Y4QG2O/
>> Code of Conduct: http://python.org/psf/codeofconduct/
>
> ___
> 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/C53WJXVWHZNGLTTPFQXHUWIZCYF2FBP7/
> Code of Conduct: http://python.org/psf/codeofconduct/
--
Night gathers, and now my watch begins. It shall not end until my death.
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe
[Python-Dev] Re: Summary of Python tracker Issues
Can we shut this down or unsubscribe the weekly email?
On Fri, May 13, 2022 at 11:13 AM Python tracker
wrote:
>
> ACTIVITY SUMMARY (2022-05-06 - 2022-05-13)
> 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:
> open7146 ( +0)
> closed 51841 ( +0)
> total 58987 ( +0)
>
> Open issues with patches: 2890
>
>
> Most recent 15 issues with no replies (15)
> ==
>
> #47258: Python 3.10 hang at exit in drop_gil() (due to resource warnin
> https://bugs.python.org/issue47258
>
> #47256: re: limit the maximum capturing group to 1,073,741,823, reduce
> https://bugs.python.org/issue47256
>
> #47253: LOAD_GLOBAL instruction with wrong source position
> https://bugs.python.org/issue47253
>
> #47252: socket.makefile documentation is missing data regarding the 'b
> https://bugs.python.org/issue47252
>
> #47251: Merge BINARY_SUBSCR_LIST_INT with BINARY_SUBSCR_LIST_TUPLE
> https://bugs.python.org/issue47251
>
> #47244: email.utils.formataddr does not respect double spaces
> https://bugs.python.org/issue47244
>
> #47242: Annoying white bar in IDLE (line 457 in sidebar.py)
> https://bugs.python.org/issue47242
>
> #47241: [C API] Move the PyCodeObject structure to the internal C API
> https://bugs.python.org/issue47241
>
> #47238: Python threading.Event().wait() depends on the system time
> https://bugs.python.org/issue47238
>
> #47236: Document types.CodeType.replace() changes about co_exceptionta
> https://bugs.python.org/issue47236
>
> #47228: Document that na??ve datetime objects represent local time
> https://bugs.python.org/issue47228
>
> #47222: subprocess.Popen() should allow capturing output and sending i
> https://bugs.python.org/issue47222
>
> #47219: asyncio with two interpreter instances
> https://bugs.python.org/issue47219
>
> #47218: adding name to lzmafile
> https://bugs.python.org/issue47218
>
> #47217: adding name to BZ2File
> https://bugs.python.org/issue47217
>
>
>
> Most recent 15 issues waiting for review (15)
> =
>
> #47256: re: limit the maximum capturing group to 1,073,741,823, reduce
> https://bugs.python.org/issue47256
>
> #47255: Many broken :meth: roles in the docs
> https://bugs.python.org/issue47255
>
> #47254: enhanced dir?
> https://bugs.python.org/issue47254
>
> #47251: Merge BINARY_SUBSCR_LIST_INT with BINARY_SUBSCR_LIST_TUPLE
> https://bugs.python.org/issue47251
>
> #47243: Duplicate entry in 'Objects/unicodetype_db.h'
> https://bugs.python.org/issue47243
>
> #47233: show_caches option affects code positions reported by dis.get_
> https://bugs.python.org/issue47233
>
> #47222: subprocess.Popen() should allow capturing output and sending i
> https://bugs.python.org/issue47222
>
> #47218: adding name to lzmafile
> https://bugs.python.org/issue47218
>
> #47217: adding name to BZ2File
> https://bugs.python.org/issue47217
>
> #47216: adding mtime option to gzip open()
> https://bugs.python.org/issue47216
>
> #47215: Add "unstable" frame stack api
> https://bugs.python.org/issue47215
>
> #47208: Support libffi implementations that cannot support invocations
> https://bugs.python.org/issue47208
>
> #47205: posix.sched_{get|set}affinity(-1) no longer returns ProcessLoo
> https://bugs.python.org/issue47205
>
> #47200: Add ZipInfo.mode property
> https://bugs.python.org/issue47200
>
> #47199: multiprocessing: micro-optimize Connection.send_bytes() method
> https://bugs.python.org/issue47199
> ___
> 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/LEYLS2TYSZ4NVDFLTDSQUT25C2Y4QG2O/
> Code of Conduct: http://python.org/psf/codeofconduct/
>
___
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/C53WJXVWHZNGLTTPFQXHUWIZCYF2FBP7/
Code of Conduct: http://python.org/psf/codeofconduct/
[Python-Dev] Re: Summary of Python tracker Issues
On Fri, Apr 29, 2022 at 8:12 PM Python tracker wrote: > ACTIVITY SUMMARY (2022-04-22 - 2022-04-29) > 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: > open7146 ( +0) > closed 51841 ( +0) > total 58987 ( +0) Congrats! We finally managed to stop users from reporting new bugs. Python reached perfection Victor ___ 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/X4NPUP6OX2AS2E3EWBSAFAO543B7KTYW/ Code of Conduct: http://python.org/psf/codeofconduct/
[Python-Dev] Re: Summary of Python tracker Issues
On 4/15/2022 2:07 PM, Python tracker wrote: ACTIVITY SUMMARY (2022-04-08 - 2022-04-15) Python tracker at https://bugs.python.org/ This report only shows the last few days of bpo activity before the migration. GH report code is apparently still beint written. ___ 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/ICNYNY45NHIYKTNZJ7SHM653B6HRHWPA/ Code of Conduct: http://python.org/psf/codeofconduct/
[Python-Dev] Re: Summary of Python tracker Issues
On Fri, May 29, 2020 at 12:16 PM Python tracker wrote: > ACTIVITY SUMMARY (2020-05-22 - 2020-05-29) > 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: > open7487 ( +9) > closed 45080 (+80) > total 52567 (+89) > > ... How hard would it be to add PRs (in the same way) to this weekly report? Also, where is the script for this hosted and where is the source repo (if any)? it might be helpful to have a link back to that info, perhaps somewhere in the devguide. -eric ___ 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/WCUONFB5MRSC6LHWT442QBF7FBN7TGQJ/ Code of Conduct: http://python.org/psf/codeofconduct/
