[Python-Dev] Summary of Python tracker Issues
ACTIVITY SUMMARY (2018-01-05 - 2018-01-12) Python tracker at https://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: open6369 ( -8) closed 37921 (+50) total 44290 (+42) Open issues with patches: 2470 Issues opened (38) == #20104: expose posix_spawn(p) https://bugs.python.org/issue20104 reopened by gregory.p.smith #23749: asyncio missing wrap_socket (starttls) https://bugs.python.org/issue23749 reopened by vstinner #29137: Fix fpectl-induced ABI breakage https://bugs.python.org/issue29137 reopened by doko #31804: multiprocessing calls flush on sys.stdout at exit even if it i https://bugs.python.org/issue31804 reopened by Pox TheGreat #31993: pickle.dump allocates unnecessary temporary bytes / str https://bugs.python.org/issue31993 reopened by serhiy.storchaka #32206: Run modules with pdb https://bugs.python.org/issue32206 reopened by ncoghlan #32498: urllib.parse.unquote raises incorrect errormessage when string https://bugs.python.org/issue32498 opened by stein-k #32500: PySequence_Length() raises TypeError on dict type https://bugs.python.org/issue32500 opened by mgorny #32501: Documentation for dir([object]) https://bugs.python.org/issue32501 opened by Vladislavs Burakovs #32502: uuid1() broken on macos high sierra https://bugs.python.org/issue32502 opened by anpetral #32503: Avoid creating small frames in pickle protocol 4 https://bugs.python.org/issue32503 opened by serhiy.storchaka #32505: dataclasses: make field() with no annotation an error https://bugs.python.org/issue32505 opened by eric.smith #32506: dataclasses: no need for OrderedDict now that dict guarantees https://bugs.python.org/issue32506 opened by eric.smith #32509: doctest syntax ambiguity between continuation line and ellipsi https://bugs.python.org/issue32509 opened by jason.coombs #32511: Thread primitives do not report the OS-level error on failure https://bugs.python.org/issue32511 opened by zwol #32512: Add an option to profile to run library module as a script https://bugs.python.org/issue32512 opened by mariocj89 #32513: dataclasses: make it easier to use user-supplied special metho https://bugs.python.org/issue32513 opened by eric.smith #32514: 0x80070002 - The system cannot find the file specified https://bugs.python.org/issue32514 opened by Beatty0111 #32515: Add an option to trace to run module as a script https://bugs.python.org/issue32515 opened by mariocj89 #32516: Add a shared library mechanism for win32 https://bugs.python.org/issue32516 opened by xoviat #32517: test_read_pty_output() of test_asyncio hangs on macOS 10.13.2 https://bugs.python.org/issue32517 opened by vstinner #32519: venv API docs - symlinks default incorrect https://bugs.python.org/issue32519 opened by jason.coombs #32521: NIS module fails to build due to the removal of interfaces rel https://bugs.python.org/issue32521 opened by cstratak #32522: Add precision argument to datetime.now https://bugs.python.org/issue32522 opened by p-ganssle #32523: inconsistent spacing in changelog.html https://bugs.python.org/issue32523 opened by ned.deily #32524: Python 2.7 leaks a packages __init__.py module object on Synta https://bugs.python.org/issue32524 opened by Segev Finer #32526: Closing async generator while it is running does not raise an https://bugs.python.org/issue32526 opened by achimnol #32528: Change base class for futures.CancelledError https://bugs.python.org/issue32528 opened by socketpair #32529: Call readinto in shutil.copyfileobj https://bugs.python.org/issue32529 opened by YoSTEALTH #32530: How ro fix the chm encoding in Non western european codepage(c https://bugs.python.org/issue32530 opened by Nim #32531: gdb.execute can not put string value. https://bugs.python.org/issue32531 opened by callmekohei #32532: improve sys.settrace and sys.setprofile documentation https://bugs.python.org/issue32532 opened by xiang.zhang #32533: SSLSocket read/write thread-unsafety https://bugs.python.org/issue32533 opened by Alexey Baldin #32534: Speed-up list.insert https://bugs.python.org/issue32534 opened by jeethu #32536: ast and tokenize disagree about line number https://bugs.python.org/issue32536 opened by Mark.Shannon #32537: multiprocessing.pool.Pool.starmap_async - wrong parameter name https://bugs.python.org/issue32537 opened by devnull #32538: Multiprocessing Manager on 3D list - no change of the list pos https://bugs.python.org/issue32538 opened by John_81 #32539: os.listdir(...) on deep path on windows in python2.7 fails wit https://bugs.python.org/issue32539 opened by Anthony Sottile Most recent 15 issues with no replies (15) == #32539: os.listdir(...) on deep path on windows in python2.7 fails wit https://bugs.python.org/issue32539 #32538: Multiprocessing Manager on 3D list - no change of the lis
Re: [Python-Dev] PEP 567 pre v3
I think we've debated the design of ContextVar and default values enough. Regardless of the philosophical questions around "what is a variable", I agree that Yury's current design is right, so let's move on to other topics (if there are any). On Thu, Jan 11, 2018 at 12:55 AM, Paul Moore wrote: > On 11 January 2018 at 07:39, Chris Jerdonek > wrote: > > But to your question, like it or not, I think the API encourages this > > way of thinking because the get() method is on the ContextVar itself, > > and so it's the ContextVar which is doing the looking up rather than > > just fulfilling the role of a key name. The API brings to mind other > > containers and things holding values like dict.get(), queue.get(), > > BytesIO.getvalue(), and container type's object.__getitem__(), etc. So > > I think one will need to be prepared for many or most users having > > this conception with the current API. (I think renaming to something > > like ContextVar.lookup() or even ContextVar.value() would go a long > > way towards dispelling that, but Guido said earlier in the thread that > > he likes the shorter name.) > > I can only offer anecdotal evidence, but I am perfectly comfortable > with seeing ContextVars as names (variables) that refer to values, and > not as containers of values. The "Var" part of the class name is what > makes that link in my head, I think, and it is a stronger association > for me than the idea that get() implies a container. > > So I'm 100% fine, personally, with ContextVars as names that refer to > values (that you access via the get() method), and with the Context as > a hidden lookup table for those values (corresponding to > globals()/locals()). I'm also OK on that same basis with ContextVars > having an "unset" state, and with it being unusual/difficult to get > back to the unset state once you've set a value. > > tl;dr If you think of a ContextVar as a "variable" or "name", the > current design makes sense (at least to me). > > Paul > ___ > 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/ > guido%40python.org > -- --Guido van Rossum (python.org/~guido) ___ 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
