[issue26143] Ensure that IDLE's stdlib imports are from the stdlib

Terry J. Reedy added the comment: Looking at https://stackoverflow.com/questions/15888186/cant-run-python-via-idle-from-explorer-2013-idles-subprocess-didnt-make-c and https://stackoverflow.com/questions/874757/python-idle-subprocess-error it seems that people have put things like tkinter.py,

[issue557704] netrc module can't handle all passwords

Martin Dengler added the comment: Bram's patch for "special" characters is in, mine is the one that allows spaces in .netrc by enabling the parsing of a password field's value that's surrounded by lexer.quotes ( https://hg.python.org/cpython/file/2.7/Lib/shlex.py#l45 ). This is not the same

[issue557704] netrc module can't handle all passwords

Martin Dengler added the comment: Anecdotal ( http://stackoverflow.com/a/12675195/2747741 ) evidence suggests other programs do indeed accept spaces, and a cursory browsing of the Perl source code ( http://perl5.git.perl.org/perl.git/blob/HEAD:/cpan/libnet/lib/Net/Netrc.pm#l120 ) indicates

[issue557704] netrc module can't handle all passwords

Guido van Rossum added the comment: (Hi Bram! :-) So does your patch also accept escaped spaces? I wonder if one of the problems here may not be that the syntax required to escape special characters isn't specified? That might be acceptable in 2003, not so much in 2016. --

[issue26143] Ensure that IDLE's stdlib imports are from the stdlib

New submission from Terry J. Reedy: In the past few months, there has been an increase "IDLE fails to start" reports that are apparently due to shadowing of stdlib modules by user modules in the same directly as as user code. For instance, a beginner creates turtle.py and then writes "import

[issue25514] Improve IDLE's "subprocess didn't make connection" message

Terry J. Reedy added the comment: I have seen another report that is likely due to masking. I don't know why this has suddenly become seemingly much more common, but I have made fixing the problem a priority. See new issue #26143. I would like to narrow this issue to the user process, and

[issue26144] test_pkg test_4 and/or test_7 sometimes fail

New submission from Martin Panter: It doesn’t always fail, and sometimes only one or the other test fails. Also, it seems to depend on the way the tests are run. I have never seen it fail with “python -m test -v”. Two commands where it does often fail for me: ./python -m test -w test_pkg

[issue26129] Difference in behaviour with grp.getgrgid and pwd.getpwuid

Brett Cannon added the comment: A single deprecation cycle should be enough since it obviously shouldn't work with floats and strings might make sense but updating code to not use them is easy enough. -- ___ Python tracker

[issue19475] Add timespec optional flag to datetime isoformat() to choose the precision

Guido van Rossum added the comment: I think Alexander has commit rights, he did most of the review, I trust him to commit it. -- ___ Python tracker ___

[issue19475] Add timespec optional flag to datetime isoformat() to choose the precision

Alexander Belopolsky added the comment: I left some comments on Rietveld. -- stage: commit review -> needs patch ___ Python tracker ___

[issue19475] Add timespec optional flag to datetime isoformat() to choose the precision

Changes by Alexander Belopolsky : -- assignee: -> belopolsky stage: patch review -> commit review ___ Python tracker ___

[issue19475] Add timespec optional flag to datetime isoformat() to choose the precision

SilentGhost added the comment: Yes, version 12 is the final patch. It doesn't add those options. To copy my opinion from the rietveld (https://bugs.python.org/review/19475/#msg14): > I don't really think nanoseconds belong here. If they don't > exist anywhere else in the module, why should

[issue19475] Add timespec optional flag to datetime isoformat() to choose the precision

Alexander Belopolsky added the comment: > I don't really think nanoseconds belong here. What about milliseconds? I'll leave it for Guido to make a call on nanoseconds. My vote is +0.5. > If they don't > exist anywhere else in the module, why should they be suddenly > introduced here? The

[issue26106] Move licences to literal blocks

Julien added the comment: And uploaded the result: http://www.afpy.org/doc/python/3.5/license.html -- ___ Python tracker ___

[issue19475] Add timespec optional flag to datetime isoformat() to choose the precision

Alexander Belopolsky added the comment: Is issue19475_v12.patch the final patch? I don't see it addressing Guido's suggestion in msg256470 to add milli- and nanoseconds options. -- ___ Python tracker

[issue26142] Formatting bug on https://docs.python.org/2.7/c-api/intro.html

Roundup Robot added the comment: New changeset 4f1ed606410b by Senthil Kumaran in branch '2.7': Issue26142 - Fix a formatting bug in c-api intro doc. https://hg.python.org/cpython/rev/4f1ed606410b -- nosy: +python-dev ___ Python tracker

[issue26142] Formatting bug on https://docs.python.org/2.7/c-api/intro.html

Senthil Kumaran added the comment: Thanks for reporting. Fixed. -- nosy: +orsenthil resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker

[issue26017] Update https://docs.python.org/3/installing/index.html to always quote arguments

Roundup Robot added the comment: New changeset 31debd0dc0dc by Senthil Kumaran in branch '3.5': Issue26017 - Suggest enclosing command args in double quotes when using characters which get interpreted by shell. https://hg.python.org/cpython/rev/31debd0dc0dc New changeset 18ae23b69e08 by

[issue26017] Update https://docs.python.org/3/installing/index.html to always quote arguments

Roundup Robot added the comment: New changeset 668827be66d6 by Senthil Kumaran in branch '2.7': Issue26017 - Suggest enclosing command args in double quotes when using characters which get interpreted by shell. https://hg.python.org/cpython/rev/668827be66d6 --

[issue26017] Update https://docs.python.org/3/installing/index.html to always quote arguments

Senthil Kumaran added the comment: Thanks for the review/comment Ezio. Agree with your suggestion and made the change accordingly. -- assignee: docs@python -> orsenthil resolution: -> fixed stage: needs patch -> resolved status: open -> closed versions: +Python 2.7, Python 3.5, Python

[issue19475] Add timespec optional flag to datetime isoformat() to choose the precision

Guido van Rossum added the comment: You can leave out the nanoseconds but please do add the milliseconds. I'm sure they would find more use than the option to show only the hours. -- ___ Python tracker

[issue26140] inspect.iscoroutinefunction raises TypeError when checks Mock of function or coroutinefunction

Guido van Rossum added the comment: Why fix this in mock rather than in the iscoroutinefunction functions? (Not a rhetorical question -- I really am not sure what the better place is to fix this, or if we should even consider fixing it.) -- ___

[issue26134] HTTPPasswordMgrWithPriorAuth does not work with DigestAuthentication

Martin Panter added the comment: Perhaps this is similar to Issue 7752, about reusing the nonce. -- ___ Python tracker ___

[issue25878] CPython on Windows builds with /W3, not /W4

Alexander Riccio added the comment: If there are few enough instances, then using a #pragma warning(suppress:4232) is probably the best idea. -- ___ Python tracker

[issue26137] [idea] use the Microsoft Antimalware Scan Interface

New submission from Alexander Riccio: I'm really not sure what it'd look like, or how it'd work, but CPython should take advantage of Microsoft's Antimalware Scan Interface, which is new to Windows 10. It's designed for applications like interpreters, which can execute u trusted code that may

[issue26137] [idea] use the Microsoft Antimalware Scan Interface

Alexander Riccio added the comment: See also: "Security Focus: Defending PowerShell with the Anti-Malware Scan Interface (AMSI)" http://blogs.technet.com/b/poshchap/archive/2015/10/16/security-focus-defending-powershell-with-windows-defender.aspx --

[issue26137] [idea] use the Microsoft Antimalware Scan Interface

Alexander Riccio added the comment: When I say "I'm really not sure what it'd look like, or how it'd work" I mean at the C level. At a higher level, there are many places that I imagine are good places to use AMSI: Perhaps expressions passed in from the command line (-c) should be scanned;

[issue26137] [idea] use the Microsoft Antimalware Scan Interface

Alexander Riccio added the comment: See "Windows 10 to offer application developers new malware defenses" https://blogs.technet.microsoft.com/mmpc/2015/06/09/windows-10-to-offer-application-developers-new-malware-defenses/ for an example of how AMSI works with PowerShell. I think the

[issue25954] Python 3.5.1 installer fails on Windows 7

Ned Batchelder added the comment: Steve, I do have that update installed. -- ___ Python tracker ___ ___

[issue24780] unittest assertEqual difference output foiled by newlines

Elena Oat added the comment: The issue is not related only to the caret. In fact, as seen in the below output, the issue occurs anytime there's a newline character in the beginning or middle of the string to be compared. In short, if a newline is present in the string and it's in the

[issue26039] More flexibility in zipfile interface

Thomas Kluyver added the comment: zipinfo-from-file.patch has an orthogonal but related change: the code in ZipFile.write() to construct a ZipInfo object from a filesystem file is pulled out to a classmethod ZipInfo.from_file(). Together, these changes make it much easier to control how a

[issue25878] CPython on Windows builds with /W3, not /W4

Stefan Krah added the comment: I would expect linking to behave "as if" the abstract machine defined by the standard were executing the code. We already had one function pointer equality issue due to COMDAT folding, so I agree that we should leave the warning on. --

[issue26138] Disable /W4 warning (non-standard dllimport behavior)

Changes by Stefan Krah : -- nosy: skrah priority: normal severity: normal status: open title: Disable /W4 warning (non-standard dllimport behavior) ___ Python tracker

[issue26139] libmpdec: disable /W4 warning (non-standard dllimport behavior)

New submission from Stefan Krah: See: #25878 -- assignee: skrah components: Extension Modules messages: 258461 nosy: skrah priority: normal severity: normal status: open title: libmpdec: disable /W4 warning (non-standard dllimport behavior) type: compile error versions: Python 3.6

[issue26139] libmpdec: disable /W4 warning (non-standard dllimport behavior)

Roundup Robot added the comment: New changeset df78978dacab by Stefan Krah in branch 'default': Issue #26139: libmpdec: disable /W4 warning (non-standard dllimport behavior). https://hg.python.org/cpython/rev/df78978dacab -- nosy: +python-dev ___

[issue26138] Disable /W4 warning (non-standard dllimport behavior)

Changes by Stefan Krah : -- resolution: -> duplicate stage: -> resolved status: open -> closed type: -> compile error ___ Python tracker

[issue26139] libmpdec: disable /W4 warning (non-standard dllimport behavior)

Changes by Stefan Krah : -- resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker ___

[issue25878] CPython on Windows builds with /W3, not /W4

Stefan Krah added the comment: Pragma added for libmpdec in #26139. -- ___ Python tracker ___ ___

[issue26140] inspect.iscoroutinefunction raises TypeError when checks Mock of function or coroutinefunction

New submission from Hiroyuki Takagi: inspect.iscoroutinefunction and asyncio.iscoroutinefunction with patch of issue25599 (https://bugs.python.org/issue25599) raise TypeError when used to check Mock object which mocks function or coroutinefunction. How to reproduce: - For the mock of

[issue26129] Difference in behaviour with grp.getgrgid and pwd.getpwuid

Larry Hastings added the comment: Nope. Argument Clinic was merged in 3.4, and in 3.3 pwd.getpwuid wouldn't accept strings. So this isn't a bug introduced in the Clinic conversion in 3.4, this is historical behavior, and we can't change it now. If anything, I'd prefer that grp.getgrid

[issue25724] SSLv3 test failure on Ubuntu 16.04 LTS

Changes by SilentGhost : -- nosy: +alex, christian.heimes, dstufft, giampaolo.rodola, janssen, pitrou stage: -> patch review versions: +Python 3.6 ___ Python tracker

[issue25724] SSLv3 test failure on Ubuntu 16.04 LTS

Antoine Pitrou added the comment: >From a procedural point of view, I think it would be reasonable to wait for >the 16.04 release (or at least feature freeze), in case there are other >breakages pending. -- versions: +Python 2.7 ___ Python tracker

[issue25954] Python 3.5.1 installer fails on Windows 7

Steve Dower added the comment: Is your installation working okay then? You seemed to imply that in an earlier message, but I just want to confirm before closing the issue. -- ___ Python tracker

[issue26129] Difference in behaviour with grp.getgrgid and pwd.getpwuid

Serhiy Storchaka added the comment: This looks as unintentional consequences of ab0221811771. I think the current behavior of grp.getgrgid() is not correct, because it accepts str, float and other types. Python is strong-typed language and shouldn't make unwanted implicit type conversions. I

[issue26137] [idea] use the Microsoft Antimalware Scan Interface

Steve Dower added the comment: I actually have a prototype of this already, though I haven't benchmarked the impact yet. Brett and I were concerned that the applicability wasn't apparent enough given the cost involved, so we've been (slowly) preparing a PEP, mainly to have that record of why

[issue19475] Add timespec optional flag to datetime isoformat() to choose the precision

SilentGhost added the comment: > I there anything else I can do for this? I think you've done all you could, it's just someone needs to commit it. I don't think they're being rude on purpose - it's just that there are so many committers in the nosy list that no one is feeling like it's their

[issue26106] Move licences to literal blocks

Julien added the comment: @georg.brandl is right, a parsed-literal block should work: Does not appear in pot files, and |release| replaced: nice. I attached a new patch. -- Added file: http://bugs.python.org/file41641/literal-licence.patch ___

[issue26141] typing module documentation incomplete

New submission from Ben Darnell: The typing module docs at https://docs.python.org/3/library/typing.html do not include everything that is documented in the PEP (https://www.python.org/dev/peps/pep-0484/#the-typing-module). Specifically, `AnyStr` is mentioned but not defined, the `@overload`