On Aug 24, 2017 11:02 AM, "Yury Selivanov" wrote:
On Thu, Aug 24, 2017 at 10:05 AM, Jim J. Jewett
wrote:
> On Thu, Aug 24, 2017 at 1:12 AM, Yury Selivanov > On Thu, Aug 24, 2017
> at 12:32 AM, Jim J. Jewett wrote:
If you look at this small example:
foo = new_context_key()
async def
On Thu, Aug 24, 2017 at 10:05 AM, Jim J. Jewett wrote:
> On Thu, Aug 24, 2017 at 1:12 AM, Yury Selivanov > On Thu, Aug 24, 2017
> at 12:32 AM, Jim J. Jewett wrote:
>
>> The key requirement for using immutable datastructures is to make
>> "get_execution_context" operation fast.
>
> Do you really n
On Thu, Aug 24, 2017 at 1:12 AM, Yury Selivanov > On Thu, Aug 24, 2017
at 12:32 AM, Jim J. Jewett wrote:
> The key requirement for using immutable datastructures is to make
> "get_execution_context" operation fast.
Do you really need the whole execution context, or do you just need
the current v
On Wed, Aug 23, 2017 at 9:32 PM, Jim J. Jewett wrote:
>> While the context is defined conceptually as a nested chain of
>> key:value mappings, we avoid using the mapping syntax because of the
>> way the values can shift dynamically out from under you based on who
>> called you
> ...
>> instead of
Hi Jim,
Sorry, I don't answer all questions/points directly. We are working
on a new version of the PEP that will hopefully address most of them.
Some comments inlined below:
On Thu, Aug 24, 2017 at 12:32 AM, Jim J. Jewett wrote:
[..]
> I still don't see how this is different from a ChainMap.
