Re: [Python-Dev] PEP 515: Underscores in Numeric Literals

2016-02-12 Thread Paul Moore
On 12 February 2016 at 00:16, Steven D'Aprano wrote: > I think that there is broad agreement that: > > - the basic idea is sound > - leading underscores followed by digits are currently legal > identifiers and this will not change > - underscores should not follow the sign

[Python-Dev] Py_SETREF again

2016-02-12 Thread Serhiy Storchaka
Sorry to bringing this up again. I was hoping we were done with that. When discussing the name of the Py_SETREF macro I was supposed to add a pair of macros: for Py_DECREF and Py_XDECREF. But I got a lot of opinions to be limited to only one macro. On 28.02.14 15:58, Kristján Valur Jónsson

Re: [Python-Dev] Time for a change of random number generator?

2016-02-12 Thread Robert Kern
On 2016-02-12 04:15, Tim Peters wrote: [Greg Ewing ] The Mersenne Twister is no longer regarded as quite state-of-the art because it can get into states that produce long sequences that are not very random. There is a variation on MT called WELL that has better

Re: [Python-Dev] Py_SETREF again

2016-02-12 Thread Nick Coghlan
On 12 February 2016 at 19:45, Serhiy Storchaka wrote: > Now Raymond, who was not involved in the previous discussions, expressed the > view that we should to rename Py_SETREF to Py_XSETREF and add new Py_SETREF > that uses Py_DECREF for using in the code that used Py_DECREF

Re: [Python-Dev] Modify PyMem_Malloc to use pymalloc for performance

2016-02-12 Thread Victor Stinner
ping? 2016-02-08 15:18 GMT+01:00 Victor Stinner : > 2016-02-04 15:05 GMT+01:00 M.-A. Lemburg : >> Sometimes, yes, but we also do allocations for e.g. >> parsing values in Python argument tuples (e.g. using >> "es" or "et"): >> >>

Re: [Python-Dev] Py_SETREF again

2016-02-12 Thread Serhiy Storchaka
On 12.02.16 15:43, Georg Brandl wrote: On 02/12/2016 10:45 AM, Serhiy Storchaka wrote: Sorry to bringing this up again. I was hoping we were done with that. When discussing the name of the Py_SETREF macro I was supposed to add a pair of macros: for Py_DECREF and Py_XDECREF. But I got a lot of

Re: [Python-Dev] Modify PyMem_Malloc to use pymalloc for performance

2016-02-12 Thread Victor Stinner
Hi, 2016-02-12 14:31 GMT+01:00 M.-A. Lemburg : > Sorry, your email must gotten lost in my inbox. no problemo > Yes, but those are part of the stdlib. You'd need to check > a few C extensions which are not tested as part of the stdlib, > e.g. numpy, scipy, lxml, pillow, etc.

Re: [Python-Dev] Py_SETREF again

2016-02-12 Thread Georg Brandl
On 02/12/2016 10:45 AM, Serhiy Storchaka wrote: > Sorry to bringing this up again. I was hoping we were done with that. > > When discussing the name of the Py_SETREF macro I was supposed to add a > pair of macros: for Py_DECREF and Py_XDECREF. But I got a lot of > opinions to be limited to only

Re: [Python-Dev] Modify PyMem_Malloc to use pymalloc for performance

2016-02-12 Thread M.-A. Lemburg
On 12.02.2016 12:18, Victor Stinner wrote: > ping? Sorry, your email must gotten lost in my inbox. > 2016-02-08 15:18 GMT+01:00 Victor Stinner : >> 2016-02-04 15:05 GMT+01:00 M.-A. Lemburg : >>> Sometimes, yes, but we also do allocations for e.g. >>>

[Python-Dev] Summary of Python tracker Issues

2016-02-12 Thread Python tracker
ACTIVITY SUMMARY (2016-02-05 - 2016-02-12) Python tracker at http://bugs.python.org/ To view or respond to any of the issues listed below, click on the issue. Do NOT respond to this message. Issues counts and deltas: open5417 ( +4) closed 32691 (+50) total 38108 (+54) Open issues

[Python-Dev] [ANN] MicroPython 1.6

2016-02-12 Thread Paul Sokolovsky
Hello, MicroPython is a lean and efficient Python implementation for microcontrollers, embedded, and mobile systems (which also runs just as fine on desktops, servers, and clouds). https://github.com/micropython/micropython https://github.com/micropython/micropython/releases/tag/v1.6 There're

Re: [Python-Dev] PEP 515: Underscores in Numeric Literals

2016-02-12 Thread Chris Barker
On Fri, Feb 12, 2016 at 1:00 AM, Paul Moore wrote: > > I have no opinion on anything other than that whatever syntax is > implemented as long as it allows single underscores between digits, > such as > > 1_000_000 > > Everything else is irrelevant to me, and if I read code

Re: [Python-Dev] PEP 515: Underscores in Numeric Literals

2016-02-12 Thread Andrew Barnert via Python-Dev
On Feb 12, 2016, at 12:58, Glenn Linderman wrote: > >> On 2/12/2016 12:06 PM, Chris Barker wrote: >> As for the SS# example -- it seems a bad idea to me to store a SS# number as >> an integer anyway -- so all the weird IDs etc. formats aren't really >> relevant... > >

Re: [Python-Dev] PEP 515: Underscores in Numeric Literals

2016-02-12 Thread Paul Moore
On 12 February 2016 at 20:06, Chris Barker wrote: > As Paul said, as long as I can do the above, I'll be fine, but I think > everyone's source code will be a lot cleaner in the long run if you don't > have the option of doing who knows what weird arrangement Just to be

Re: [Python-Dev] PEP 515: Underscores in Numeric Literals

2016-02-12 Thread Glenn Linderman
On 2/12/2016 12:06 PM, Chris Barker wrote: On Fri, Feb 12, 2016 at 1:00 AM, Paul Moore > wrote: I have no opinion on anything other than that whatever syntax is implemented as long as it allows single underscores between digits,

Re: [Python-Dev] PEP 515: Underscores in Numeric Literals

2016-02-12 Thread MRAB
On 2016-02-12 20:06, Chris Barker wrote: On Fri, Feb 12, 2016 at 1:00 AM, Paul Moore > wrote: I have no opinion on anything other than that whatever syntax is implemented as long as it allows single underscores between digits, such