[issue19715] test_touch_common failure under Windows

Steve Dower added the comment: Or as Martin suggested earlier, time.time() could be returning different values to what the system uses when it creates the file (which I assume is GetSystemTimeAsFileTime/SetFileTime or the kernel-mode equivalent). I only looked briefly at the touch() implementa

[issue19085] Add tkinter basic options tests

Ned Deily added the comment: See msg202006 above. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://ma

[issue19085] Add tkinter basic options tests

Serhiy Storchaka added the comment: Crashes? It should be separate issue, no one Tkinter operation shouldn't crash Python. Fill free to disable this tests on MacOSX (or better on more specific environment) if they prevent the test suite from running. -- __

[issue19715] test_touch_common failure under Windows

Tim Peters added the comment: I have a different theory about this. As explained all over the place, on FAT file creation times are good to 10 milliseconds but modification times only good to 2 seconds. But I can't find one credible word about what the various precisions are for NTFS. For e

[issue19716] test that touch doesn't change file contents

Kushal Das added the comment: Patch to check no change in file content after pathlib.touch(). -- keywords: +patch Added file: http://bugs.python.org/file32792/issue19716_v1.patch ___ Python tracker

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

Ned Deily added the comment: Also, FTR, the "install or upgrade pip" option is currently enabled by default for the OS X installers. -- ___ Python tracker ___ __

[issue19551] PEP 453: Mac OS X installer integration

Changes by Ned Deily : -- priority: release blocker -> resolution: -> fixed stage: needs patch -> committed/rejected status: open -> closed ___ Python tracker ___ _

[issue19551] PEP 453: Mac OS X installer integration

Roundup Robot added the comment: New changeset 257fda20a6cf by Ned Deily in branch 'default': Issue #19551: Update whatsnew. http://hg.python.org/cpython/rev/257fda20a6cf -- ___ Python tracker _

[issue19551] PEP 453: Mac OS X installer integration

Roundup Robot added the comment: New changeset 4e12f145f18f by Ned Deily in branch 'default': Issue #19551: PEP 453 - OS X installer now installs or upgrades pip by default. http://hg.python.org/cpython/rev/4e12f145f18f -- nosy: +python-dev ___ Python

[issue19715] test_touch_common failure under Windows

Tim Peters added the comment: Steve, I'm afraid sleeping 100ns wouldn't be enough. The more data I collect, the more bizarre this gets :-( Across 300 runs I recorded the difference, in nanoseconds, between the "old" and "new" timestamps. A negative difference is a test failure. I was very s

[issue19715] test_touch_common failure under Windows

Steve Dower added the comment: The "000" or "500" still smells of floating point rounding to me. Windows appears to round-trip the values provided perfectly: import ctypes def do_test(t): h = ctypes.windll.kernel32.CreateFileW("test.txt", 0xC000, 7, None, 2, 0, 0) assert h != -1

[issue8813] SSLContext doesn't support loading a CRL

Ned Deily added the comment: This problem also breaks the 32-bit OS X installer build. -- nosy: +larry priority: normal -> release blocker ___ Python tracker ___ _

[issue19715] test_touch_common failure under Windows

Tim Peters added the comment: [MvL] > One "obvious" conversion error is this code from > > http://hg.python.org/cpython/file/4101bfaa76fe/Python/pytime.c#l35 > > microseconds = large.QuadPart / 10 - 116444736; > > This discard the 100ns part of the current time, rounding it > down to the

[issue19715] test_touch_common failure under Windows

Martin v. Löwis added the comment: One "obvious" conversion error is this code from http://hg.python.org/cpython/file/4101bfaa76fe/Python/pytime.c#l35 microseconds = large.QuadPart / 10 - 116444736; This discard the 100ns part of the current time, rounding it down to the previous mic

[issue19729] [regression] str.format sublevel format parsing broken in Python 3.3.3

STINNER Victor added the comment: According to hg bisect, the regression comes from: changeset: 83817:6786e681ed58 branch: 3.3 parent: 83812:cd2457463eeb user:Benjamin Peterson date:Fri May 17 17:34:30 2013 -0500 files: Lib/test/test_unicode.py Misc/NEWS Objec

[issue19729] [regression] str.format sublevel format parsing broken in Python 3.3.3

Benjamin Peterson added the comment: Amusingly, it also works in 3.4. -- nosy: +benjamin.peterson ___ Python tracker ___ ___ Python-bu

[issue19729] [regression] str.format sublevel format parsing broken in Python 3.3.3

Changes by Antoine Pitrou : -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python

[issue19731] Fix copyright footer

Antoine Pitrou added the comment: See https://mail.python.org/pipermail/python-legal-sig/2013-November/59.html -- ___ Python tracker ___ _

[issue19731] Fix copyright footer

STINNER Victor added the comment: > Marc-André pointed out that the copyright footer has the wrong date. In an email? Could you please give the reference to the mail? (I never understood these copyright dates, so it may help me to understand :-)) -- nosy: +haypo __

[issue19730] Clinic fixes: add converters with length, version directive

New submission from Larry Hastings: Two minor changes for Argument Clinic. * Added a "version" directive, so a programmer can require a specific version (or better) of Clinic. * Finished off support for all the 'legacy' converters. The ones today were those that give off a "length" paramet

[issue19085] Add tkinter basic options tests

Ned Deily added the comment: test_widgets.ButtonTest is still causing a Cocoa Tk 8.5/8.6 crash which also crashes Python while running the test suite. The test should be fixed or disabled. -- ___ Python tracker

[issue19731] Fix copyright footer

New submission from Antoine Pitrou: Marc-André pointed out that the copyright footer has the wrong date. See attached patch. -- assignee: docs@python components: Documentation files: copyright.patch keywords: patch messages: 203959 nosy: docs@python, lemburg, pitrou priority: low severi

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

Nick Coghlan added the comment: The examples from the 3.4 What's New may make it clearer why the exception wrapping in the codec machinery is much broader in scope that just detecting output type errors (even though handling that case was the original motivation for the idea): >>> import

[issue19729] [regression] str.format sublevel format parsing broken in Python 3.3.3

Changes by HCT : -- title: str.format sublevel format parsing broken in Python 3.3.3 -> [regression] str.format sublevel format parsing broken in Python 3.3.3 ___ Python tracker ___

[issue19729] [regression] str.format sublevel format parsing broken in Python 3.3.3

Changes by HCT : -- type: -> crash ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mai

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

Nick Coghlan added the comment: Just noting the exact list of codecs that currently bypass the full codec machinery and go direct to the C implementation by normalising the codec name (which includes forcing to lowercase) and then using strcmp to check against a specific set of known encodings

[issue19729] str.format sublevel format parsing broken in Python 3.3.3

New submission from HCT: can't find a way around it... maybe a new regression test on this. Python 3.3.3 (v3.3.3:c3896275c0f6, Nov 18 2013, 21:18:40) [MSC v.1600 32 bit (Intel)] on win32 Type "help", "copyright", "credits" or "license" for more information. >>> "0x{:0{:d}X}".format(0x0,16) Trac

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

Ned Deily added the comment: FTR, on OS X, there is no standard mechanism provided by the Apple-supplied installer program to uninstall binary packages. Thus, most third-party binary distributions for OS X that use the OS X installer can only be uninstalled manually unless they provide some c

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

Donald Stufft added the comment: Also does the PEP need updated? It specifically called out this problem and said that it will leave pip behind? -- ___ Python tracker ___ __

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

Donald Stufft added the comment: I don't know much about installers, can they execute code as part of their uninstall process? -- ___ Python tracker ___

[issue19347] PEP 453 implementation tracking issue

Nick Coghlan added the comment: Created issue 19728 to track what is needed before the installation of pip can be made the default in the installers (at least for Windows, but I assume MvL's concerns would apply equally to the Mac OS X installer) -- ___

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

New submission from Nick Coghlan: While implementing the Windows installer for PEP 453 in issue 19550, MvL pointed out that, *by default*, the installers should be able to uninstall everything they install. At the moment, if they install pip by default, that's not accurate, as we don't curren

[issue19694] test_venv failing on one of the Ubuntu buildbots

Roundup Robot added the comment: New changeset 0ce8d68181a2 by Nick Coghlan in branch 'default': Close #19694: venv now runs ensurepip in isolated mode http://hg.python.org/cpython/rev/0ce8d68181a2 -- nosy: +python-dev resolution: -> fixed stage: needs patch -> committed/rejected status

[issue18874] Add a new tracemalloc module to trace memory allocations

STINNER Victor added the comment: Oh, Jim Jewett found a bug: if set_traceback_limit() is called while tracemalloc is tracing, two tracebacks are seen different because their length is different, whereas the full traceback would be the same. To avoid this issue, I propose to add an optional nf

[issue19694] test_venv failing on one of the Ubuntu buildbots

Nick Coghlan added the comment: Reviewing the current buildbot failures, this is still the only one reporting the error: http://buildbot.python.org/all/builders/AMD64%20Ubuntu%20LTS%203.x/builds/3165/steps/test/logs/stdio I can reproduce the failure locally by running: $ PYTHONWARNINGS=d ./py

[issue19697] refactor pythonrun.c to make use of specs (__main__.__spec__)

Eric Snow added the comment: I've already started on this somewhat. However, I'm going to close out more of the other PEP 451 issues before going any further. Nick: when do you think things will settle down that you could field a question or two and some reviews relative to the __main__ chang

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

Nick Coghlan added the comment: Note that I still plan to do a documentation-only PEP for 3.4, proposing some adjustments to the way the codecs module is documented, making binary and test transform defined terms in the glossary, etc. I'll probably aim for beta 2 for that. -- ___

[issue19727] os.utime(..., None) has poor resolution on Windows

New submission from Antoine Pitrou: os.utime() uses the following code when times is None under Windows: SYSTEMTIME now; GetSystemTime(&now); if (!SystemTimeToFileTime(&now, &mtime) || !SystemTimeToFileTime(&now, &atime)) { PyErr_SetFromWindowsErr(

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

Roundup Robot added the comment: New changeset 5e960d2c2156 by Nick Coghlan in branch 'default': Close #7475: Restore binary & text transform codecs http://hg.python.org/cpython/rev/5e960d2c2156 -- nosy: +python-dev resolution: -> fixed stage: -> committed/rejected status: open -> clos

[issue19715] test_touch_common failure under Windows

Antoine Pitrou added the comment: I thought that using utime(..., None) would be better, but it's actually much worse: it calls GetSystemTime, which only has millisecond precision, while time.time() calls GetSystemTimeAsFileTime which has better precision. (this is probably a bug in utime())

[issue19715] test_touch_common failure under Windows

Roundup Robot added the comment: New changeset a273f99159e0 by Antoine Pitrou in branch 'default': Revert utime(..., None) strategy (it has too poor resolution under Windows) and restore the previous test workaround http://hg.python.org/cpython/rev/a273f99159e0 -- _

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

STINNER Victor added the comment: > Regarding UTF-8 et al, the existing shortcuts in unicodeobject.c already > bypass the full codec machinery, and that includes the exception wrapping > on failures. There are still platforms using locale encodings different than ascii, latin1 or utf8. For examp

[issue19715] test_touch_common failure under Windows

Roundup Robot added the comment: New changeset d647a4a8505e by Antoine Pitrou in branch 'default': Trying other strategy for #19715: use utime(..., None) http://hg.python.org/cpython/rev/d647a4a8505e -- ___ Python tracker

[issue19722] Expose stack effect calculator to Python

Larry Hastings added the comment: stack_effect will never know about EXTENDED_ARG. Instead, you simply pass the already-extended arg as the second argument. Making the second argument support a default of None will be slightly inconvenient, but I'll do it if you think it's a big improvement.

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

Nick Coghlan added the comment: With issue 19619 resolved for Python 3.4 (the issue itself remains open awaiting a backport to 3.3), Victor has softened his stance on this topic and given the go ahead to restore the codec aliases: http://bugs.python.org/issue19619#msg203897 I'll be committing

[issue19715] test_touch_common failure under Windows

Martin v. Löwis added the comment: OTOH, a time.time() in units of 100ns needs 53.6 bits, so it should "almost" fit. -- ___ Python tracker ___ __

[issue19715] test_touch_common failure under Windows

Antoine Pitrou added the comment: Looking at one of the failure instances: >>> math.frexp(1385150397.383464)[0] * 2**53 5809741852347053.0 >>> math.frexp(1385150397.3834648)[0] * 2**53 5809741852347056.0 It doesn't seem that lack of FP precision would be sufficient to explain the problem, alth

[issue19715] test_touch_common failure under Windows

Martin v. Löwis added the comment: Looking at the ReactOS sources, it appears that Windows doesn't do any rounding, so it's all Python's fault. Windows keeps its system time (in KI_USER_SHARED_DATA) in essentially a FILETIME represenation (i.e. units of 100ns since 1601), and never needs to co

[issue19713] Deprecate various things in importlib thanks to PEP 451

Eric Snow added the comment: It's definitely worth it to be more explicit. (Brett had referenced msg202663.) When I get some time I'll update this ticket with a list of the specific deprecation items. -- ___ Python tracker

[issue19722] Expose stack effect calculator to Python

Nick Coghlan added the comment: Hmm, looking at dis.py, I'm -1 on exposing this as a public opcode module API at this point, although I'm still a fan of exposing it as opcode._stack_effect to allow advanced users access (ala sys._get_frames). I initially thought the required addition to dis.In

[issue19715] test_touch_common failure under Windows

Roundup Robot added the comment: New changeset 602062d2a008 by Antoine Pitrou in branch 'default': Try to fix issue #19715 (timestamp rounding inconsistencies under Windows?) http://hg.python.org/cpython/rev/602062d2a008 -- ___ Python tracker

[issue19715] test_touch_common failure under Windows

Antoine Pitrou added the comment: > No, I really meant step 4 (touch). The second touch call *really* > steps backwards. I don't find that very surprising, since it is > actually the first call that passes an actual time. Ok, now I see what you mean. Indeed, we are calling utime() on the file w

[issue19715] test_touch_common failure under Windows

Martin v. Löwis added the comment: >> Then, the utime call in step 4 asked to set this to > You mean step 3, right? ("date back 10s") No, I really meant step 4 (touch). The second touch call *really* steps backwards. I don't find that very surprising, since it is actually the first call that

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

Nick Coghlan added the comment: Yay, thanks Victor! Regarding UTF-8 et al, the existing shortcuts in unicodeobject.c already bypass the full codec machinery, and that includes the exception wrapping on failures. -- ___ Python tracker

[issue19726] BaseProtocol is not an ABC

Guido van Rossum added the comment: Good question. I don't mind making these ABCs, but I don't think it's necessary to do it before beta1 (since it won't matter for most people). -- ___ Python tracker

[issue19358] Integrate "Argument Clinic" into CPython build

Larry Hastings added the comment: (Whoops, forgot to attach the new diff.) -- Added file: http://bugs.python.org/file32788/larry.make.clinic.patch.2.diff ___ Python tracker ___ _

[issue19358] Integrate "Argument Clinic" into CPython build

Larry Hastings added the comment: Okay, there's more than one way to skin this cat. This version uses os.walk(). -- ___ Python tracker ___ __

[issue19659] Document Argument Clinic

Nick Coghlan added the comment: While it's still a private tool, something in the dev guide would be appropriate, then it can be promoted to the regular docs if it becomes a public capability in 3.5. -- ___ Python tracker

[issue19722] Expose stack effect calculator to Python

Nick Coghlan added the comment: +1 from me. A stack_effect attribute on dis.Instruction would be a nice bonus, but doesn't need to be part of this patch. -- ___ Python tracker __

[issue19726] BaseProtocol is not an ABC

New submission from Antoine Pitrou: BaseProtocol docstring describes it as an "ABC for base protocol class", but it is not actually an ABC in the technical sense. -- assignee: gvanrossum components: Library (Lib) messages: 203921 nosy: gvanrossum, pitrou priority: normal severity: norma

[issue19713] Deprecate various things in importlib thanks to PEP 451

Nick Coghlan added the comment: Keep in mind we figured out post-PEP acceptance that there are still a couple of obscure use cases that need the old loader API, so we may want to keep that around as a "power user" mode rather than deprecating it (either forever or until a replacement is defined i

[issue18059] Add multibyte encoding support to pyexpat

Marc-Andre Lemburg added the comment: On 22.11.2013 23:03, STINNER Victor wrote: > > I'm not sure that multibyte encodings other than UTF-8 are used in the world. > I'm not convinced that we should support them. If the changes are small, it's > maybe not a bad thing. Do you know which applicat

[issue19291] Add docs for asyncio package (Tulip, PEP 3156)

Roundup Robot added the comment: New changeset e4b7377a690a by Antoine Pitrou in branch 'default': Issue #19291: add crude stubs to the asyncio docs http://hg.python.org/cpython/rev/e4b7377a690a -- nosy: +python-dev ___ Python tracker

[issue19291] Add docs for asyncio package (Tulip, PEP 3156)

Guido van Rossum added the comment: Thanks -- please just commit, we can iterate. -- ___ Python tracker ___ ___ Python-bugs-list maili

[issue19291] Add docs for asyncio package (Tulip, PEP 3156)

Antoine Pitrou added the comment: Following patch stubs a couple of things, this is very crude though. -- Added file: http://bugs.python.org/file32787/asyncio_stub.patch ___ Python tracker _

[issue19358] Integrate "Argument Clinic" into CPython build

STINNER Victor added the comment: + $(RUNSHARED) $(PYTHON_FOR_BUILD) ./Tools/clinic/clinic.py */*.c There are deeper directories containing .c files: Mac/Tools, Modules/cjkcodecs, Modules/_ctypes, Modules/_decimal, Modules/expat, ./PC/bdist_wininst, etc. -- _

[issue19715] test_touch_common failure under Windows

Roundup Robot added the comment: New changeset 716e41100553 by Victor Stinner in branch 'default': Issue #19715: Ensure that consecutive calls to monotonic() are monotonic http://hg.python.org/cpython/rev/716e41100553 -- ___ Python tracker

[issue19715] test_touch_common failure under Windows

Tim Peters added the comment: Here's a failure with the patch: self.assertGreaterEqual(st.st_mtime_ns, old_mtime_ns) AssertionError: 1385161652120374900 not greater than or equal to 1385161652120375500 And another: AssertionError: 1385161754170484000 not greater than or equal to 1385161754

[issue19358] Integrate "Argument Clinic" into CPython build

Larry Hastings added the comment: Attached is a patch to at least add a "make clinic" target for the UNIX-like platforms. This doesn't add anything for the Windows build. -- keywords: +patch stage: -> patch review Added file: http://bugs.python.org/file32786/larry.make.clinic.patch.1.

[issue19715] test_touch_common failure under Windows

Steve Dower added the comment: > 7. verify original_mtime - 0.001 < p.stat().st_mtime < original_mtime + 0.001 Actually, don't check the upper-bound here... that's a bad idea :) -- ___ Python tracker _

[issue19715] test_touch_common failure under Windows

Steve Dower added the comment: I don't have any extra insight into this. The documented resolution for mtime on NTFS is 100ns (2s on FAT32), so without delaying by at least that long you're not going to see an official change. The noise is probably from floating-point conversions (in _PyTime_O

[issue19715] test_touch_common failure under Windows

Antoine Pitrou added the comment: > 3. Python uses an insane (non-monotonic) scheme to convert the time > to a float. Yes, I was at least hoping to clear that out. The code is there: http://hg.python.org/cpython/file/4101bfaa76fe/Modules/posixmodule.c#l1459 Other than that, I suppose I can hack

[issue19674] Add introspection information for builtins

Larry Hastings added the comment: I went with __text_signature__. I also did some more polishing, and added / fixed the unit tests, and even added a Misc/NEWS. Is it good enough to go in before the beta? -- Added file: http://bugs.python.org/file32785/larry.introspection.for.builtin

[issue19715] test_touch_common failure under Windows

Tim Peters added the comment: FYI, the test fails on my box (32-bit Windows Vista) about 1 time in 3. Here's the latest failure: AssertionError: 1385160333.612968 not greater than or equal to 1385160333.6129684 And here's another: AssertionError: 1385160530.348423 not greater than or equal

[issue18059] Add multibyte encoding support to pyexpat

Serhiy Storchaka added the comment: > I'm not sure that multibyte encodings other than UTF-8 are used in the world. I don't use any of them but I heard some of them are still widely used. This issue was provoked by issue13612. See also related issue15877. > pyexpat_encoding_create() looks like

[issue8813] SSLContext doesn't support loading a CRL

Ned Deily added the comment: 10.4 is *very* old: $ /usr/bin/openssl version OpenSSL 0.9.7l 28 Sep 2006 If you kept around that version of the headers and libs, you'd probably catch most of the problems. -- ___ Python tracker

[issue8813] SSLContext doesn't support loading a CRL

Christian Heimes added the comment: :( I seriously need access to a Darwin or OSX box. This is the second time I broke the build on OSX. Ned Deily schrieb: > >Ned Deily added the comment: > >This change seems to have broken the OS X 10.4 Tiger buildbot: > >_ssl.c:2240: error: 'struct x509_sto

[issue19715] test_touch_common failure under Windows

Roundup Robot added the comment: New changeset 4101bfaa76fe by Antoine Pitrou in branch 'default': Try to debug issue #19715 http://hg.python.org/cpython/rev/4101bfaa76fe -- nosy: +python-dev ___ Python tracker ___

[issue19467] asyncore documentation: redirect users to the new asyncio module

Guido van Rossum added the comment: Heh, I'd forgotten about this issue. Done. :-) -- assignee: -> gvanrossum resolution: -> fixed stage: -> committed/rejected status: open -> closed type: -> enhancement ___ Python tracker

[issue19467] asyncore documentation: redirect users to the new asyncio module

STINNER Victor added the comment: Guido: I see that you added a note in asyncore and asynchat doc. Can you close the issue? http://hg.python.org/cpython/rev/db6ae01a5f7f changeset: 87364:db6ae01a5f7f user:Guido van Rossum date:Fri Nov 22 11:57:35 2013 -0800 summary: Add not

[issue19715] test_touch_common failure under Windows

Antoine Pitrou added the comment: To recap a bit, here is a very simplified view of the test: A. path is opened for writing (and then closed) B. its st_mtime is recorded in old_mtime C. path is opened again for writing (and closed) D. assert `path's current mtime` >= old_mtime Whatever the deta

[issue19723] Argument Clinic should add markers for humans

Larry Hastings added the comment: > However, to bikeshed a little, I would prefer > "preprocessor" instead of "clinic", since jokes > tend to wear off if one sees then too often. "Argument Clinic" is the name of the tool. The marker /*[clinic]*/ was chosen deliberately: * If someone says "what

[issue18059] Add multibyte encoding support to pyexpat

STINNER Victor added the comment: I'm not sure that multibyte encodings other than UTF-8 are used in the world. I'm not convinced that we should support them. If the changes are small, it's maybe not a bad thing. Do you know which applications use such codecs? pyexpat_encoding_create() looks l

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

STINNER Victor added the comment: With blacklisted transform codecs, I'm fine with the idea of restoring codecs aliases for transform codecs in Python 3.4. Go ahead Nick. -- For Python 3.5, a better solution should be found to declare transform codecs. And I had like to also add transform()/u

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

STINNER Victor added the comment: > Victor, please accept the fact that the codec sub-system in Python > doesn't only have the Unicode implementation as target. It's > true that most codecs were added for the Unicode implementation, > but I deliberately designed the system to be open for other >

[issue14373] C implementation of functools.lru_cache

Serhiy Storchaka added the comment: Updated patch fixes bugs found by Antoine. Thank you Antoine. -- Added file: http://bugs.python.org/file32784/clru_cache2.patch ___ Python tracker ___

[issue8813] SSLContext doesn't support loading a CRL

Ned Deily added the comment: This change seems to have broken the OS X 10.4 Tiger buildbot: _ssl.c:2240: error: 'struct x509_store_st' has no member named 'param' _ssl.c:2253: error: 'struct x509_store_st' has no member named 'param' _ssl.c:2257: error: 'struct x509_store_st' has no member named

[issue19659] Document Argument Clinic

STINNER Victor added the comment: > I quite agree. My plan is to write a quick HOWTO for now to get > people up and running for now, then flesh it out into a full document. Oh yes, I prefer a practical doc based on examples rather a full reference of the API. -- _

[issue19725] Richer stat object

New submission from Philip Jenvey: With discussion of the new Pathlib API there's been suggestion (and maybe even already consensus) that some of the convenience APIs provided by it should exist on stat result objects. It's maybe too late for 3.4, but let's track exactly what additions are wan

[issue17457] Unittest discover fails with namespace packages and builtin modules

Claudiu.Popa added the comment: Added patch which addresses Eric's comments. It contains a situation which I'm not so happy, mostly due to not knowing in depth (or at least at a comfortable level) the import mechanics: in the AttributeError except handler, if the spec can't be determined and t

[issue19718] Path.glob() on case-insensitive Posix filesystems

Antoine Pitrou added the comment: Ok, thanks (and thanks Brett for writing and testing the patch)! -- resolution: -> fixed stage: -> committed/rejected status: open -> closed ___ Python tracker __

[issue19671] Option to select the optimization level on compileall

Sworddragon added the comment: After checking it: Yes it does, thanks for the hint. In this case I'm closing this ticket now. -- resolution: -> invalid status: open -> closed ___ Python tracker __

[issue19718] Path.glob() on case-insensitive Posix filesystems

Ned Deily added the comment: test_pathlib now passes. I'd say it's fixed until someone claims otherwise. -- ___ Python tracker ___ __

[issue19715] test_touch_common failure under Windows

Antoine Pitrou added the comment: > I think I found the problem. In one run, the current time (as reported > by time.time()) was > > 1385154213.291315 > > On the first touch call (in step 1), the file is not there, and gets > its current time internally from the system (not sure which part > ex

[issue19718] Path.glob() on case-insensitive Posix filesystems

Antoine Pitrou added the comment: > FWIW, it looks like Path.glob() is behaving the same as the default > shell (bash 3.2 on OS X 10.6.8) Thanks, we're in good company then (or at least we're not alone :-)). Do you think I should fix this issue as fixed now? -- __

[issue19718] Path.glob() on case-insensitive Posix filesystems

Roundup Robot added the comment: New changeset 4734f6e2fd2f by Antoine Pitrou in branch 'default': Issue #19718: add one more globbing test under POSIX http://hg.python.org/cpython/rev/4734f6e2fd2f -- ___ Python tracker

[issue12226] use HTTPS by default for uploading packages to pypi

Christian Heimes added the comment: How about: - load ca cert from default verify locations - try connect with CERT_REQUIRED - print warning when cert validation fails and try again with CERT_NONE - match hostname otherwise At least this warns the user about the issue. Is there way to distingui

[issue19718] Path.glob() on case-insensitive Posix filesystems

Ned Deily added the comment: FWIW, it looks like Path.glob() is behaving the same as the default shell (bash 3.2 on OS X 10.6.8): Python 3.4.0a4+ (default:cce14bc9b675, Nov 22 2013, 13:01:47) [GCC 4.2.1 (Apple Inc. build 5666) (dot 3)] on darwin Type "help", "copyright", "credits" or "license"

[issue19715] test_touch_common failure under Windows

Martin v. Löwis added the comment: I think I found the problem. In one run, the current time (as reported by time.time()) was 1385154213.291315 On the first touch call (in step 1), the file is not there, and gets its current time internally from the system (not sure which part exactly assigns

[issue19718] Path.glob() on case-insensitive Posix filesystems

Roundup Robot added the comment: New changeset cd09766bb18f by Brett Cannon in branch 'default': Issue #19718: Add a case-insensitive FS check to test.support to use http://hg.python.org/cpython/rev/cd09766bb18f -- nosy: +python-dev ___ Python tracker

  1   2   3   4   >