Re: [Python-ideas] "Assignment expression" with function call-alike syntax

2018-05-23 6:32 GMT+09:00 Kirill Balunov : > Just one more variation on "assignment exression" syntax to make the list > more complete :) Sorry, if something similar has already been suggested. > The idea is to use function's call-like syntax in the from: `this( name = >

Re: [Python-ideas] PEP 572 version 2: Statement-Local Name Bindings

FWIW, I thought another way which provides cache object library, it seems to just work in some cases. But it doesn't create statement local scope and might be difficult to read because looks ordinary expression doing magic. Chris, would you append the library to alternative proposal section?

Re: [Python-ideas] π = math.pi

correct? > > -- > Ryan (ライアン) > Yoko Shimomura > ryo (supercell/EGOIST) > Hiroyuki Sawano >> everyone else > http://refi64.com > > On Jun 1, 2017 2:27 PM, "Masayuki YAMAMOTO" <ma3yuki.8mam...@gmail.com> > wrote: > > Hi Stephan, > > &g

Re: [Python-ideas] π = math.pi

Hi Stephan, Nevertheless, I would like to point out that the encoding assumed for a > Python3 source file never depends on the locale. > Yeah, as you pointed out. I'd like to correct my said. > My understanding is that in the default encoding for Python source files > (utf-8), East Asian

Re: [Python-ideas] π = math.pi

The width of Greek letters is East Asian Ambiguous. Using ambiguous width characters possibly will be a reason that is source code layout break on specific locale. Masayuki 2017-06-01 15:47 GMT+09:00 Serhiy Storchaka : > What you are think about adding Unicode aliases for

Re: [Python-ideas] New PyThread_tss_ C-API for CPython

2016-12-31 16:42 GMT+09:00 Nick Coghlan <ncogh...@gmail.com>: > On 31 December 2016 at 08:24, Masayuki YAMAMOTO <ma3yuki.8mam...@gmail.com > > wrote: > >> I have read the discussion and I'm sure that use structure as Py_tss_t >> instead of platform-speci

Re: [Python-ideas] New PyThread_tss_ C-API for CPython

I have read the discussion and I'm sure that use structure as Py_tss_t instead of platform-specific data type. Just as Steve said that Py_tss_t should be genuinely treated as an opaque type, the key state checking should provide macros or inline functions with name like PyThread_tss_is_created.

Re: [Python-ideas] New PyThread_tss_ C-API for CPython

2016-12-21 19:01 GMT+09:00 Erik Bray : > On Wed, Dec 21, 2016 at 2:10 AM, Nick Coghlan wrote: > > Ouch, I'd missed that, and I agree it's not a negligible implementation > > detail - there are definitely applications embedding CPython out there > that >

Re: [Python-ideas] New PyThread_tss_ C-API for CPython

2016-12-20 22:30 GMT+09:00 Erik Bray : > This is probably an implementation detail, but ISTM that even with > PyThread_call_once, it will be necessary to reset any used once_flags > manually in PyOS_AfterFork, essentially for the same reason the > autoTLSkey is reset there

Re: [Python-ideas] New PyThread_tss_ C-API for CPython

2016-12-17 18:35 GMT+09:00 Stephen J. Turnbull : > I don't understand this. I assume that there are no such platforms > supported at present. I would think that when such a platform becomes > supported, code supporting "key" functions becomes unsupportable

Re: [Python-ideas] New PyThread_tss_ C-API for CPython

Hi, I'm patch author, I don't need to say anything for Erik's draft. I feel awesome that it has been clearly to explain, especially for history of API and against PEP. Thanks for great job, Erik! Cheers, Masayuki ___ Python-ideas mailing list