Re: [Python-Dev] PEP 550 v4

2017-08-30 Thread Kevin Conway
> Can Execution Context be implemented outside of CPython I know I'm well late to the game and a bit dense, but where in the pep is the justification for this assertion? I ask because we buy something to solve the same problem in Twisted some time ago: https://bitbucket.org/hipchat/txlocal . We we

Re: [Python-Dev] PEP 550 v4

2017-08-30 Thread Yury Selivanov
On Wed, Aug 30, 2017 at 1:39 PM, Kevin Conway wrote: >> Can Execution Context be implemented outside of CPython > > I know I'm well late to the game and a bit dense, but where in the pep is > the justification for this assertion? I ask because we buy something to > solve the same problem in Twiste

Re: [Python-Dev] [Python-checkins] bpo-5001: More-informative multiprocessing error messages (#3079)

2017-08-30 Thread Oleg Broytman
Hi! On Wed, Aug 30, 2017 at 04:32:22PM +0200, Antoine Pitrou wrote: > On Wed, 30 Aug 2017 03:16:42 -0700 > Chris Jerdonek wrote: > > https://github.com/python/cpython/commit/bd73e72b4a9f019be514954b1d40e64dc3a5e81c > > > commit: bd73e72b4a9f019be514954b1d40e64dc3a5e81c > > > branch: master > >

Re: [Python-Dev] PEP 550 v4

2017-08-30 Thread Yury Selivanov
On Wed, Aug 30, 2017 at 8:19 AM, Koos Zevenhoven wrote: > On Wed, Aug 30, 2017 at 2:36 AM, Greg Ewing > wrote: >> >> Yury Selivanov wrote: >>> >>> While we want "yield from" to have semantics close to a function call, >> >> >> That's not what I said! I said that "yield from foo()" should >> have

Re: [Python-Dev] PEP 550 v4

2017-08-30 Thread Yury Selivanov
On Wed, Aug 30, 2017 at 9:44 AM, Yury Selivanov wrote: [..] >> FYI, I've been sketching an alternative solution that addresses these kinds >> of things. I've been hesitant to post about it, partly because of the >> PEP550-based workarounds that Nick, Nathaniel, Yury etc. have been >> describing, a

Re: [Python-Dev] [Python-checkins] bpo-5001: More-informative multiprocessing error messages (#3079)

2017-08-30 Thread Antoine Pitrou
On Wed, 30 Aug 2017 03:21:42 -0700 Chris Jerdonek wrote: > > https://github.com/python/cpython/commit/bd73e72b4a9f019be514954b1d40e64dc3a5e81c > > commit: bd73e72b4a9f019be514954b1d40e64dc3a5e81c > > branch: master > > author: Allen W. Smith, Ph.D > > committer: Antoine Pitrou > > date: 2017-08-

Re: [Python-Dev] [Python-checkins] bpo-5001: More-informative multiprocessing error messages (#3079)

2017-08-30 Thread Antoine Pitrou
On Wed, 30 Aug 2017 03:16:42 -0700 Chris Jerdonek wrote: > https://github.com/python/cpython/commit/bd73e72b4a9f019be514954b1d40e64dc3a5e81c > > commit: bd73e72b4a9f019be514954b1d40e64dc3a5e81c > > branch: master > > author: Allen W. Smith, Ph.D > > committer: Antoine Pitrou > > date: 2017-08-30

Re: [Python-Dev] PEP 550 v4

2017-08-30 Thread Yury Selivanov
On Wed, Aug 30, 2017 at 8:55 AM, Greg Ewing wrote: > Yury Selivanov wrote: > >> BTW we already have mechanisms to always propagate context to the >> caller -- just use threading.local() or a global variable. > > > But then you don't have a way to *not* propagate the > context change when you don't

Re: [Python-Dev] PEP 550 v4

2017-08-30 Thread Greg Ewing
Yury Selivanov wrote: BTW we already have mechanisms to always propagate context to the caller -- just use threading.local() or a global variable. But then you don't have a way to *not* propagate the context change when you don't want to. Here's my suggestion: Make an explicit distinction bet

Re: [Python-Dev] PEP 550 v4

2017-08-30 Thread Koos Zevenhoven
On Wed, Aug 30, 2017 at 2:36 AM, Greg Ewing wrote: > Yury Selivanov wrote: > >> While we want "yield from" to have semantics close to a function call, >> > > That's not what I said! I said that "yield from foo()" should > have semantics close to a function call. If you separate the > "yield from"

Re: [Python-Dev] [Python-checkins] bpo-5001: More-informative multiprocessing error messages (#3079)

2017-08-30 Thread Chris Jerdonek
> https://github.com/python/cpython/commit/bd73e72b4a9f019be514954b1d40e64dc3a5e81c > commit: bd73e72b4a9f019be514954b1d40e64dc3a5e81c > branch: master > author: Allen W. Smith, Ph.D > committer: Antoine Pitrou > date: 2017-08-30T00:52:18+02:00 > summary: > > bpo-5001: More-informative multiproce

Re: [Python-Dev] [Python-checkins] bpo-5001: More-informative multiprocessing error messages (#3079)

2017-08-30 Thread Chris Jerdonek
https://github.com/python/cpython/commit/bd73e72b4a9f019be514954b1d40e64dc3a5e81c > commit: bd73e72b4a9f019be514954b1d40e64dc3a5e81c > branch: master > author: Allen W. Smith, Ph.D > committer: Antoine Pitrou > date: 2017-08-30T00:52:18+02:00 > summary: > > ... > @@ -307,6 +309,10 @@ def imap(sel

Re: [Python-Dev] bpo-5001: More-informative multiprocessing error messages (#3079)

2017-08-30 Thread Paul Moore
On 30 August 2017 at 10:48, Nick Coghlan wrote: > On 30 August 2017 at 19:39, Antoine Pitrou wrote: >> On Wed, 30 Aug 2017 08:48:56 +0300 >> Serhiy Storchaka wrote: >>> Please, please don't forget to edit commit messages before merging. An >>> excessively verbose commit message will be kept in t

Re: [Python-Dev] bpo-5001: More-informative multiprocessing error messages (#3079)

2017-08-30 Thread Nick Coghlan
On 30 August 2017 at 19:39, Antoine Pitrou wrote: > On Wed, 30 Aug 2017 08:48:56 +0300 > Serhiy Storchaka wrote: >> Please, please don't forget to edit commit messages before merging. An >> excessively verbose commit message will be kept in the repository >> forever and will harm future developer

Re: [Python-Dev] bpo-5001: More-informative multiprocessing error messages (#3079)

2017-08-30 Thread Antoine Pitrou
On Wed, 30 Aug 2017 08:48:56 +0300 Serhiy Storchaka wrote: > 30.08.17 01:52, Antoine Pitrou пише: > > https://github.com/python/cpython/commit/bd73e72b4a9f019be514954b1d40e64dc3a5e81c > > commit: bd73e72b4a9f019be514954b1d40e64dc3a5e81c > > branch: master > > author: Allen W. Smith, Ph.D > > com