[issue19944] Make importlib.find_spec load packages as needed

Nick Coghlan added the comment: Actually, why *is* find_spec at package level, rather than in util with resolve_name? I know we said it was at package level in the PEP, but we never really gave the question serious thought. Also, why use builtins.__import__ rather than using __import__ directl

[issue19944] Make importlib.find_spec load packages as needed

Eric Snow added the comment: Good points, Nick. I was trying to limit touches on _bootstrap.py for 3.4, but that "simple" patch is mostly just a hacky band-aid. Here's a patch that hopefully stands on its own and still limits touches. (The patch is the bare-bones changes only.) There are 2

[issue19977] Use "surrogateescape" error handler for sys.stdin and sys.stdout on UNIX for the C locale

Nick Coghlan added the comment: Larry: I'm assuming it's way too late to make a change like this for the 3.4 release? Slavek: assuming this change is made for 3.5 upstream, we may want to look at backporting it as a 3.4 patch in Fedora (as part of the Python-3-by-default project). Otherwise i

[issue19714] Add tests for importlib.machinery.WindowsRegistryFinder

Eric Snow added the comment: I added 2 rudimentary tests for issue #20097 which gives at least coverage in the test suite, but we need the following tests still: * registry entry exists and module is found (spec returned) * registry entry exists and module is not found (None returned) Dependin

[issue20097] Bad use of `self` in importlib

Eric Snow added the comment: Thanks for the review, Victor. As to that note, it is the subject of issue #19714. -- assignee: brett.cannon -> eric.snow dependencies: -Add tests for importlib.machinery.WindowsRegistryFinder resolution: -> fixed stage: patch review -> committed/rejected

[issue20097] Bad use of `self` in importlib

Roundup Robot added the comment: New changeset 7dbb4c6cd30e by Eric Snow in branch 'default': Issue #20097: Fix bad use of "self" in importlib's WindowsRegistryFinder. http://hg.python.org/cpython/rev/7dbb4c6cd30e -- nosy: +python-dev ___ Python track

[issue19347] PEP 453 implementation tracking issue

Nick Coghlan added the comment: Actually, with the docs update being the only remaining "this really should be done before 3.4 is released" issue related to PEP 453, I think this tracking issue has now served its purpose. So, closing this umbrella issue now, since issue 19407 covers the docs u

[issue19407] PEP 453: update the "Installing Python Modules" documentation

Changes by Nick Coghlan : -- priority: release blocker -> deferred blocker ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue18585] Add a text truncation function

Daniel Holth added the comment: Previous changeset was meant for #18515 -- nosy: +dholth ___ Python tracker ___ ___ Python-bugs-list m

[issue18585] Add a text truncation function

Roundup Robot added the comment: New changeset 536a2cf5f1d2 by Daniel Holth in branch 'default': Issue #18585: speed zipfile import by only generating zipfile._ZipDecryptor on demand http://hg.python.org/cpython/rev/536a2cf5f1d2 -- ___ Python tracker

[issue19347] PEP 453 implementation tracking issue

Changes by Martin v. Löwis : -- priority: release blocker -> normal ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue1346238] A constant folding optimization pass for the AST

STINNER Victor added the comment: My astoptimizer project has an experimental support of constant folding. It works in the same file, or constants can be propagated to other files using config.add_constant('NAME', value). https://bitbucket.org/haypo/astoptimizer/ -- nosy: +haypo

[issue19407] PEP 453: update the "Installing Python Modules" documentation

Nick Coghlan added the comment: Agreed, this was set to ensure Larry followed up with a "Please explain" if I didn't get it done in a timely manner. I'll still try to get it done for the beta, but I still have linux.conf.aupreparation to do, so it may slip to the first RC. -- _

[issue19347] PEP 453 implementation tracking issue

Nick Coghlan added the comment: Agreed, it was mostly to ensure we reviewed the status to make sure we were happy with progress. The only remaining "must fix" item is the docs update, and that's shouldn't block beta 2 (although I'll still try to get at least an initial version done now that pip 1

[issue20097] Bad use of `self` in importlib

STINNER Victor added the comment: Would it be possible to put @unittest.skipUnless(...) on WindowsRegistryFinderTests instead of duplicating it? Except of this nit, the patch looks good to me. Note: WindowsRegistryFinder.find_spec() contains the comment: # XXX untested! Need a Windows pers

[issue20111] pathlib.PurePath.with_suffix() allows creation of otherwise impossible paths

Antoine Pitrou added the comment: I've committed a fix: ValueError is now raised for invalid suffixes. -- resolution: -> fixed stage: -> committed/rejected status: open -> closed versions: -Python 3.5 ___ Python tracker

[issue20111] pathlib.PurePath.with_suffix() allows creation of otherwise impossible paths

Roundup Robot added the comment: New changeset ef2b2ddd27c8 by Antoine Pitrou in branch 'default': Issue #20111: pathlib.Path.with_suffix() now sanity checks the given suffix. http://hg.python.org/cpython/rev/ef2b2ddd27c8 -- nosy: +python-dev ___ Pyth

[issue20111] pathlib.PurePath.with_suffix() allows creation of otherwise impossible paths

Antoine Pitrou added the comment: Thank you for reporting this! You're right, this is a bug. -- ___ Python tracker ___ ___ Python-bugs

[issue20110] Misleading word used for __annotations__

Roundup Robot added the comment: New changeset 203ca77ea819 by Benjamin Peterson in branch '3.3': correct word for __annotations__ doc (closes #20110) http://hg.python.org/cpython/rev/203ca77ea819 New changeset 3e75f649e93b by Benjamin Peterson in branch 'default': merge 3.3 (#20110) http://hg.p

[issue20112] The documentation for http.server error_message_format is inadequate.

New submission from R. David Murray: The description of error_message_format does not give enough information to use it. The description should talk about how it is used (ie: using % formatting) and the fact that when filled in it should form a complete html document because it will be sent a

[issue20101] Determine correct behavior for time functions on Windows

Zachary Ware added the comment: I ran the same test on all of the Windows buildbots, with the following results: x86 XP-4: http://buildbot.python.org/all/builders/x86%20XP-4%20custom/builds/33/steps/test/logs/stdio monotonic: good time: good clock/perf_counter: 10 failures x86 Windows7 http://b

[issue16113] SHA-3 (Keccak) support may need to be removed before 3.4

Martin v. Löwis added the comment: I just looked at the hash-forum archives (*) http://cio.nist.gov/esd/emaildir/lists/hash-forum/msg02809.html which says that they plan to publish the draft "soon after Christmas". They also indicate how the padding open issue might get resolved (append f

[issue16113] SHA-3 (Keccak) support may need to be removed before 3.4

Gregory P. Smith added the comment: Given the likely delay in the standard Martin cites, I've change my mind: agreed. Go ahead and remove it for 3.4. We'll have an official sha3 in Python 3.5. Early adopters can live with PyPI. -- ___ Python track

[issue16113] SHA-3 (Keccak) support may need to be removed before 3.4

STINNER Victor added the comment: OpenSSL doesn't implement SHA-3 yet, it's strange to have SHA-3 in Python but not in OpenSSL. If the standard is still a draft, I agree to remove the code right now. -- ___ Python tracker

[issue17997] ssl.match_hostname(): sub string wildcard should not match IDNA prefix

Changes by Martin v. Löwis : -- priority: normal -> release blocker ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue16113] SHA-3 (Keccak) support may need to be removed before 3.4

Antoine Pitrou added the comment: I agree with Martin that it should be removed right now. It's not really reasonable to call something SHA-3 if it's not SHA-3, even in beta versions. -- ___ Python tracker ___

[issue16113] SHA-3 (Keccak) support may need to be removed before 3.4

Martin v. Löwis added the comment: Ok, this this remains a release blocker. I'm still +1 for removing it, and I'm -0 for removing it just before the release candidate. AFAICT, there is *zero* (.1) chance that it actually becomes a NIST standard before the Python release is made. Accord

[issue20111] pathlib.PurePath.with_suffix() allows creation of otherwise impossible paths

Changes by R. David Murray : -- nosy: +r.david.murray ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://m

[issue16113] SHA-3 (Keccak) support may need to be removed before 3.4

Christian Heimes added the comment: I have created a backport of the sha3 for Python 2.6 to 3.3 about an year ago. It's on PyPI: https://pypi.python.org/pypi/pysha3 . I'm planing to update the code with SHAKE256 and SHAKE512 support soonish, too. I have very high confidence that NIST is neithe

[issue20111] pathlib.PurePath.with_suffix() allows creation of otherwise impossible paths

Changes by July Tikhonov : -- type: -> behavior ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue20101] Determine correct behavior for time functions on Windows

Tim Peters added the comment: 1. I'm sync'ing with north-america.pool.ntp.org. But the docs on my box say "Your clock is typically updated once a week", and I believe it. 2. I just ran Zach's program again, with the same Python, and _this_ time 'time' passed 25 times (as did 'monotonic'). 't

[issue20111] pathlib.PurePath.with_suffix() allows creation of otherwise impossible paths

New submission from July Tikhonov: This is not a real-world example, but it brokes some invariant (part of path must not contain separator): >>> pathlib.PurePath('/a/b.c.d').with_suffix('///') PurePosixPath('/a/b.c///') >>> pathlib.PurePath('/a/b.c.d').with_suffix('/not/split/into/parts').parts

[issue16113] SHA-3 (Keccak) support may need to be removed before 3.4

Gregory P. Smith added the comment: I would not bother pulling this out until the week before RC1 if the standard has not yet been declared final. Otherwise, -1 on keeping it under another name. The only hashes we bundle should be standard ones as those are the only ones people will want to u

[issue20110] Misleading word used for __annotations__

New submission from Claudiu.Popa: The documentation for `__annotations__` specify that the dict contains the parameter names ``or`` the return, but this is misleading, because `return` exists even if the parameter keys are present. -- assignee: docs@python components: Documentation fil

[issue17282] document the defaultTest parameter to unittest.main()

R. David Murray added the comment: Thanks Kyle. I reworded it a bit to clarify the precedence of argv over defaultTest. (Also FYI your patch had stray spaces at the ends of the lines.) -- nosy: +r.david.murray resolution: -> fixed stage: patch review -> committed/rejected status: ope

[issue15132] Let unittest.TestProgram()'s defaultTest argument be a list

Roundup Robot added the comment: New changeset 1bbf8c263d3c by R David Murray in branch 'default': Merge and update #17282: Document unittest.main defaultTest argument. http://hg.python.org/cpython/rev/1bbf8c263d3c -- ___ Python tracker

[issue17282] document the defaultTest parameter to unittest.main()

Roundup Robot added the comment: New changeset 045e7a587f3c by R David Murray in branch '3.3': #17282: Document unittest.main defaultTest argument. http://hg.python.org/cpython/rev/045e7a587f3c New changeset 69b5f6924553 by R David Murray in branch '2.7': #17282: Document unittest.main defaultTe

[issue20108] cannot pass kwarg `func` to `inspect.getcallargs`

Roundup Robot added the comment: New changeset b0d472e3ff42 by Benjamin Peterson in branch '3.3': avoid parameter name clash (closes #20108) http://hg.python.org/cpython/rev/b0d472e3ff42 New changeset c265675cd8e2 by Benjamin Peterson in branch 'default': merge 3.3 (closes #20108) http://hg.pyth

[issue20109] TestProgram is mentioned in the unittest docs but is not documented

New submission from R. David Murray: IMO, TestProgram should either be made anonymous in the docs ('main returns an object that has a results attribute...') or its external API should be formally documented. If results is the only external API other than its init (which is documented as unitt

[issue20108] cannot pass kwarg `func` to `inspect.getcallargs`

New submission from Joost van Zwieten: Consider the following example. import inspect inspect.getcallargs(lambda **kwargs: None, func=1) IMHO `getcallargs` should return {'kwargs': {'func': 1}} however, Python (versions 3.3 and 3.4) throws the following exception instead: Typ

[issue16043] xmlrpc: gzip_decode has unlimited read()

Martin v. Löwis added the comment: Demoting this from release blocker: apparently, the release-blocking property was only intended for 2.6.9, which has been released. -- nosy: +loewis priority: release blocker -> critical ___ Python tracker

[issue19407] PEP 453: update the "Installing Python Modules" documentation

Martin v. Löwis added the comment: I suggest that a documentation issue cannot be a release blocker. Most people read the documentation online, and will read an update once it is available. -- nosy: +loewis ___ Python tracker

[issue16113] SHA-3 (Keccak) support may need to be removed before 3.4

Antoine Pitrou added the comment: Either that, or we call it something else than "sha3"? -- ___ Python tracker ___ ___ Python-bugs-lis

[issue19347] PEP 453 implementation tracking issue

Martin v. Löwis added the comment: I propose to downgrade this from "release blocker" again. "prefer to have everything we can sorted" is IMO not a sufficient rationale to block the release; if taken literally, 3.4 could never ever release since it doesn't have everything sorted out that I wou

[issue16113] SHA-3 (Keccak) support may need to be removed before 3.4

STINNER Victor added the comment: Will it be possible/easy to maintain a sha3 module on PyPI? It would be nice to have to for Python 2.6-3.4. @Christian: Are you interested to do that? -- nosy: +haypo ___ Python tracker

[issue19749] test_venv failure on AIX: 'module' object has no attribute 'O_NOFOLLOW'

Martin v. Löwis added the comment: test_venv now passes on that buildbot, apparently since PIP 1.5 has fixed the issue, and is now bundled with Python. -- nosy: +loewis resolution: -> fixed status: open -> closed ___ Python tracker

[issue17997] ssl.match_hostname(): sub string wildcard should not match IDNA prefix

Martin v. Löwis added the comment: Just to clarify the status of this issue: it *only* blocks 3.2. -- priority: release blocker -> normal ___ Python tracker ___ _

[issue16113] SHA-3 (Keccak) support may need to be removed before 3.4

Martin v. Löwis added the comment: I'm going to remove sha3 from the trunk tomorrow unless I hear otherwise. Python shouldn't implement something called "sha3" until SHA-3 actually is a standard. According to the current NIST timeline, the comment period on the draft FIPS should have ended by

[issue20101] Determine correct behavior for time functions on Windows

Roundup Robot added the comment: New changeset 82df66a091da by Zachary Ware in branch '3.3': Issue #20101: Allow test_monotonic to pass on Windows machines on which http://hg.python.org/cpython/rev/82df66a091da New changeset e2a1400b7db9 by Zachary Ware in branch 'default': Issue #20101: Merge w

[issue18604] Consolidate gui available checks in test.support

Changes by Zachary Ware : -- stage: needs patch -> patch review ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue19143] Finding the Windows version getting messier

Changes by Zachary Ware : -- nosy: +zach.ware ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyth

[issue20101] Determine correct behavior for time functions on Windows

Zachary Ware added the comment: Martin v. Löwis wrote: > As a further datapoint, it would be good to find out whether any of you has > NTP enabled, and if so, against what time server. To find out, open the clock > settings ("Datums- und Uhrzeiteinstellungen ändern"), and go to NTP tab > ("Int

[issue20107] Revert PEP 453 integration

Donald Stufft added the comment: pip 1.5 is released and CPython has been updated. -- assignee: -> dstufft resolution: -> fixed status: open -> closed ___ Python tracker ___ __

[issue20101] Determine correct behavior for time functions on Windows

STINNER Victor added the comment: time.get_clock_info("time") and time.get_clock_info("monotonic") is currently using GetSystemTimeAdjustment(). In msg206886 it was said that "GetSystemTimeAdjustment is not the function to look at." Should we modify this function to use NtQueryTimerResolution(

[issue19744] test_venv fails if SSL/TLS is not available

Nick Coghlan added the comment: This should be fixed, so I don't think it's a release blocker any more, but I also don't want to close it until Tim confirms it also works for him. -- priority: release blocker -> deferred blocker status: pending -> open _

[issue20000] SSLContext.get_ca_certs() and self-signed certs

Martin v. Löwis added the comment: BTW, congrats to issue 20,000. -- nosy: +loewis ___ Python tracker ___ ___ Python-bugs-list mailing

[issue20101] Determine correct behavior for time functions on Windows

Martin v. Löwis added the comment: As a further datapoint, it would be good to find out whether any of you has NTP enabled, and if so, against what time server. To find out, open the clock settings ("Datums- und Uhrzeiteinstellungen ändern"), and go to NTP tab ("Internetzeit"). -- nos

[issue19728] PEP 453: enable pip by default in the Windows binary installers

Roundup Robot added the comment: New changeset 4c7b3e7fd4ca by Martin v. Löwis in branch 'default': Issue #19728: Enable pip installation by default on Windows. http://hg.python.org/cpython/rev/4c7b3e7fd4ca -- ___ Python tracker

[issue19728] PEP 453: enable pip by default in the Windows binary installers

Martin v. Löwis added the comment: The command works fine; I have now integrated it into the installer. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___

[issue7475] codecs missing: base64 bz2 hex zlib hex_codec ...

Changes by Jakub Wilk : -- nosy: +jwilk ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/

[issue20050] distutils should check PyPI certs when connecting to it

Changes by Jakub Wilk : -- nosy: +jwilk ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org

[issue20093] Wrong OSError message from os.rename() when dst is a non-empty directory

Changes by Jakub Wilk : -- nosy: +jwilk ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org

[issue19619] Blacklist base64, hex, ... codecs from bytes.decode() and str.encode()

Changes by Jakub Wilk : -- nosy: +jwilk ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org

[issue2943] Distutils should generate a better error message when the SDK is not installed

Holger Waldmann added the comment: On Python 3.3.3 it is even worse. I am using Python 3.3.3 (32bit) on Windows 7 (64bit). Visual Studio C++ 2008 Express Edition is properly installed. Note: I use Python 32bit because Visual Studio C++ 2008 Express Edition includes only the 32bit compiler. Usi

[issue18829] csv produces confusing error message when passed a non-string delimiter

Roundup Robot added the comment: New changeset 0daf7f02c97f by Victor Stinner in branch '3.3': Issue #18829: Add tests for the csv module for invalid characters (delimiter, http://hg.python.org/cpython/rev/0daf7f02c97f New changeset ccb52323039f by Victor Stinner in branch 'default': (Merge 3.3)

[issue18314] Have os.unlink remove junction points

Changes by Antoine Pitrou : -- stage: test needed -> patch review versions: +Python 3.5 -Python 3.4 ___ Python tracker ___ ___ Python-

[issue18314] Have os.unlink remove junction points

Tim Golden added the comment: I'll have a look at this in a week or so when I'm back on-line. -- ___ Python tracker ___ ___ Python-bug

[issue20107] Revert PEP 453 integration

Donald Stufft added the comment: It's not released yet, I'll have it (future tense) release today. It's roughly 6am here and I'm getting ready to get my daughter ready for school. I just happened to check my email before starting that. Once I get her on the bus I'll do the release. --

[issue20107] Revert PEP 453 integration

Martin v. Löwis added the comment: But it's not in git, AFAICT, https://github.com/pypa/pip/blob/1.5.X/pip/__init__.py still has "1.5rc4" in 93820f5e37, and pypi.python.org/pypi/pip still points to 1.4.1. So what do you mean by "released today"? -- ___

[issue20107] Revert PEP 453 integration

Donald Stufft added the comment: I'll have it released today, there are no known issues with the last rc of pip. I just didn't want to release the fix to the distlib issue without a day or two of an RC (which we've now had) and the folks who reported the issue verifying it fixed for them (whic

[issue20107] Revert PEP 453 integration

Larry Hastings added the comment: I agree--though it would be better if you simply got it in before Saturday. -- ___ Python tracker ___ __

[issue20107] Revert PEP 453 integration

Martin v. Löwis added the comment: The only "known" (to me) release date of PIP is documented on http://www.pip-installer.org/en/latest/news.html "Beta and final releases of 1.5 are planned for end of 2013." Apparently, this hasn't happened, either. Something *must* happen by Saturday, I veto

[issue20107] Revert PEP 453 integration

Donald Stufft added the comment: It's basically ready for a release. We had a last minute bug with distlib that was fixed by distlib 0.6 released on 12-31. I was giving the rc that had that bug fix a day or two for any other issues to surface before making the final release. -- _

[issue20107] Revert PEP 453 integration

STINNER Victor added the comment: > So is it ok that I revert the PIP integration by Saturday? I'm not ok, this PEP is expected by many users. There is for example, an article on the PEP: http://lwn.net/Articles/570471/ > According to PEP 453, the integration of pip must be reverted if PIP 1.5

[issue20107] Revert PEP 453 integration

New submission from Martin v. Löwis: According to PEP 453, the integration of pip must be reverted if PIP 1.5 was not released by December 29. AFAICT, this hasn't happened. So is it ok that I revert the PIP integration by Saturday? -- messages: 207149 nosy: dstufft, larry, loewis, ncog

[issue20106] warn_dir is always true for install_data, even if an install_dir is specified

New submission from Tabrez Mohammed: In run(), there is a warning message printed to the console if warn_dir is '1': if self.warn_dir: self.warn("setup script did not provide a directory for " "'%s' -- installing right in '%s'" % (f, self.install_dir)) warn_dir s

[issue2943] Distutils should generate a better error message when the SDK is not installed

Mark Lawrence added the comment: How about "Error: vcvarsall.bat not found - VC++ not installed or wrong version" ? -- nosy: +BreamoreBoy ___ Python tracker ___ _