Re: [Python-Dev] PEP 567 pre v3

2018-01-10 Thread Chris Jerdonek
On Wed, Jan 10, 2018 at 10:58 PM, Yury Selivanov wrote: > On Thu, Jan 11, 2018 at 10:35 AM, Chris Jerdonek > wrote: >> On Mon, Jan 8, 2018 at 11:02 PM, Nathaniel Smith wrote: >>> Right now, the set of valid states for a

Re: [Python-Dev] PEP 567 pre v3

2018-01-10 Thread Yury Selivanov
On Thu, Jan 11, 2018 at 10:35 AM, Chris Jerdonek wrote: > On Mon, Jan 8, 2018 at 11:02 PM, Nathaniel Smith wrote: >> Right now, the set of valid states for a ContextVar are: it can hold >> any Python object, or it can be undefined. However, the only way

Re: [Python-Dev] PEP 567 pre v3

2018-01-10 Thread Yury Selivanov
On Thu, Jan 11, 2018 at 10:39 AM, Ethan Furman wrote: > On 01/10/2018 10:23 PM, Yury Selivanov wrote: [..] >> Therefore I'm still in favour of keeping the current PEP 567 >> behaviour. > > > To be clear: We'll now be able to specify a default when we create the > variable,

Re: [Python-Dev] PEP 567 pre v3

2018-01-10 Thread Ethan Furman
On 01/10/2018 10:23 PM, Yury Selivanov wrote: On Thu, Jan 11, 2018 at 4:44 AM, Nathaniel Smith wrote: It may have gotten lost in that email, but my actual favorite approach is that we make the signatures: ContextVar(name, *, initial_value) # or even (*, name, initial_value) ContextVar.get()

Re: [Python-Dev] PEP 567 pre v3

2018-01-10 Thread Chris Jerdonek
On Mon, Jan 8, 2018 at 11:02 PM, Nathaniel Smith wrote: > Right now, the set of valid states for a ContextVar are: it can hold > any Python object, or it can be undefined. However, the only way it > can be in the "undefined" state is in a new Context where it has never > had a

Re: [Python-Dev] PEP 567 pre v3

2018-01-10 Thread Yury Selivanov
On Thu, Jan 11, 2018 at 4:44 AM, Nathaniel Smith wrote: [..] > It may have gotten lost in that email, but my actual favorite approach > is that we make the signatures: > > ContextVar(name, *, initial_value) # or even (*, name, initial_value) > ContextVar.get() >

Re: [Python-Dev] PEP 567 pre v3

2018-01-10 Thread Nick Coghlan
On 11 January 2018 at 10:44, Nathaniel Smith wrote: > It may have gotten lost in that email, but my actual favorite approach > is that we make the signatures: > > ContextVar(name, *, initial_value) # or even (*, name, initial_value) > ContextVar.get() > ContextVar.set(value) > >

Re: [Python-Dev] PEP 567 pre v3

2018-01-10 Thread Nathaniel Smith
On Tue, Jan 9, 2018 at 3:41 AM, Yury Selivanov wrote: > On Tue, Jan 9, 2018 at 11:02 AM, Nathaniel Smith wrote: >> Right now, the set of valid states for a ContextVar are: it can hold >> any Python object, or it can be undefined. However, the only way it

Re: [Python-Dev] Bug report in audioop module.

2018-01-10 Thread MRAB
On 2018-01-10 20:37, Moses Egypt wrote: I was told to post this here when I asked what to do on the python reddit. This is the issue: https://bugs.python.org/issue32004 It has received no response since I posted it two months ago, so I figured I didn't fill something out correctly to get it

Re: [Python-Dev] Bug report in audioop module.

2018-01-10 Thread Nick Coghlan
On 11 January 2018 at 06:37, Moses Egypt wrote: > I was told to post this here when I asked what to do on the python reddit. > This is the issue: > https://bugs.python.org/issue32004 Thank you for taking the time to file that! > It has received no response since I

Re: [Python-Dev] PEP 567 v2

2018-01-10 Thread Nathaniel Smith
On Tue, Jan 9, 2018 at 2:59 AM, Yury Selivanov wrote: > > >> On Jan 9, 2018, at 11:18 AM, Nathaniel Smith wrote: >> The approach I took in PEP 568 is even simpler, I think. The PEP is a >> few pages long because I wanted to be exhaustive to make sure we >>

[Python-Dev] Bug report in audioop module.

2018-01-10 Thread Moses Egypt
I was told to post this here when I asked what to do on the python reddit. This is the issue: https://bugs.python.org/issue32004 It has received no response since I posted it two months ago, so I figured I didn't fill something out correctly to get it put on someone's tracker. This is my first

Re: [Python-Dev] Thoughts on "contexts". PEPs 550, 555, 567, 568

2018-01-10 Thread Guido van Rossum
I'm sorry, Koos, but based on your past contributions I am not interested in discussing this topic with you. On Wed, Jan 10, 2018 at 8:58 AM, Koos Zevenhoven wrote: > The status of PEP 555 is just a side track. Here, I took a step back > compared to what went into PEP 555. >

Re: [Python-Dev] Thoughts on "contexts". PEPs 550, 555, 567, 568

2018-01-10 Thread Koos Zevenhoven
The status of PEP 555 is just a side track. Here, I took a step back compared to what went into PEP 555. —Koos On Wed, Jan 10, 2018 at 6:21 PM, Guido van Rossum wrote: > The current status of PEP 555 is "Withdrawn". I have no interest in > considering it any more, so if

Re: [Python-Dev] Thoughts on "contexts". PEPs 550, 555, 567, 568

2018-01-10 Thread Guido van Rossum
The current status of PEP 555 is "Withdrawn". I have no interest in considering it any more, so if you'd rather see a decision from me I'll be happy to change it to "Rejected". On Tue, Jan 9, 2018 at 10:29 PM, Koos Zevenhoven wrote: > On Jan 10, 2018 07:17, "Yury Selivanov"

Re: [Python-Dev] Best Python API for exposing posix_spawn

2018-01-10 Thread Pablo Galindo Salgado
I think I really like Antoine's suggestion so I'm going to finish implementing it that way. I think this keeps the API simple, does not bring in the os module new dependencies, keeps the C implementation clean and is consistent with the rest of the posix module. I will post an update when is