Re: [Python-Dev] Farewell, Python 3.4

Thank you for your service! On Wed, May 8, 2019, at 08:37, Larry Hastings wrote: > > > It's with a note of sadness that I announce the final retirement of > Python 3.4. The final release was back in March, but I didn't get > around to actually closing and deleting the 3.4 branch until this >

[Python-Dev] My PyCon talk on the GIL, the C-API, and subinterpreters

I just wanted to share links to my talk about the above, which I gave a week ago at PyCon. Enjoy! :) -eric video: https://youtu.be/7RlqbHCCVyc slides: https://bit.ly/2UMMJey project: https://github.com/ericsnowcurrently/multi-core-python ___

Re: [Python-Dev] Redoing failed PR checks

On 08.05.2019 22:47, Terry Reedy wrote: On 5/8/2019 10:23 AM, Eric V. Smith wrote: I think you can close and reopen the PR. That’s what I’m trying on my blocked PR. That works but reruns all the CI checks, including the ones already passed.  Some bots allow individual reruns, but it is not

Re: [Python-Dev] Redoing failed PR checks

On 5/8/2019 10:23 AM, Eric V. Smith wrote: I think you can close and reopen the PR. That’s what I’m trying on my blocked PR. That works but reruns all the CI checks, including the ones already passed. Some bots allow individual reruns, but it is not as clear as it should be. -- Terry

Re: [Python-Dev] Farewell, Python 3.4

Thank you for having been 3.4 release manager, Larry ! On 08.05.2019 17:36, Larry Hastings wrote: > > It's with a note of sadness that I announce the final retirement of > Python 3.4.  The final release was back in March, but I didn't get > around to actually closing and deleting the 3.4 branch

Re: [Python-Dev] Definition of equality check behavior

Ahh, I didn't locate the documentation on the NotImplemented constant as I was checking 2.7's docs, so I wasn't aware of the layer of indirection and fallback behavior for the operator. Sorry about that! Based on that, the right

[Python-Dev] Farewell, Python 3.4

It's with a note of sadness that I announce the final retirement of Python 3.4.  The final release was back in March, but I didn't get around to actually closing and deleting the 3.4 branch until this morning. Python 3.4 introduced many features we all enjoy in modern Python--the asyncio,

Re: [Python-Dev] Definition of equality check behavior

On Tue, 7 May 2019 at 22:31, Jordan Adler wrote: > Hey folks! > > Through the course of work on the future polyfills > that mimic > the behavior of Py3 builtins across versions of Python, we've discovered > that the equality check

Re: [Python-Dev] Hello

On May 8, 2019, at 10:13, Petr Viktorin wrote: > > Not sure what the original intent was, but I read that as: "Whenever you get > to sending your first post, include an introduction in it. But, before you > start actively participating, take your time to hang around and absorb the > culture."

Re: [Python-Dev] Redoing failed PR checks

I think you can close and reopen the PR. That’s what I’m trying on my blocked PR. -- Eric V. Smith True Blade Systems, Inc (301) 859-4544 > On May 8, 2019, at 10:07 AM, Mark Shannon wrote: > > Hi, > > How do I redo a failed PR check? > The appveyor failure for

Re: [Python-Dev] Hello

On 5/7/19 9:08 PM, Ben Kane wrote: Sorry Victor, I must have misinterpreted this snippet from the mailbot. Maybe it would be a good idea to re-word it? I'll be happy to open an issue for that in an appropriate mailing list if you think that would help. > Welcome to the Python-Dev@python.org

[Python-Dev] Redoing failed PR checks

Hi, How do I redo a failed PR check? The appveyor failure for https://github.com/python/cpython/pull/13181 appears to be spurious, but there is no obvious way to redo it. BTW, this is not the first time I've seen a PR blocked by a spurious appveyor failure. Cheers, Mark.