[issue22178] _winreg.QueryInfoKey Last Modified Time Value Incorrect or Explanation Incorrect

New submission from sw: The explanation of the 3rd index of the tuple returned from _winreg.QueryInfoKey(key) explains that it is a long representing 100s of nanoseconds since 1/1/1600. However, when I use this value and convert to the actual date using startDate = datetime(1600,1,1) lastModi

[issue22174] property doc fixes

diana added the comment: This whitespace? Or did you mean something else? class C: def __init__(self): self._x = None def getx(self): return self._x def setx(self, value): self._x = value def delx(self):

[issue22174] property doc fixes

Raymond Hettinger added the comment: Also, please don't add the extra whitespace to the docstring. It is intentionally compact because of the differing needs of various IDEs and help utlities. -- assignee: docs@python -> rhettinger nosy: +rhettinger __

[issue21121] -Werror=declaration-after-statement is added even for extension modules through setup.py

Roundup Robot added the comment: New changeset 2a3538f14948 by Benjamin Peterson in branch '3.4': add -Werror=declaration-after-statement only to stdlib extension modules (closes #21121) http://hg.python.org/cpython/rev/2a3538f14948 New changeset a5368cfbea0e by Benjamin Peterson in branch 'def

[issue21591] "exec(a, b, c)" not the same as "exec a in b, c" in nested functions

Roundup Robot added the comment: New changeset 0e9b023078e6 by Benjamin Peterson in branch '2.7': restore runtime exec test (#21591) http://hg.python.org/cpython/rev/0e9b023078e6 -- ___ Python tracker _

[issue21965] Add support for Memory BIO to _ssl

Changes by Glyph Lefkowitz : -- nosy: -glyph ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyth

[issue21591] "exec(a, b, c)" not the same as "exec a in b, c" in nested functions

Nick Coghlan added the comment: Agreed reverting isn't necessary - main thing is to figure out what went wrong in the py test suite and come up with a new test case that covers it. The reason I suspect it's the missing runtime check that's causing the py problem is because (as far as I am awar

[issue16893] Create IDLE help.txt from Doc/library/idle.rst

Changes by Mark Lawrence : -- versions: +Python 3.5 -Python 3.3 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue22177] Incorrect version reported after downgrade

jp added the comment: Have you checked if there are pyc files left around by the previous installation? -- Yes, hundreds! After making a backup, i deleted all 900+ occurrences of "*.pyc" in c:\python27 and it still reports 2.7.8. Have you specified the full path to python.exe from cmd while ru

[issue6858] This is a python file, apply syntax highlighting

Changes by Mark Lawrence : -- versions: +Python 2.7, Python 3.4, Python 3.5 -Python 3.2, Python 3.3 ___ Python tracker ___ ___ Python-b

[issue14944] Setup & Usage documentation for pydoc, idle & 2to3

Mark Lawrence added the comment: I'm assuming that this still applies to 3.4 and 2.7. -- nosy: +BreamoreBoy versions: +Python 3.5 -Python 3.3 ___ Python tracker ___ _

[issue22177] Incorrect version reported after downgrade

Ezio Melotti added the comment: Have you checked if there are pyc files left around by the previous installation? Have you specified the full path to python.exe from cmd while running python -V? If you start the interpreter and print sys.version what do you get? Does anything change if you rel

[issue22177] Incorrect version reported after downgrade

jp added the comment: Forget to mention this downgrade was installed over the existing python installation. -- ___ Python tracker ___ ___

[issue22176] update internal libffi copy to 3.1, introducing AArch64 and POWER ELF ABIv2

Roundup Robot added the comment: New changeset 4d3f960c26f5 by doko in branch '3.4': - Issue #22176: Fix build failure on ARM with -Werror=declaration-after-statement http://hg.python.org/cpython/rev/4d3f960c26f5 -- ___ Python tracker

[issue22177] Incorrect version reported after downgrade

New submission from jp: After downgrading from version 2.7.8 to 2.7.5 on Win7 x86 32bit Python, the interpreter continues to report version 2.7.8. I have verified that the installation folder has the correct files belonging to 2.7.5 as evidenced by python.exe having a 2013 timestamp. Ran pyt

[issue22176] update internal libffi copy to 3.1, introducing AArch64 and POWER ELF ABIv2

Roundup Robot added the comment: New changeset 269ec4c568bd by doko in branch '3.4': - Issue #22176: Add src/x86/win32.S for x86 libffi builds. http://hg.python.org/cpython/rev/269ec4c568bd -- ___ Python tracker __

[issue22176] update internal libffi copy to 3.1, introducing AArch64 and POWER ELF ABIv2

Roundup Robot added the comment: New changeset f73c8cf6261f by doko in branch '3.4': - Issue #22176: Update the ctypes module's libffi to v3.1. This release http://hg.python.org/cpython/rev/f73c8cf6261f New changeset 0fef0afb9d19 by doko in branch 'default': - Issue #22176: Update the ctypes mo

[issue21725] RFC 6531 (SMTPUTF8) support in smtpd

R. David Murray added the comment: OK, it's a bug in mock_socket, then. getpeername should be returning a tuple (address, port). I went ahead and fixed it, and committed the patch. Thanks Milan! Sorry the reviews were so delayed. -- resolution: -> fixed stage: patch review -> resol

[issue14105] Breakpoints in debug lost if line is inserted; IDLE

Terry J. Reedy added the comment: Forgot to mention: after inserting \n, the breakpoint tag can be cleared from either line independently. Tagging complete lines makes this easy. If a line is split into three and the middle line untagged, then the first and third are left separately tagged. -

[issue22176] update internal libffi copy to 3.1, introducing AArch64 and POWER ELF ABIv2

New submission from Matthias Klose: tracking the import of libffi 3.1 -- components: ctypes messages: 225109 nosy: doko priority: normal severity: normal status: open title: update internal libffi copy to 3.1, introducing AArch64 and POWER ELF ABIv2 versions: Python 3.4, Python 3.5 ___

[issue14105] Breakpoints in debug lost if line is inserted; IDLE

Terry J. Reedy added the comment: On 8/9/2014 10:13 AM, Saimadhav Heblikar wrote: > > Saimadhav Heblikar added the comment: > > Not sure if this consequence of the commit is intended behavior, It is. > In any file, set a breakpoint on any line. Pressing key > anywhere after the first character

[issue21591] "exec(a, b, c)" not the same as "exec a in b, c" in nested functions

Dirkjan Ochtman added the comment: I can take a look at the py failure next week. Keeping the run-time compatibility code seems sensible, but I'm not sure if it'd fix the py test? I don't think reverting the changes at this point is warranted. -- _

[issue21725] RFC 6531 (SMTPUTF8) support in smtpd

Milan Oberkirch added the comment: I think that the peer arg is supposed to be set to the address of the peer connecting to our server. The value 'peer' comes from test/mock_socket.py:105 and is the best answer we can get for mock_sock.getpeername() because there is no real client when directl

[issue21725] RFC 6531 (SMTPUTF8) support in smtpd

R. David Murray added the comment: I tweaked your additions. Instead of trying to strip out the 'b' to make things "look pretty", I think it is better to print them and thus make it explicit when we are dealing with binary data and when we are dealing with strings. It also clues the user in

[issue14105] Breakpoints in debug lost if line is inserted; IDLE

Saimadhav Heblikar added the comment: Not sure if this consequence of the commit is intended behavior, but still placing it here. In any file, set a breakpoint on any line. Pressing key anywhere after the first character, will create a new breakpoint in the next line. These lines will also

[issue21965] Add support for Memory BIO to _ssl

Geert Jansen added the comment: Thanks to Ben and Glyph for their feedback. The memory BIO should allow ProactorEventLoop to support SSL. I say "should" because I have not looked at it myself. However, my Gruvi project is proactor (libuv) based and I have a private branch where SSL support is

[issue22147] PosixPath() constructor should not accept strings with embedded NUL bytes

Vajrasky Kok added the comment: Here is the patch. -- keywords: +patch nosy: +vajrasky Added file: http://bugs.python.org/file36327/embedded_null_in_path.patch ___ Python tracker ___

[issue10803] ctypes: better support of bytearray objects

Serhiy Storchaka added the comment: Existing inconsistency was fixed in issue22161. Patch updated, synchronized with tip. Added new tests. -- Added file: http://bugs.python.org/file36326/ctypes_bytearray_2.patch ___ Python tracker