I believe that the current status is: - assigning None isn't treated specially – it does mask any underlying values (which I think is what we want)
- there is currently no way to "unmask" - but it's generally agreed that there should be a way to do that, at least in some cases, to handle the save/restore issue I raised. It's just that Yury & Elvis wanted to deal with restructuring the PEP first before doing more work on the api details. -n On Aug 27, 2017 9:08 AM, "Jim J. Jewett" <jimjjew...@gmail.com> wrote: > Does setting an ImplicitScopeVar to None set the value to None, or just > remove it? > > If it removes it, does that effectively unmask a previously masked value? > > If it really sets to None, then is there a way to explicitly unmask > previously masked values? > > Perhaps the initial constructor should require an initial value > (defaulting to None) and the docs should give examples both for using a > sensible default value and for using a special "unset" marker. > > -jJ > > > > _______________________________________________ > Python-Dev mailing list > Python-Dev@python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: https://mail.python.org/mailman/options/python-dev/ > njs%40pobox.com > >
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
