On 17/03/2020 7:00 pm, Steve Dower wrote:
On 17Mar2020 1803, Chris Angelico wrote:
On Wed, Mar 18, 2020 at 3:50 AM Mark Shannon <m...@hotpy.org> wrote:
The accessibility of a thread-local variable is a strict superset of
that of a function-local variable.
Therefore storing the thread state in a thread-local variable is at
least as capable as passing thread-state as a parameter.
And by that logic, globals are even more capable. I don't understand
your point. Isn't the purpose of the tstate parameters to avoid the
problem of being unable to have multiple tstates within the same OS
thread? I think I've missed something here.
You haven't. Separating the Python thread from the "physical" thread is
indeed the point.
That seems like a strawman argument; maybe I'm misunderstanding Steve.
It seems to me that Steve is implying that using thread-local variables
somehow prevents that separation. It does not.
The point I'm making is that adding `tstate` parameters everywhere is
unnecessary. Using a thread local variable is much less intrusive and is
at least as capable.
Cheers,
Mark.
_______________________________________________
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at
https://mail.python.org/archives/list/python-dev@python.org/message/CLRCMGUC5LO3JOFGB2QG6DCJRTVVC3A4/
Code of Conduct: http://python.org/psf/codeofconduct/
