[Python-Dev] [RELEASE] Python 3.7.3 is now available

2019-03-25 Thread Ned Deily
https://blog.python.org/2019/03/python-373-is-now-available.html Python 3.7.3 is now available. Python 3.7.3 is the next maintenance release of Python 3.7, the latest feature release of Python. You can find Python 3.7.3 here: https://www.python.org/downloads/release/python-373/ See the What’s

Re: [Python-Dev] BDFL-Delegate appointments for several PEPs

2019-03-25 Thread Brett Cannon
On Sun, Mar 24, 2019 at 2:03 PM Terry Reedy wrote: > On 3/24/2019 8:21 AM, Nick Coghlan wrote: > > > We'll be announcing those appointments as we go, so I'm happy to > > report that I will be handling the BDFL-Delegate responsibilities for > > the following PEPs: > > Where do we discuss these? >

Re: [Python-Dev] Replacement for array.array('u')?

2019-03-25 Thread Steve Dower
On 25Mar2019 0812, Martin (gzlist) wrote: On Fri, 22 Mar 2019 at 16:12, Steve Dower wrote: On 22Mar2019 0433, Antoine Pitrou wrote: The question is: why would you use a array.array() with a Windows C API? I started replying to this with a whole lot of examples, and eventually convinced myse

Re: [Python-Dev] Replacement for array.array('u')?

2019-03-25 Thread Martin (gzlist) via Python-Dev
On Fri, 22 Mar 2019 at 16:12, Steve Dower wrote: > > On 22Mar2019 0433, Antoine Pitrou wrote: > > The question is: why would you use a array.array() with a Windows C API? > > I started replying to this with a whole lot of examples, and eventually > convinced myself that you wouldn't (or shouldn't)

Re: [Python-Dev] Removing PendingDeprecationWarning

2019-03-25 Thread Inada Naoki
On Mon, Mar 25, 2019 at 8:53 PM Nick Coghlan wrote: > > On Mon, 25 Mar 2019 at 14:39, Inada Naoki wrote: > > We have many ways to deprecation: > > > > * Document only deprecation (no warning) -- no actual removal is planned. > > * FutureWarning -- to warn end users. > > * DeprecationWarning -- to

Re: [Python-Dev] Removing PendingDeprecationWarning

2019-03-25 Thread Antoine Pitrou
On Mon, 25 Mar 2019 21:53:07 +1000 Nick Coghlan wrote: > On Mon, 25 Mar 2019 at 14:39, Inada Naoki wrote: > > We have many ways to deprecation: > > > > * Document only deprecation (no warning) -- no actual removal is planned. > > * FutureWarning -- to warn end users. > > * DeprecationWarning --

Re: [Python-Dev] Removing PendingDeprecationWarning

2019-03-25 Thread Nick Coghlan
On Mon, 25 Mar 2019 at 14:39, Inada Naoki wrote: > We have many ways to deprecation: > > * Document only deprecation (no warning) -- no actual removal is planned. > * FutureWarning -- to warn end users. > * DeprecationWarning -- to warn Python developers. > * PendingDeprecationWarning -- to warn P

Re: [Python-Dev] BDFL-Delegate appointments for several PEPs

2019-03-25 Thread Cameron Simpson
On 25Mar2019 03:52, Terry Reedy wrote: On 3/25/2019 12:27 AM, Cameron Simpson wrote: I was thinking about IDLE and its tangled web of circular inports, but I am now convinced that this change will not affect it.  Indeed, idlelib/pyshell.py already implements idea of the proposal, ending with

Re: [Python-Dev] BDFL-Delegate appointments for several PEPs

2019-03-25 Thread Terry Reedy
On 3/25/2019 12:27 AM, Cameron Simpson wrote: On 24Mar2019 23:22, Terry Reedy wrote: On 3/24/2019 10:01 PM, Terry Reedy wrote: On 3/24/2019 7:00 PM, Cameron Simpson wrote: Did you have a specific scenario in mind? I was thinking about IDLE and its tangled web of circular inports, but I am