Mailing List Archive

On Fri, 30 Nov 2012 14:38:12 -0500, Brett Cannon <brett@python.org> wrote:
> Do we have a graph of the historical trend of the number of bugs (or at
> least the historical details stored somewhere)? I think we have had a net

Not really. Ezio made one by hand once, but there is nothing automated.

The historical details are stored only in the mailing list archives, as
far as I know. In theory I think you could re-calculate them from the
Roundup DB, but for various reasons the numbers would probably come out
slightly different. Still, getting the data from the DB would be better
than parsing the emails, since for one reason and another there are
missing Friday reports, and reports that were issued on non-Friday
dates.

> decrease in open bugs the last couple of weeks and it would be neat to see
> an absolute and relative graph of the overall trend since Python 3.3.0 was
> released. Also might make a nice motivator to try to close issues faster. =)
>
> Otherwise is the code public for this somewhere? I assume it's making an

Yes. It is in the software repository for our roundup instances:

http://hg.python.org/tracker/python-dev/file/default/scripts/roundup-summary

(Be warned that that isn't the location from which the script is
executed, so it is possible for what is actually running to get out of
sync with what is checked in at that location.)

> XML-RPC call or something every week to get the results, but if I decide to

Nope, it talks directly to the DB. And as you will see, it is more
than a bit gnarly.

> do a little App Engine app to store historical data and do a graph I would
> rather not have to figure all of this out from scratch. =) Although I could
> I guess also parse the email if I wanted to ignore all other emails.

I'm not sure how one would go about integrating the above with an App
Engine app. I suspect that not quite enough information is available
through the XML-RPC interface to replicate that script, but maybe you
could manage just the open-close counting part of it. I haven't
looked at what it would take.

--David
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

On Fri, Nov 30, 2012 at 4:07 PM, R. David Murray <rdmurray@bitdance.com>wrote:

> On Fri, 30 Nov 2012 14:38:12 -0500, Brett Cannon <brett@python.org> wrote:
> > Do we have a graph of the historical trend of the number of bugs (or at
> > least the historical details stored somewhere)? I think we have had a net
>
> Not really. Ezio made one by hand once, but there is nothing automated.
>
> The historical details are stored only in the mailing list archives, as
> far as I know. In theory I think you could re-calculate them from the
> Roundup DB, but for various reasons the numbers would probably come out
> slightly different. Still, getting the data from the DB would be better
> than parsing the emails, since for one reason and another there are
> missing Friday reports, and reports that were issued on non-Friday
> dates.
>
> > decrease in open bugs the last couple of weeks and it would be neat to
> see
> > an absolute and relative graph of the overall trend since Python 3.3.0
> was
> > released. Also might make a nice motivator to try to close issues
> faster. =)
> >
> > Otherwise is the code public for this somewhere? I assume it's making an
>
> Yes. It is in the software repository for our roundup instances:
>
>
> http://hg.python.org/tracker/python-dev/file/default/scripts/roundup-summary
>
> (Be warned that that isn't the location from which the script is
> executed, so it is possible for what is actually running to get out of
> sync with what is checked in at that location.)
>
> > XML-RPC call or something every week to get the results, but if I decide
> to
>
> Nope, it talks directly to the DB. And as you will see, it is more
> than a bit gnarly.
>
>
I think I could also download the csv file and parse that to get whatever
data I wanted.


> > do a little App Engine app to store historical data and do a graph I
> would
> > rather not have to figure all of this out from scratch. =) Although I
> could
> > I guess also parse the email if I wanted to ignore all other emails.
>
> I'm not sure how one would go about integrating the above with an App
> Engine app. I suspect that not quite enough information is available
> through the XML-RPC interface to replicate that script, but maybe you
> could manage just the open-close counting part of it. I haven't
> looked at what it would take.
>

It really depends on what statistics I cared about (e.g. there are less
than 4000 bugs while there are less than 25,000 closed bugs). If I just did
high-level statistics it wouldn't be bad, but if I try to track every issue
independently that might be annoying (and actually cost money for me,
although I already personally pay for py3ksupport.appspot.com so I can
probably piggyback off of that app's quota). We will see if this ever goes
anywhere. =)

Hi,

On Fri, Nov 30, 2012 at 11:52 PM, Brett Cannon <brett@python.org> wrote:

> On Fri, Nov 30, 2012 at 4:07 PM, R. David Murray <rdmurray@bitdance.com>wrote:
>
>> On Fri, 30 Nov 2012 14:38:12 -0500, Brett Cannon <brett@python.org>
>> wrote:
>> > Do we have a graph of the historical trend of the number of bugs (or at
>> > least the historical details stored somewhere)? I think we have had a
>> net
>>
>> Not really. Ezio made one by hand once, but there is nothing automated.
>>
>
The one I made can be found here:
https://docs.google.com/spreadsheet/ccc?key=0AplyAWXqkvHUdFF0SkVrT3VKcnRBZXNrR1hleHowWnc
I now updated it with the latest data.
On the Sheet 2 you can find additional graphs that show the releases of
Python together with the data. Only final releases are included, alphas,
betas and rcs are not included.
The spreadsheet is a bit messy because I was experimenting with different
kind of graphs and trying to work around some limitations of Google Docs,
but it should be good enough.


>
>> The historical details are stored only in the mailing list archives, as
>> far as I know. In theory I think you could re-calculate them from the
>> Roundup DB, but for various reasons the numbers would probably come out
>> slightly different. Still, getting the data from the DB would be better
>> than parsing the emails, since for one reason and another there are
>> missing Friday reports, and reports that were issued on non-Friday
>> dates.
>>
>
One option I was considering is having the weekly report script append the
result on a file and make it available on bugs.python.org, or even use it
to generate graphs directly. This is something I considered and planned to
implement for a long time, but haven't done it yet.


>> > decrease in open bugs the last couple of weeks and it would be neat to
>> see
>> > an absolute and relative graph of the overall trend since Python 3.3.0
>> was
>> > released. Also might make a nice motivator to try to close issues
>> faster. =)
>> >
>> > Otherwise is the code public for this somewhere? I assume it's making an
>>
>> Yes. It is in the software repository for our roundup instances:
>>
>>
>> http://hg.python.org/tracker/python-dev/file/default/scripts/roundup-summary
>>
>> (Be warned that that isn't the location from which the script is
>> executed, so it is possible for what is actually running to get out of
>> sync with what is checked in at that location.)
>>
>> > XML-RPC call or something every week to get the results, but if I
>> decide to
>>
>> Nope, it talks directly to the DB. And as you will see, it is more
>> than a bit gnarly.
>>
>>
> I think I could also download the csv file and parse that to get whatever
> data I wanted.
>

To figure out when an issue was closed you need to access its history, and
that's not available through XML-RPC/csv IIRC. You should be able to
figure out when the issue got created though.
Anyway, it's probably easier to implement something like what I mentioned
earlier.


>
>> > do a little App Engine app to store historical data and do a graph I
>> would
>> > rather not have to figure all of this out from scratch. =) Although I
>> could
>> > I guess also parse the email if I wanted to ignore all other emails.
>>
>> I'm not sure how one would go about integrating the above with an App
>> Engine app. I suspect that not quite enough information is available
>> through the XML-RPC interface to replicate that script, but maybe you
>> could manage just the open-close counting part of it. I haven't
>> looked at what it would take.
>>
>
> It really depends on what statistics I cared about (e.g. there are less
> than 4000 bugs while there are less than 25,000 closed bugs). If I just did
> high-level statistics it wouldn't be bad, but if I try to track every issue
> independently that might be annoying (and actually cost money for me,
> although I already personally pay for py3ksupport.appspot.com so I can
> probably piggyback off of that app's quota). We will see if this ever goes
> anywhere. =)
>
>
Another somehow related project/experiment I've been working on is
collecting stats about the patches available on the tracker. I put
together a temporary page that allows you to enter the name of a module (or
any file/path) and get a list of issues with patches that affect the
specified module(s): http://wolfprojects.altervista.org/issues.html
FTR this is based on the word done by anatoly (see links on the page).
I'm planning to eventually integrate this in the tracker too, but lately I
don't have too much time, so there's no ETA.

Best Regards,
Ezio Melotti

Brett Cannon wrote:
> Do we have a graph of the historical trend of the number of bugs (or at least
> the historical details stored somewhere)? I think we have had a net decrease in
> open bugs the last couple of weeks and it would be neat to see an absolute and
> relative graph of the overall trend since Python 3.3.0 was released. Also might
> make a nice motivator to try to close issues faster. =)
>
> Otherwise is the code public for this somewhere? I assume it's making an
> XML-RPC call or something every week to get the results, but if I decide to do
> a little App Engine app to store historical data and do a graph I would rather
> not have to figure all of this out from scratch. =) Although I could I guess
> also parse the email if I wanted to ignore all other emails.

A few months ago I made a script that downloads all python-dev mailman
archives, scans them to find the summary messages, parses the messages
and creates a graph using matplotlib. The script is available at
https://gist.github.com/2723809.
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

T-Mobile. America's First Nationwide 4G Network.


------ Original message------From: Python trackerDate: Fri, Sep 26, 2014 12:07 PMTo: python-dev@python.org;Subject:[Python-Dev] Summary of Python tracker IssuesACTIVITY SUMMARY (2014-09-19 - 2014-09-26)Python tracker at http://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 4677 (+15) closed 29587 (+43) total 34264 (+58)Open issues with patches: 2197 Issues opened (39)==================#22444: Floor divide should return inthttp://bugs.python.org/issue22444 opened by belopolsky#22445: Memoryviews require more strict contiguous checks then necessahttp://bugs.python.org/issue22445 opened by seberg#22449: SSLContext.load_verify_locations behavior on Windows and OSXhttp://bugs.python.org/issue22449 opened by christian.heimes#22450: urllib doesn't put Accept: */* in the headershttp://bugs.python.org/issue22450 opened by rhettinger#22452: addTypeEqualityFunc is not used in assertListEqualhttp://bugs.python.org/issue22452 opened by simonzack#22453: PyObject_REPR macro causes refcount leakhttp://bugs.python.org/issue22453 opened by Chris.Colbert#22454: Adding the opposite function of shlex.split()http://bugs.python.org/issue22454 opened by Sworddragon#22455: idna/punycode give wrong results on narrow buildshttp://bugs.python.org/issue22455 opened by bukzor#22456: __base__ undocumentedhttp://bugs.python.org/issue22456 opened by Arfrever#22457: load_tests not invoked in root __init__.py when start=package http://bugs.python.org/issue22457 opened by rbcollins#22458: Add fractions benchmarkhttp://bugs.python.org/issue22458 opened by scoder#22460: idle editor: replace all in selectionhttp://bugs.python.org/issue22460 opened by bagratte#22462: Modules/pyexpat.c violates PEP 384http://bugs.python.org/issue22462 opened by Mark.Shannon#22463: Warnings when building on AIXhttp://bugs.python.org/issue22463 opened by jelie#22465: Number agreement error in section 3.2 of web docshttp://bugs.python.org/issue22465 opened by pauamma#22466: problem with installing python 2.7.8http://bugs.python.org/issue22466 opened by elctr0#22468: Tarfile using fstat on GZip file objecthttp://bugs.python.org/issue22468 opened by bartolsthoorn#22470: Possible integer overflow in error handlershttp://bugs.python.org/issue22470 opened by serhiy.storchaka#22472: OSErrors should use str and not repr on pathshttp://bugs.python.org/issue22472 opened by r.david.murray#22473: The gloss on asyncio "future with run_forever" example is confhttp://bugs.python.org/issue22473 opened by r.david.murray#22474: No explanation of how a task gets destroyed in asyncio 'task' http://bugs.python.org/issue22474 opened by r.david.murray#22475: asyncio task get_stack documentation seems to contradict itselhttp://bugs.python.org/issue22475 opened by r.david.murray#22476: asyncio task chapter confusion about 'task', 'future', and 'schttp://bugs.python.org/issue22476 opened by r.david.murray#22477: GCD in Fractionshttp://bugs.python.org/issue22477 opened by brg@gladman.plus.com#22480: SystemExit out of run_until_complete causes AttributeError whehttp://bugs.python.org/issue22480 opened by chrysn#22482: logging: fileConfig doesn't support formatter styleshttp://bugs.python.org/issue22482 opened by domzippilli#22486: Add math.gcd()http://bugs.python.org/issue22486 opened by scoder#22489: .gitignore filehttp://bugs.python.org/issue22489 opened by rbcollins#22490: Using realpath for __PYVENV_LAUNCHER__ makes Homebrew installshttp://bugs.python.org/issue22490 opened by tdsmith#22491: Support Unicode line boundaries in regular expressionhttp://bugs.python.org/issue22491 opened by serhiy.storchaka#22492: small addition to print() docs: no binary streams.http://bugs.python.org/issue22492 opened by georg.brandl#22493: Deprecate the use of flags not at the start of regular expresshttp://bugs.python.org/issue22493 opened by serhiy.storchaka#22494: default logging time string is not localizedhttp://bugs.python.org/issue22494 opened by sdague#22495: merge large parts of test_binop.py and test_fractions.pyhttp://bugs.python.org/issue22495 opened by wolma#22496: urllib2 fails against IIS (urllib2 can't parse 401 reply www-ahttp://bugs.python.org/issue22496 opened by deronnax#22497: msiexec not creating msvcr90.dll with python -2.7.6.msihttp://bugs.python.org/issue22497 opened by dykesk#22499: [SSL: BAD_WRITE_RETRY] bad write retry in _ssl.c:1636http://bugs.python.org/issue22499 opened by nikratio#22500: Argparse always stores True for positional argumentshttp://bugs.python.org/issue22500 opened by Tristan.Fisher#22501: Optimise PyLong division by 1 or -1http://bugs.python.org/issue22501 opened by scoderMost recent 15 issues with no replies (15)==========================================#22495: merge large parts of test_binop.py and test_fractions.pyhttp://bugs.python.org/issue22495#22494: default logging time string is not localizedhttp://bugs.python.org/issue22494#22493: Deprecate the use of flags not at the start of regular expresshttp://bugs.python.org/issue22493#22492: small addition to print() docs: no binary streams.http://bugs.python.org/issue22492#22489: .gitignore filehttp://bugs.python.org/issue22489#22475: asyncio task get_stack documentation seems to contradict itselhttp://bugs.python.org/issue22475#22470: Possible integer overflow in error handlershttp://bugs.python.org/issue22470#22468: Tarfile using fstat on GZip file objecthttp://bugs.python.org/issue22468#22465: Number agreement error in section 3.2 of web docshttp://bugs.python.org/issue22465#22463: Warnings when building on AIXhttp://bugs.python.org/issue22463#22462: Modules/pyexpat.c violates PEP 384http://bugs.python.org/issue22462#22460: idle editor: replace all in selectionhttp://bugs.python.org/issue22460#22455: idna/punycode give wrong results on narrow buildshttp://bugs.python.org/issue22455#22453: PyObject_REPR macro causes refcount leakhttp://bugs.python.org/issue22453#22429: asyncio: pending call to loop.stop() if a coroutine raises a Bhttp://bugs.python.org/issue22429Most recent 15 issues waiting for review (15)=============================================#22501: Optimise PyLong division by 1 or -1http://bugs.python.org/issue22501#22493: Deprecate the use of flags not at the start of regular expresshttp://bugs.python.org/issue22493#22492: small addition to print() docs: no binary streams.http://bugs.python.org/issue22492#22490: Using realpath for __PYVENV_LAUNCHER__ makes Homebrew installshttp://bugs.python.org/issue22490#22489: .gitignore filehttp://bugs.python.org/issue22489#22486: Add math.gcd()http://bugs.python.org/issue22486#22470: Possible integer overflow in error handlershttp://bugs.python.org/issue22470#22462: Modules/pyexpat.c violates PEP 384http://bugs.python.org/issue22462#22457: load_tests not invoked in root __init__.py when start=package http://bugs.python.org/issue22457#22450: urllib doesn't put Accept: */* in the headershttp://bugs.python.org/issue22450#22449: SSLContext.load_verify_locations behavior on Windows and OSXhttp://bugs.python.org/issue22449#22445: Memoryviews require more strict contiguous checks then necessahttp://bugs.python.org/issue22445#22442: subprocess.check_call hangs on large PIPEd data.http://bugs.python.org/issue22442#22437: re module: number of named groups is limited to 100 maxhttp://bugs.python.org/issue22437#22435: socketserver.TCPSocket leaks socket to garbage collector if sehttp://bugs.python.org/issue22435Top 10 most discussed issues (10)=================================#22477: GCD in Fractionshttp://bugs.python.org/issue22477 31 msgs#22444: Floor divide should return inthttp://bugs.python.org/issue22444 23 msgs#22486: Add math.gcd()http://bugs.python.org/issue22486 23 msgs#22501: Optimise PyLong division by 1 or -1http://bugs.python.org/issue22501 16 msgs#18814: Add codecs.convert_surrogateescape to "clean" surrogate escapehttp://bugs.python.org/issue18814 15 msgs#22445: Memoryviews require more strict contiguous checks then necessahttp://bugs.python.org/issue22445 14 msgs#1602: windows console doesn't print or input Unicodehttp://bugs.python.org/issue1602 12 msgs#22458: Add fractions benchmarkhttp://bugs.python.org/issue22458 9 msgs#22396: AIX posix_fadvise and posix_fallocatehttp://bugs.python.org/issue22396 8 msgs#22466: problem with installing python 2.7.8http://bugs.python.org/issue22466 8 msgsIssues closed (41)==================#4888: misplaced (or misleading) assert in ceval.chttp://bugs.python.org/issue4888 closed by berker.peksag#12845: PEP-3118: C-contiguity with zero strideshttp://bugs.python.org/issue12845 closed by skrah#14293: Message methods delegated via __getattr__ inaccessible using shttp://bugs.python.org/issue14293 closed by r.david.murray#15799: httplib client and statuslinehttp://bugs.python.org/issue15799 closed by karlcow#17462: argparse FAQ: how it is different from optparsehttp://bugs.python.org/issue17462 closed by berker.peksag#18993: There is an overshadowed and invalid test in testmock.pyhttp://bugs.python.org/issue18993 closed by berker.peksag#20912: [zipfile.py]: Make zip directory attributes more friendly for http://bugs.python.org/issue20912 closed by serhiy.storchaka#21079: EmailMessage.is_attachment == False if filename is presenthttp://bugs.python.org/issue21079 closed by r.david.murray#21091: EmailMessage.is_attachment should be a methodhttp://bugs.python.org/issue21091 closed by r.david.murray#21332: subprocess bufsize=1 docs are misleadinghttp://bugs.python.org/issue21332 closed by pitrou#21431: 3.4.1rc1 test_pydoc fails: pydoc_data.topics.topics values arehttp://bugs.python.org/issue21431 closed by python-dev#21860: Correct FileIO docstringshttp://bugs.python.org/issue21860 closed by berker.peksag#22278: urljoin duplicate slasheshttp://bugs.python.org/issue22278 closed by orsenthil#22359: Remove incorrect uses of recursive makehttp://bugs.python.org/issue22359 closed by pitrou#22362: Warn about octal escapes > 0o377 in rehttp://bugs.python.org/issue22362 closed by serhiy.storchaka#22408: Tkinter doesn't handle Unicode dead key combinations on Windowhttp://bugs.python.org/issue22408 closed by ned.deily#22415: Fix re debugging outputhttp://bugs.python.org/issue22415 closed by serhiy.storchaka#22420: Use print(file=sys.stderr) instead of sys.stderr.write() in IDhttp://bugs.python.org/issue22420 closed by terry.reedy#22427: TemporaryDirectory attempts to clean up twicehttp://bugs.python.org/issue22427 closed by serhiy.storchaka#22438: eventlet broke by python 2.7.xhttp://bugs.python.org/issue22438 closed by benjamin.peterson#22440: Setting SSLContext object's check_hostname manually might accihttp://bugs.python.org/issue22440 closed by christian.heimes#22443: read(1) blocks on unflushed outputhttp://bugs.python.org/issue22443 closed by Sworddragon#22446: Shortening code in abc.pyhttp://bugs.python.org/issue22446 closed by benjamin.peterson#22447: logging.config.fileConfig attempts to write to file even when http://bugs.python.org/issue22447 closed by vinay.sajip#22448: call_at/call_later with Timer cancellation can result in (prachttp://bugs.python.org/issue22448 closed by yselivanov#22451: filtertuple, filterstring and filterunicode don't have optimizhttp://bugs.python.org/issue22451 closed by pitrou#22459: str.strip() documentation: wrong examplehttp://bugs.python.org/issue22459 closed by python-dev#22461: Test failure: Lib/test/test_pydoc.py line 851, "topic?key=def"http://bugs.python.org/issue22461 closed by georg.brandl#22464: Speed up fractions implementationhttp://bugs.python.org/issue22464 closed by scoder#22467: Lib/http/server.py, inconsistent header casinghttp://bugs.python.org/issue22467 closed by r.david.murray#22469: Allow the "backslashreplace" error handler support decodinghttp://bugs.python.org/issue22469 closed by serhiy.storchaka#22471: Python build problems via Homebrew on Mac OS X when GNU core/fhttp://bugs.python.org/issue22471 closed by ned.deily#22478: tests for urllib2net are in bad shapeshttp://bugs.python.org/issue22478 closed by orsenthil#22479: strange behavior of importing random modulehttp://bugs.python.org/issue22479 closed by haypo#22481: Lists within tuples mutability issuehttp://bugs.python.org/issue22481 closed by ezio.melotti#22483: Copyright infringement on PyPIhttp://bugs.python.org/issue22483 closed by dstufft#22484: Build doc archives for RC versions, docs download broken for 3http://bugs.python.org/issue22484 closed by python-dev#22485: Documentation download links (3.4.2http://bugs.python.org/issue22485 closed by berker.peksag#22487: ABC register doesn't check abstract methodshttp://bugs.python.org/issue22487 closed by r.david.murray#22488: 3.4 rc2 docs download link brokenhttp://bugs.python.org/issue22488 closed by ned.deily#22498: frozenset allows modification via -= operatorhttp://bugs.python.org/issue22498 closed by ezio.melotti_______________________________________________Python-Dev mailing listPython-Dev@python.orghttps://mail.python.org/mailman/listinfo/python-devUnsubscribe: https://mail.python.org/mailman/options/python-dev/dario670%40gmail.com

30.06.17 19:09, Python tracker ????:
> ACTIVITY SUMMARY (2017-06-23 - 2017-06-30)
> Python tracker at http://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 6006 (-20)

Victor closed a half of hundred his issues.

_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: https://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

Le 1 juil. 2017 10:18 AM, "Serhiy Storchaka" <storchaka@gmail.com> a écrit :

Victor closed a half of hundred his issues.


Let me elaborate :-) I am still learning the new GitHub workflow, and it's
common that I forget to close issues after merging a change. I had many
issues that I forgot to update since we moved to GitHub.

I had also complex bugs splitted into small issues and it took time to fix
all branches and to wait for buildots to confirm that it's really fixed.

To finish, I closed a lot of issues that were older than 2 years because
the bug was fixed in the meanwhile in another issue, or just because I lost
track of the issue and also lost interest and I don't consider that the bug
or feature was worth it.

Victor

No stats for last week?

On Sat, Feb 9, 2019 at 3:11 AM Python tracker <status@bugs.python.org>
wrote:

>
> ACTIVITY SUMMARY (2019-02-01 - 2019-02-08)
> 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 6998 (+13)
> closed 40696 (+47)
> total 47694 (+60)
>
> Open issues with patches: 2783
>
> --
INADA Naoki <songofacandy@gmail.com>

On Thu, Feb 28, 2019, 8:02 AM INADA Naoki <songofacandy@gmail.com> wrote:

> No stats for last week?
>

Been missing for two weeks actually. I did not receive a summary on either
the 15th or 22nd.

>

On 2/28/2019 8:07 AM, Jonathan Goble wrote:
> On Thu, Feb 28, 2019, 8:02 AM INADA Naoki <songofacandy@gmail.com
> <mailto:songofacandy@gmail.com>> wrote:
>
> No stats for last week?
>
>
> Been missing for two weeks actually. I did not receive a summary on
> either the 15th or 22nd.

Ditto for me. I get pydev via gmane. Anyone missing the same issues
get pydev directly by email?


--
Terry Jan Reedy

_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: https://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

On Thu, Feb 28, 2019, 5:11 PM Terry Reedy <tjreedy@udel.edu> wrote:

> On 2/28/2019 8:07 AM, Jonathan Goble wrote:
> > On Thu, Feb 28, 2019, 8:02 AM INADA Naoki <songofacandy@gmail.com
> > <mailto:songofacandy@gmail.com>> wrote:
> >
> > No stats for last week?
> >
> >
> > Been missing for two weeks actually. I did not receive a summary on
> > either the 15th or 22nd.
>
> Ditto for me. I get pydev via gmane. Anyone missing the same issues
> get pydev directly by email?
>

I get direct emails only and stated my observation above. :-)

>

On 2/28/2019 2:18 PM, Jonathan Goble wrote:
> On Thu, Feb 28, 2019, 5:11 PM Terry Reedy <tjreedy@udel.edu
> <mailto:tjreedy@udel.edu>> wrote:
>
> On 2/28/2019 8:07 AM, Jonathan Goble wrote:
> > On Thu, Feb 28, 2019, 8:02 AM INADA Naoki
> <songofacandy@gmail.com <mailto:songofacandy@gmail.com>
> > <mailto:songofacandy@gmail.com <mailto:songofacandy@gmail.com>>>
> wrote:
> >
> >     No stats for last week?
> >
> >
> > Been missing for two weeks actually. I did not receive a summary on
> > either the 15th or 22nd.
>
> Ditto for me.  I get pydev via gmane.  Anyone missing the same issues
> get pydev directly by email?
>
>
> I get direct emails only and stated my observation above. :-)

I confirm and concur with Jonathan's observation, by searching my email
archive for this group list. So it is not just something about his
particular email address... except we both do use Google Mail services. 
I do check my Google SPAM box for the account, and it wasn't there
either, by recollection (I don't archive the SPAM, but delete it ASAP).

Can someone not using a Google email address also confirm?

Glenn

On 2/28/2019 5:38 PM, Glenn Linderman wrote:
> On 2/28/2019 2:18 PM, Jonathan Goble wrote:
>> On Thu, Feb 28, 2019, 5:11 PM Terry Reedy <tjreedy@udel.edu
>> <mailto:tjreedy@udel.edu>> wrote:
>>
>> On 2/28/2019 8:07 AM, Jonathan Goble wrote:
>> > On Thu, Feb 28, 2019, 8:02 AM INADA Naoki
>> <songofacandy@gmail.com <mailto:songofacandy@gmail.com>
>> > <mailto:songofacandy@gmail.com <mailto:songofacandy@gmail.com>>>
>> wrote:
>> >
>> >     No stats for last week?
>> >
>> >
>> > Been missing for two weeks actually. I did not receive a summary on
>> > either the 15th or 22nd.
>>
>> Ditto for me.  I get pydev via gmane.  Anyone missing the same issues
>> get pydev directly by email?
>>
>>
>> I get direct emails only and stated my observation above. :-)
>
> I confirm and concur with Jonathan's observation, by searching my email
> archive for this group list. So it is not just something about his
> particular email address... except we both do use Google Mail services.
> I do check my Google SPAM box for the account, and it wasn't there
> either, by recollection (I don't archive the SPAM, but delete it ASAP).
>
> Can someone not using a Google email address also confirm?

I effectively did when I said I access via gmane -- as a newsgroup via
NNTP. I am sure that the mail server sends directly to news.gmane.org
rather than through google.


--
Terry Jan Reedy


_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: https://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

On 2/28/2019 2:52 PM, Terry Reedy wrote:
> On 2/28/2019 5:38 PM, Glenn Linderman wrote:
>> On 2/28/2019 2:18 PM, Jonathan Goble wrote:
>>> On Thu, Feb 28, 2019, 5:11 PM Terry Reedy <tjreedy@udel.edu
>>> <mailto:tjreedy@udel.edu>> wrote:
>>>
>>>     On 2/28/2019 8:07 AM, Jonathan Goble wrote:
>>>     > On Thu, Feb 28, 2019, 8:02 AM INADA Naoki
>>>     <songofacandy@gmail.com <mailto:songofacandy@gmail.com>
>>>     > <mailto:songofacandy@gmail.com <mailto:songofacandy@gmail.com>>>
>>>     wrote:
>>>     >
>>>     >     No stats for last week?
>>>     >
>>>     >
>>>     > Been missing for two weeks actually. I did not receive a
>>> summary on
>>>     > either the 15th or 22nd.
>>>
>>>     Ditto for me.  I get pydev via gmane.  Anyone missing the same
>>> issues
>>>     get pydev directly by email?
>>>
>>>
>>> I get direct emails only and stated my observation above. :-)
>>
>> I confirm and concur with Jonathan's observation, by searching my
>> email archive for this group list. So it is not just something about
>> his particular email address... except we both do use Google Mail
>> services.  I do check my Google SPAM box for the account, and it
>> wasn't there either, by recollection (I don't archive the SPAM, but
>> delete it ASAP).
>>
>> Can someone not using a Google email address also confirm?
>
> I effectively did when I said I access via gmane -- as a newsgroup via
> NNTP.  I am sure that the mail server sends directly to news.gmane.org
> rather than through google.

That's a whole different protocol. I don't know all the configurations
for the server that sends the Summary messages, or how it is handled,
but you confirm it didn't get to gnane via NNTP, and Jonathan and I
confirm it didn't get to Google email servers, but neither one really
confirms that it didn't get to other email servers. Google email is
definitely different than other email servers.

There seems to be enough evidence that something went wrong somewhere,
though, and whoever maintains that process should start investigating,
but it would still be nice to get confirmation from a non-Google email
recipient whether they did or did not get the Summary messages.

I wonder if there is a way to manually send them, and if the missing two
weeks of activity can be reported... once the sending problem is
understood and resolved.

On Thu, Feb 28, 2019 at 6:57 PM Glenn Linderman <v+python@g.nevcal.com>
wrote:

> On 2/28/2019 2:52 PM, Terry Reedy wrote:
>
> On 2/28/2019 5:38 PM, Glenn Linderman wrote:
>
> On 2/28/2019 2:18 PM, Jonathan Goble wrote:
>
> On Thu, Feb 28, 2019, 5:11 PM Terry Reedy <tjreedy@udel.edu
> <mailto:tjreedy@udel.edu> <tjreedy@udel.edu>> wrote:
>
> On 2/28/2019 8:07 AM, Jonathan Goble wrote:
> > On Thu, Feb 28, 2019, 8:02 AM INADA Naoki
> <songofacandy@gmail.com <mailto:songofacandy@gmail.com>
> <songofacandy@gmail.com>
> > <mailto:songofacandy@gmail.com <songofacandy@gmail.com>
> <mailto:songofacandy@gmail.com> <songofacandy@gmail.com>>>
> wrote:
> >
> > No stats for last week?
> >
> >
> > Been missing for two weeks actually. I did not receive a summary on
> > either the 15th or 22nd.
>
> Ditto for me. I get pydev via gmane. Anyone missing the same issues
> get pydev directly by email?
>
>
> I get direct emails only and stated my observation above. :-)
>
>
> I confirm and concur with Jonathan's observation, by searching my email
> archive for this group list. So it is not just something about his
> particular email address... except we both do use Google Mail services. I
> do check my Google SPAM box for the account, and it wasn't there either, by
> recollection (I don't archive the SPAM, but delete it ASAP).
>
> Can someone not using a Google email address also confirm?
>
>
> I effectively did when I said I access via gmane -- as a newsgroup via
> NNTP. I am sure that the mail server sends directly to news.gmane.org
> rather than through google.
>
>
> That's a whole different protocol. I don't know all the configurations for
> the server that sends the Summary messages, or how it is handled, but you
> confirm it didn't get to gnane via NNTP, and Jonathan and I confirm it
> didn't get to Google email servers, but neither one really confirms that it
> didn't get to other email servers. Google email is definitely different
> than other email servers.
>
> There seems to be enough evidence that something went wrong somewhere,
> though, and whoever maintains that process should start investigating, but
> it would still be nice to get confirmation from a non-Google email
> recipient whether they did or did not get the Summary messages.
>
> I wonder if there is a way to manually send them, and if the missing two
> weeks of activity can be reported... once the sending problem is understood
> and resolved.
>

It's also possible that the fault is not in sending (we have evidence here
that two entirely different protocols have not received it, and they are
also not in the archives [1]), but in the generation of the report. Could
there have been a subtle change to the bpo tracker itself, or something
else along those lines, that is causing the script to fail silently before
it ever reaches the point of attempting to send? Or perhaps a disk ran out
of space somewhere?

[1] https://mail.python.org/pipermail/python-dev/2019-February/date.html

>
> It's also possible that the fault is not in sending (we have evidence here that two entirely different protocols have not received it, and they are also not in the archives [1]), but in the generation of the report. Could there have been a subtle change to the bpo tracker itself, or something else along those lines, that is causing the script to fail silently before it ever reaches the point of attempting to send? Or perhaps a disk ran out of space somewhere?
>
> [1] https://mail.python.org/pipermail/python-dev/2019-February/date.html

I suspect so. See "Open issues deltas (weekly)" graph in this page.
It is ended by 2/8.

https://bugs.python.org/issue?@template=stats

--
INADA Naoki <songofacandy@gmail.com>
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: https://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

On 2019-02-28 23:54, Glenn Linderman wrote:
> On 2/28/2019 2:52 PM, Terry Reedy wrote:
>> On 2/28/2019 5:38 PM, Glenn Linderman wrote:
>>> On 2/28/2019 2:18 PM, Jonathan Goble wrote:
>>>> On Thu, Feb 28, 2019, 5:11 PM Terry Reedy <tjreedy@udel.edu
>>>> <mailto:tjreedy@udel.edu>> wrote:
>>>>
>>>>     On 2/28/2019 8:07 AM, Jonathan Goble wrote:
>>>>     > On Thu, Feb 28, 2019, 8:02 AM INADA Naoki
>>>>     <songofacandy@gmail.com <mailto:songofacandy@gmail.com>
>>>>     > <mailto:songofacandy@gmail.com <mailto:songofacandy@gmail.com>>>
>>>>     wrote:
>>>>     >
>>>>     >     No stats for last week?
>>>>     >
>>>>     >
>>>>     > Been missing for two weeks actually. I did not receive a
>>>> summary on
>>>>     > either the 15th or 22nd.
>>>>
>>>>     Ditto for me.  I get pydev via gmane.  Anyone missing the same
>>>> issues
>>>>     get pydev directly by email?
>>>>
>>>>
>>>> I get direct emails only and stated my observation above. :-)
>>>
>>> I confirm and concur with Jonathan's observation, by searching my
>>> email archive for this group list. So it is not just something about
>>> his particular email address... except we both do use Google Mail
>>> services.  I do check my Google SPAM box for the account, and it
>>> wasn't there either, by recollection (I don't archive the SPAM, but
>>> delete it ASAP).
>>>
>>> Can someone not using a Google email address also confirm?
>>
>> I effectively did when I said I access via gmane -- as a newsgroup via
>> NNTP.  I am sure that the mail server sends directly to news.gmane.org
>> rather than through google.
>
> That's a whole different protocol. I don't know all the configurations
> for the server that sends the Summary messages, or how it is handled,
> but you confirm it didn't get to gnane via NNTP, and Jonathan and I
> confirm it didn't get to Google email servers, but neither one really
> confirms that it didn't get to other email servers. Google email is
> definitely different than other email servers.
>
> There seems to be enough evidence that something went wrong somewhere,
> though, and whoever maintains that process should start investigating,
> but it would still be nice to get confirmation from a non-Google email
> recipient whether they did or did not get the Summary messages.
>
> I wonder if there is a way to manually send them, and if the missing two
> weeks of activity can be reported... once the sending problem is
> understood and resolved.
>
I subscribed at https://mail.python.org/mailman/listinfo/python-dev and
I don't use Google for email. I didn't receive them either.
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: https://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

On 2/28/2019 6:54 PM, Glenn Linderman wrote:

> There seems to be enough evidence that something went wrong somewhere,
> though, and whoever maintains that process should start investigating,
> but it would still be nice to get confirmation from a non-Google email
> recipient whether they did or did not get the Summary messages.
>
> I wonder if there is a way to manually send them, and if the missing two
> weeks of activity can be reported... once the sending problem is
> understood and resolved.

I posted a note to the core-workflow list, but I don't know if anyone
with power or knowledge still reads it.

To get a listing, go to the tracker search page, put
2019-02-09 to 2019-03-01
in the date box, and change status to don't care. At the moment, this
returns 204 issues.

--
Terry Jan Reedy

_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: https://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

On Fri, Mar 1, 2019 at 5:59 AM Terry Reedy <tjreedy@udel.edu> wrote:
>
> On 2/28/2019 6:54 PM, Glenn Linderman wrote:
>
> > There seems to be enough evidence that something went wrong somewhere,
> > though, and whoever maintains that process should start investigating,
> > but it would still be nice to get confirmation from a non-Google email
> > recipient whether they did or did not get the Summary messages.
> >
> > I wonder if there is a way to manually send them, and if the missing two
> > weeks of activity can be reported... once the sending problem is
> > understood and resolved.
>
> I posted a note to the core-workflow list, but I don't know if anyone
> with power or knowledge still reads it.
>

The tracker got migrated recently, and that's the most likely cause of
the missing reports.
We'll look into it and get them back :)

> To get a listing, go to the tracker search page, put
> 2019-02-09 to 2019-03-01
> in the date box, and change status to don't care. At the moment, this
> returns 204 issues.
>
> --
> Terry Jan Reedy
>
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: https://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

On Fri, Mar 1, 2019 at 8:05 AM Ezio Melotti <ezio.melotti@gmail.com> wrote:
>
> On Fri, Mar 1, 2019 at 5:59 AM Terry Reedy <tjreedy@udel.edu> wrote:
> >
> > On 2/28/2019 6:54 PM, Glenn Linderman wrote:
> >
> > > There seems to be enough evidence that something went wrong somewhere,
> > > though, and whoever maintains that process should start investigating,
> > > but it would still be nice to get confirmation from a non-Google email
> > > recipient whether they did or did not get the Summary messages.
> > >
> > > I wonder if there is a way to manually send them, and if the missing two
> > > weeks of activity can be reported... once the sending problem is
> > > understood and resolved.
> >
> > I posted a note to the core-workflow list, but I don't know if anyone
> > with power or knowledge still reads it.
> >
>
> The tracker got migrated recently, and that's the most likely cause of
> the missing reports.
> We'll look into it and get them back :)
>

Ernest promptly fixed the issue so last week report was sent out correctly.
I just generated and sent out the two reports that were missing and
updated the tracker stats at
https://bugs.python.org/issue?@template=stats
Note that some values in the report might be a bit off (for example,
the list of issues waiting for review doesn't include issues that were
closed after the selected period, and the patch count includes issues
created before or during the selected period even if a patch was
uploaded after the selected period).
The issues counts and deltas at the top of the summary should be correct.
Let me know if you notice any other problem (and thanks Ned for
bringing this to my attention!).

Best Regards,
Ezio Melotti

> > To get a listing, go to the tracker search page, put
> > 2019-02-09 to 2019-03-01
> > in the date box, and change status to don't care. At the moment, this
> > returns 204 issues.
> >
> > --
> > Terry Jan Reedy
> >
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: https://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

Thank you for fixing it.Weekly status give me motivation to look issues.

--
Inada Naoki <songofacandy@gmail.com>
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: https://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

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 <brett@python.org> wrote:
>
> Can we shut this down or unsubscribe the weekly email?
>
> On Fri, May 13, 2022 at 11:13 AM Python tracker <status@bugs.python.org> 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:
>> 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-leave@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-leave@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 send an email to python-dev-leave@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/BWHOPLP36N6QZTVT57DJ6U2WBEE5UB3Z/
Code of Conduct: http://python.org/psf/codeofconduct/

On Fri, 13 May 2022 at 19:54, Brett Cannon <brett@python.org> 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-leave@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/

>
> 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

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-leave@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/