[Python-Dev] Re: [python-committers] Thank you Larry Hastings!

[Cameron Simpson]

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
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/KOWF7E5UN7BWE23TVLPJCDUD4EHZJCQK/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: PR checks hang because travis does not report back to github

[Victor Stinner]

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 changes related to Travis CI.
>
> Travis CI migrated from legacy API to new GitHub Action API:
> https://github.com/python/core-workflow/issues/371
>
> Removal of old webhooks:
> https://github.com/python/core-workflow/issues/374
>
> Travis CI can be reported/discussed at:
> https://travis-ci.community/
>
> --
>
> If Travis CI is made optional (not mandatory), can we mark another
> Linux CI as mandatory? Like the "GitHub Action Ubuntu" job? I didn't
> pay attention to whether it's reliable or not.
>
> In my experience, no CI is reliable, and all CI need attention from
> time to time :-)
>
> Victor
>
> Le dim. 4 oct. 2020 à 19:46, Stefan Behnel  a écrit :
> >
> > Hi devs,
> >
> > I have a trivial documentation PR
> >
> > https://github.com/python/cpython/pull/22464
> >
> > for which travis (unsurprisingly) had a successful run,
> >
> > https://travis-ci.com/github/python/cpython/builds/187435578
> >
> > but github lists the travis build as "created" instead of "passed".
> >
> > https://github.com/python/cpython/pull/22464/checks?check_run_id=1188595760
> >
> > I already tried closing the PR and reopening it, and also triggering the
> > build again on travis side, but github still fails to pick up the build 
> > status.
> >
> > I tried creating a new PR, but it seems that github (or travis) deduplicate
> > the build requests and still refer to the original build, so that there is
> > still no response from travis.
> >
> > I also cannot find a way to terminate the checks process in github, or
> > otherwise make it stop waiting for Godot.
> >
> > Is this a known issue? Is there anything I can do about it?
> >
> > Thanks,
> > Stefan
> > ___
> > 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/4TNKVOJ2LUJZZHHIBNORZ7GIVMYMNDER/
> > Code of Conduct: http://python.org/psf/codeofconduct/
>
>
>
> --
> Night gathers, and now my watch begins. It shall not end until my death.



-- 
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-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/5CNZYKADCL72CUEFJYC2NYP2M2PYZR26/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: [python-committers] Thank you Larry Hastings!

[Nick Coghlan]

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 
https://mail.python.org/archives/list/python-dev@python.org/message/5JGI6OUBQ3TYLO5E6ZKNH5OM3SKYIO4V/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: [python-committers] Re: Thank you Larry Hastings!

[Lysandros Nikolaou]

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 email to python-committers-le...@python.org
> https://mail.python.org/mailman3/lists/python-committers.python.org/
> Message archived at
> https://mail.python.org/archives/list/python-committ...@python.org/message/5JGI6OUBQ3TYLO5E6ZKNH5OM3SKYIO4V/
> Code of Conduct: https://www.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/I5CJ46COXEGV7R3OA3NVQN2DNUAL5OEJ/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: PR checks hang because travis does not report back to github

[Stefan Behnel]

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
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/77GIBSETK44CPRBTF34VNR7CRT66WUGP/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] PEP 617 -- New PEG parser for CPython

[Brett Lovgren]

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 for a certain number of explicit
rejections, but more work could be done, e.g. by using a fuzzer that
inserts random subtle bugs into existing code. We're open to help in this
area.)"
https://www.python.org/dev/peps/pep-0617/#validation

Sincerely,
Brett
___
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/4IG64CLKT4HTQOOYGUHCUUGWNJROCN5A/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: [Python-checkins] bpo-41944: No longer call eval() on content received via HTTP in the UnicodeNames tests (GH-22575)

[Walter Dörwald]

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 longer call eval() on content received via HTTP in the 
UnicodeNames tests (GH-22575)


Similarly to GH-22566, those tests called eval() on content received 
via
HTTP in test_named_sequences_full. This likely isn't exploitable 
because

unicodedata.lookup(seqname) is called before self.checkletter(seqname,
None) - thus any string which isn't a valid unicode character name
wouldn't ever reach the checkletter method.

Still, it's probably better to be safe than sorry.

files:
M Lib/test/test_ucn.py
[...]
 # Helper that put all \N escapes inside eval'd raw strings,
 # to make sure this script runs even if the compiler
 # chokes on \N escapes
-res = eval(r'"\N{%s}"' % name)
+res = ast.literal_eval(r'"\N{%s}"' % name)
 self.assertEqual(res, code)
 return res


It would be even simpler to use unicodedata.lookup() which returns the 
unicode character when passed the name of the character, e.g.



unicodedata.lookup("NO-BREAK SPACE")

'\xa0'

Servus,
   Walter
___
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/3S7BHOFRG3KYYXQUBGZBFTDIDN2IHG3M/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: Thank you Larry Hastings!

[Peter Wang]

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), which emphatically does not exist, hereby
> officially doesn’t thank Larry for his years of diligent service as the
> Python 3.4 and 3.5 release manager.
>
> On the other hand, the Python Steering Council, Python Software
> Foundation, and worldwide Python community, all of which emphatically *do*
> exist, all extend our heartfelt thanks to Larry for his excellent
> stewardship of Python 3.4 and 3.5!
>
> Python 3.4 and 3.5 were both pivotal releases.  While the features of
> these two releases are too numerous to mention here, they introduced such
> staples as:
>
> * asyncio
> * enum
> * pathlib
> * async and await keywords
> * matrix multiplication operators
> * typing and zipapp modules
>
> and so much more.  For details, see:
>
> * https://docs.python.org/3/whatsnew/3.4.html
> * https://docs.python.org/3/whatsnew/3.5.html
>
> Larry’s first official release of 3.4.0a1 was on 2013-08-03 and his last
> Python 3.5.10 release was 2020-09-05.  That’s 7 years of exemplary release
> managing!
>
> Larry, from all of us, and from me personally, thank you so much for your
> invaluable contributions to Python.  Enjoy your retirement!
>
> Cheers,
> -Barry (on behalf of the PSC and PSF)
>
> ___
> 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/QGIHFU64TBYT56K6M5A5LYTYTSVFKHWQ/
> 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/4CUKCSEICPIWWE4SDGLZU37VGYOUH3DP/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: PEP 617 -- New PEG parser for CPython

[Guido van Rossum]

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 characters
in files isn't going to be very effective). If someone wants to give that a
try I'm sure they'd be delighted to use up the rest of your AWS budget. :-)

On Tue, Oct 6, 2020 at 7:02 AM Brett Lovgren 
wrote:

> 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 for a certain number of explicit
> rejections, but more work could be done, e.g. by using a fuzzer that
> inserts random subtle bugs into existing code. We're open to help in this
> area.)"
> https://www.python.org/dev/peps/pep-0617/#validation
>
> Sincerely,
> Brett
> ___
> 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/4IG64CLKT4HTQOOYGUHCUUGWNJROCN5A/
> Code of Conduct: http://python.org/psf/codeofconduct/
>


-- 
--Guido van Rossum (python.org/~guido)
*Pronouns: he/him **(why is my pronoun here?)*

___
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/F6ELI34QWOPZNXKW73K6DTV27LXQZ76V/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: [python-committers] Thank you Larry Hastings!

[Larry Hastings]

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 does not exist, hereby officially 
doesn’t thank Larry for his years of diligent service as the Python 3.4 and 3.5 
release manager.

On the other hand, the Python Steering Council, Python Software Foundation, and 
worldwide Python community, all of which emphatically *do* exist, all extend 
our heartfelt thanks to Larry for his excellent stewardship of Python 3.4 and 
3.5!

Python 3.4 and 3.5 were both pivotal releases.  While the features of these two 
releases are too numerous to mention here, they introduced such staples as:

* asyncio
* enum
* pathlib
* async and await keywords
* matrix multiplication operators
* typing and zipapp modules

and so much more.  For details, see:

* https://docs.python.org/3/whatsnew/3.4.html
* https://docs.python.org/3/whatsnew/3.5.html

Larry’s first official release of 3.4.0a1 was on 2013-08-03 and his last Python 
3.5.10 release was 2020-09-05.  That’s 7 years of exemplary release managing!

Larry, from all of us, and from me personally, thank you so much for your 
invaluable contributions to Python.  Enjoy your retirement!

Cheers,
-Barry (on behalf of the PSC and PSF)


___
python-committers mailing list -- python-committ...@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committ...@python.org/message/QGIHFU64TBYT56K6M5A5LYTYTSVFKHWQ/
Code of Conduct: https://www.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/2EWB7WU7Q2RXDYX4BBL3NDHHWNM6DEFT/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: [Python-checkins] bpo-41944: No longer call eval() on content received via HTTP in the UnicodeNames tests (GH-22575)

[Victor Stinner]

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 first idea as well when I reviewed the change, but the
function contains this comment:

def checkletter(self, name, code):
# Helper that put all \N escapes inside eval'd raw strings,
# to make sure this script runs even if the compiler
# chokes on \N escapes

test_named_sequences_full() checks that unicodedata.lookup() works,
but that checkletter() raises a SyntaxError. Look at the code ;-)

Victor
-- 
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-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/LNZSHNATY7MSO5JKHELR433TCJ7ZZ5YR/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: Do we still need a support of non-type objects in issubclass()?

[Random832]

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 subject line, you're not suggesting removing 
support for non-type objects altogether [i.e. with __subclasscheck__], right? 
Just the ability to use a non-slotted __bases__ attribute?
___
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/BVDGIKBAM6U4CNGUP2BODSX62I7RTNLZ/
Code of Conduct: http://python.org/psf/codeofconduct/