[issue31513] Document structure of memo dictionary to enable more advanced __deepcopy__ uses

R. David Murray added the comment: Unless I'm mistaken (and someone will correct me and reopen the issue if I am :) it is intentionally undocumented. A proposal for a documented protocol of some sort is certainly a possibility, but is something that should start with a discussion on the pytho

[issue21622] ctypes.util incorrectly fails for libraries without DT_SONAME

Changes by Richard Eames : -- nosy: +Richard Eames ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mai

[issue31485] Tkinter widget.unbind(sequence, funcid) unbind all bindings

Juliette Monsel added the comment: I don't mind writing a patch and opening a pull request, however I don't know which corner cases I need to take into account. -- ___ Python tracker _

[issue24243] behavior for finding an empty string is inconsistent with documentation

Vedran Čačić added the comment: Raymond, with respect, I think you're either wrong here, or misleading with a purpose. There is a big difference between any(()) returning False, all(()) returning True, '' in '' returning True, math.factorial(0) returning 1, and set() <= set() returning True,

[issue24243] behavior for finding an empty string is inconsistent with documentation

Antoine Pitrou added the comment: I'm not sure why we're arguing over this. Is this actually something that matters in the real world? -- ___ Python tracker ___ __

[issue31370] Remove support for threads-less builds

Steve Gomez added the comment: Oracle Binary Code License Agreement for the Java SE Platform Products and JavaFX ORACLE AMERICA, INC. ("ORACLE"), FOR AND ON BEHALF OF ITSELF AND ITS SUBSIDIARIES AND AFFILIATES UNDER COMMON CONTROL, IS WILLING TO LICENSE THE SOFTWARE TO YOU ONLY UPON THE CONDI

[issue24243] behavior for finding an empty string is inconsistent with documentation

R. David Murray added the comment: I'm not Raymond, but he is correct. This is an example of "taking advantage of the corner cases", and is something Python does a lot of, especially around strings and slices. The current behavior was carefully considered and has useful properties.

[issue31370] Remove support for threads-less builds

Antoine Pitrou added the comment: New changeset 88c60c9668f0aa732693517a60b851cc1dfce0cb by Antoine Pitrou in branch 'master': Trivial cleanups following bpo-31370 (#3649) https://github.com/python/cpython/commit/88c60c9668f0aa732693517a60b851cc1dfce0cb -- ___

[issue31447] proc communicate not exiting on python subprocess timeout using PIPES

Eryk Sun added the comment: > when I said "also with close_fds=True", I meant that I tried > WITHOUT overriding stdin, stdout, and stderr AND setting > close_fds=True, but it didn't work. Console applications (e.g. python.exe) duplicate their standard handles into a child console process whe

[issue31512] Add non-elevated symlink support for dev mode Windows 10

Eryk Sun added the comment: Py_CreateSymbolicLinkW can be removed in 3.5+ because Windows XP is no longer supported and calling enable_symlink() is pointless. The Windows API uses some privileges simply to determine which security principals can access a capability. Whether the privilege is c

[issue13224] Change str(x) to return only the qualname for some types

Éric Araujo added the comment: Martin Panter > I’m a bit confused. In the current patch, the new type_str() function > appears to use the “qualname” (which I support), but some of the test > changes seem to contradict this, e.g.: > >>> C.foo(1) > -classmethod 1 > +classmethod C 1 C is a qual

[issue13224] Change str(x) to return only the qualname for some types

Éric Araujo added the comment: (Nick and Guido! «My proposal is to make str(x) return x.__name__ for exactly these three types of objects: modules, classes, and functions.») -- ___ Python tracker

[issue31514] There is a problem with the setdefault type conversion in the tuple

New submission from sk xing: The setdefault method of the tuple allows the introduction of custom data types.At this point, the __repr__ method is implemented so that the returned data type has an error.The type of str is returned, but the int type is written to the tuple.Also, write str witho

[issue23666] Add shell session logging option to IDLE

Grant Jenks added the comment: +1 from me. I'd like to see it ask me to save when I close the window if I've already saved once. -- nosy: +grantjenks ___ Python tracker ___ ___

[issue13224] Change str(x) to return only the qualname for some types

Guido van Rossum added the comment: For modules, __name__ is the fully-qualified name, and that's fine. But for classes and functions __name__ is just the "given name" from the syntax (whatever came after 'def' or 'class') and that's not fine -- for anything except builtins where we do this I

[issue31498] Default values for zero in time.strftime()

Denis Osipov added the comment: It seems strange to me that time.strftime() returns formatted date with wrong day of week and day of year values. So, I think it's probably a bug. But I'm just learning Python and programming and I think that it can be intentional behavior. If it's a bug I'd like

[issue21937] IDLE interactive window doesn't display unsaved-indicator

Terry J. Reedy added the comment: The 'follow-on' issue is #23666. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubs

[issue13224] Change str(x) to return only the qualname for some types

Nick Coghlan added the comment: Specifically this message, where the unwritten rationale is to offer behavioural consistency across the builtin types that know their own name and include it in their current repr() output: https://mail.python.org/pipermail/python-ideas/2011-October/012464.html

[issue31506] Improve the error message logic for object_new & object_init

Nick Coghlan added the comment: Those would both report "C() takes no parameters" without further enhancements (which would be out of scope for this issue). The proposed improvement here isn't "Let's make the error message exactly correct in all cases" (that's probably impossible, since we've

[issue31514] There is a problem with the setdefault type conversion in the tuple

Steven D'Aprano added the comment: The demo code you give seems to be working perfectly correctly. I don't think anything here is a bug. (1) You are working with a dict, not a tuple. (2) The potint.__repr__ method does NOT have a bug. (3) de['four'] is NOT an int, it is a potint object, just

[issue30744] Local variable assignment is broken when combined with threads + tracing + closures

Nick Coghlan added the comment: For write-backs: no, since the interpreter will still write those values back into the destination cell For locals display: no, since nothing changes for the handling of fast locals For closure display: yes as, by default, debuggers will now print the closure c

<    1   2