On Sat, Oct 3, 2020, at 04:41, Serhiy Storchaka wrote:
> Should we continue to support non-type objects with __bases__ in
> issubclass()? If no, can we remove their support in 3.10 (it would fix a
> crash in issue41909) or after passing a deprecation period?
Er, to be clear, contrary to the
Hi Walter,
> https://github.com/python/cpython/commit/a8bf44d04915f7366d9f8dfbf84822ac37a4bab3
Le mar. 6 oct. 2020 à 17:02, Walter Dörwald a écrit :
> It would be even simpler to use unicodedata.lookup() which returns the
> unicode character when passed the name of the character
That was my
Thank you to the PSC and everybody else for your nice thoughts and kind
words. Glad to have helped out!
Best wishes,
//arry/
On 10/5/20 11:38 AM, Barry Warsaw wrote:
They say being a Python Release Manager is a thankless job, so the Python
Secret Underground (PSU), which emphatically
That's appreciated, but I think what's needed more is someone who actually
wants to undertake this project. It's not just a matter of running a small
script for hours -- someone will have to come up with a way to fuzz that is
actually useful for this particular situation (inserting random
Thank you Thank you, Larry! 3.4 and 3.5 were so critical to getting the
scientific & pydata data community over the 2to3 hump.
-Peter
On Mon, Oct 5, 2020 at 1:43 PM Barry Warsaw wrote:
> They say being a Python Release Manager is a thankless job, so the Python
> Secret Underground (PSU),
On 6 Oct 2020, at 16:22, Florian Bruhin wrote:
https://github.com/python/cpython/commit/a8bf44d04915f7366d9f8dfbf84822ac37a4bab3
commit: a8bf44d04915f7366d9f8dfbf84822ac37a4bab3
branch: master
author: Florian Bruhin
committer: GitHub
date: 2020-10-06T16:21:56+02:00
summary:
bpo-41944: No
I have access to a small Amazon Web Services credit through the end of
November 2020. I'd be happy to let your team use that credit in support of
the fuzzing validation mentioned below.
"(One area we have not explored extensively is rejection of all wrong
programs. We have unit tests that check
Victor Stinner schrieb am 05.10.20 um 12:25:
> Would you mind reporting the issue to
> https://github.com/python/core-workflow/issues so we can aggregate
> information about this issue?
Done.
Stefan
___
Python-Dev mailing list -- python-dev@python.org
Thank you for all your contributions, Larry!
Cheers,
Lysandros
On Tue, Oct 6, 2020 at 12:08 PM Nick Coghlan wrote:
> Thank you, Larry!
>
> Cheers,
> Nick.
> ___
> python-committers mailing list -- python-committ...@python.org
> To unsubscribe send an
Thank you, Larry!
Cheers,
Nick.
___
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
Stefan created https://github.com/python/core-workflow/issues/376
Victor
Le lun. 5 oct. 2020 à 12:25, Victor Stinner a écrit :
>
> Hi,
>
> Would you mind reporting the issue to
> https://github.com/python/core-workflow/issues so we can aggregate
> information about this issue?
>
> Latest
On 05Oct2020 22:14, Tal Einat wrote:
>You have my thanks as well, Larry.
And mine. - Cameron Simpson
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
12 matches
Mail list logo
