[issue28165] The 'subprocess' module leaks roughly 4 KiB of memory per call

Xavion added the comment: I wouldn't have reported this if it was only happening *once*. I already have it in a loop; a new shell command is fired every second. The memory footprint increases by roughly 4 KiB *each* time. I monitor it via the following Bash script: while true; do

[issue28150] Error CERTIFICATE_VERIFY_FAILED in macOS

Ned Deily added the comment: Sorry, the information about this feature is currently only documented in the OS X installer ReadMe. As you noted, it's displayed to the user during installation when using the OS X installer app. A copy of the ReadMe is also installed for later reference in the

[issue28165] The 'subprocess' module leaks roughly 4 KiB of memory per call

Antti Haapala added the comment: 3.5.1+ ubuntu; I run the Popen case in while True, and watch `top` - not a single digit changes in the memory usage (the last digit being the kilobytes). That the memory footprint increases *once* by 4KiB is nothing; please run this in a loop. --

[issue28165] The 'subprocess' module leaks roughly 4 KiB of memory per call

New submission from Xavion: Each time I run a shell command via the 'subprocess' module, I notice that the memory footprint of my program increases by roughly 4 KiB. I've tested the problem with two different slices of code; the result is the same in either case (long after the function

[issue28099] Drop Mac OS X Tiger support in Python 3.6

Changes by Ned Deily : -- assignee: -> ned.deily ___ Python tracker ___ ___

[issue26081] Implement asyncio Future in C to improve performance

INADA Naoki added the comment: This is the patch. And git branch is here https://github.com/methane/cpython/pull/5 -- Added file: http://bugs.python.org/file44670/fastfuture.patch ___ Python tracker

[issue28164] _PyIO_get_console_type fails for various paths

New submission from Eryk Sun: _PyIO_get_console_type currently hard codes the names "CON", "CONIN$", and "CONOUT$" and doesn't use a case-insensitive comparison. For example, opening "conin$" doesn't get directed to WindowsConsoleIO: >>> open('conin$', 'rb', buffering=0) <_io.FileIO

[issue28055] pyhash's siphash24 assumes alignment of the data pointer

Changes by Ned Deily : -- priority: normal -> high stage: needs patch -> patch review versions: +Python 3.7 ___ Python tracker ___

[issue21337] Add tests for Tix

Zachary Ware added the comment: Tix is now deprecated, extra tests are unnecessary. -- resolution: -> out of date stage: needs patch -> resolved status: open -> closed ___ Python tracker

[issue28140] Attempt to give better errors for pip commands typed into the REPL

Nick Coghlan added the comment: Given that this can be done with just an excepthook change, I'm going to suggest we make the change for 3.5 and 2.7 as well. -- versions: +Python 2.7, Python 3.5 ___ Python tracker

[issue28163] WindowsConsoleIO fileno() passes wrong flags to _open_osfhandle

New submission from Eryk Sun: WindowsConsoleIO fileno() gets a file descriptor on demand by calling _open_osfhandle. As a low I/O function this expects _open flags, but currently the code is passing 'rb' (int 0x7262) and 'wb' (int 0x7762). It should use _O_RDONLY | _O_BINARY and _O_WRONLY |

[issue28162] WindowsConsoleIO readall() fails if first line starts with Ctrl+Z

New submission from Eryk Sun: For a console readall(), if the first line starts with '\x1a' (i.e. Ctrl+Z), it breaks out of its read loop before incrementing len. Thus the input isn't handled properly as EOF, for which the check requires len > 0. Instead it ends up calling WideCharToMultiByte

[issue28140] Attempt to give better errors for pip commands typed into the REPL

Nick Coghlan added the comment: Paul Moore pointed out on distutils-sig that since this is mainly desired for the REPL, we can put the logic in the default excepthook rather than into the SyntaxError constructor the way we had to for "print" and "exec": def excepthook(typ, value,

[issue28161] Opening CON for write access fails

New submission from Eryk Sun: When opening the CON device the underlying CreateFile call needs to use either GENERIC_READ or GENERIC_WRITE access, but not both. Currently opening for writing fails as follows: >>> open('CON', 'wb', buffering=0) Traceback (most recent call last):

[issue26081] Implement asyncio Future in C to improve performance

Yury Selivanov added the comment: > Implementing __del__ and __repr__ in C is bit hard task to me. > I can't do it in this week. (maybe I can't do it in this month too.) NP. I'll take a look myself after you upload the next iteration of the patch... --

[issue26081] Implement asyncio Future in C to improve performance

INADA Naoki added the comment: I'm working on fixing points you commented. Wait a minute. Implementing __del__ and __repr__ in C is bit hard task to me. I can't do it in this week. (maybe I can't do it in this month too.) On Thu, Sep 15, 2016 at 7:37 AM, Yury Selivanov

[issue9334] argparse does not accept options taking arguments beginning with dash (regression from optparse)

paul j3 added the comment: Clint, 'nargs=argparser.REMAINDER' ('...') may do what you want p=argparse.ArgumentParser() p.add_argument('--subscipt_args', nargs='...') p.add_argument('pos',nargs='*') p.parse_args('--subscipt_args --foo --bar --baz -- other args'.split())

[issue28147] Unbounded memory growth resizing split-table dicts

INADA Naoki added the comment: xiang is right. Python 3.5 has same issue when using popitem(). I'll make patch for 3.5. But it will be bit differ from patch for 3.6 and they will conflict. -- ___ Python tracker

[issue27906] Socket accept exhaustion during high TCP traffic

Guido van Rossum added the comment: (Of course I meant b2.) -- ___ Python tracker ___ ___ Python-bugs-list

[issue28160] Python -V and --version output to stderr instead of stdout

Berker Peksag added the comment: Thanks for the report. This was already done in Python 3.4. See https://docs.python.org/dev/whatsnew/3.4.html#changes-in-python-command-behavior and issue 18338 for details. Backporting this to 2.7 would break backwards compatibility so that means we can't

[issue27906] Socket accept exhaustion during high TCP traffic

Yury Selivanov added the comment: > @Yury, do you think you could get to this before b1 goes out? It's a pure > optimization (and a good one!). LGTM. Will commit tomorrow. -- assignee: -> yselivanov ___ Python tracker

[issue27906] Socket accept exhaustion during high TCP traffic

Guido van Rossum added the comment: Sorry, we didn't get to this. @Yury, do you think you could get to this before b1 goes out? It's a pure optimization (and a good one!). -- ___ Python tracker

[issue28160] Python -V and --version output to stderr instead of stdout

Yaron Goland added the comment: To be fair it turns out that Java also outputs its version to stderr. Still seems wrong. It's not an error! -- ___ Python tracker

[issue28160] Python -V and --version output to stderr instead of stdout

New submission from Yaron Goland: When running python -V or --version the output goes to stderr instead of stdout. Unless python thinks its version is an err shouldn't the result go to stdout? -- components: Macintosh messages: 276496 nosy: Yaron Goland, ned.deily, ronaldoussoren

[issue28055] pyhash's siphash24 assumes alignment of the data pointer

STINNER Victor added the comment: Christian Heimes added the comment: > The main reason for two different hash algorithms was missing support for 64bit integer types. Python 3.4 was targeting platforms that had no 64bit integer support at all (IIRC SPARC). Nowaday Python requires 64bit ints to

[issue26182] Deprecation warnings for the future async and await keywords in Python 3.6

Changes by Guido van Rossum : -- nosy: -gvanrossum ___ Python tracker ___ ___

[issue26081] Implement asyncio Future in C to improve performance

Yury Selivanov added the comment: INADA, would you be able to address my last review comments? Also, I'm wondering what if we could implement __del__ and __repr__ in C too, so that we could drop BaseFuture class? -- ___ Python tracker

[issue26182] Deprecation warnings for the future async and await keywords in Python 3.6

Yury Selivanov added the comment: I had to rewrite the patch to make sure it reports correct position and covers all cases where using async/await should trigger a warning. Brett, could you please take a look at the patch? -- Added file:

[issue28130] Document that time.tzset updates time module globals

Changes by Alexander Belopolsky : -- title: Document that time.tzset updates time module constants -> Document that time.tzset updates time module globals ___ Python tracker

[issue1100942] Add datetime.time.strptime and datetime.date.strptime

Changes by Alexander Belopolsky : -- assignee: belopolsky -> priority: high -> versions: +Python 3.7 -Python 3.6 ___ Python tracker

[issue28159] Deprecate isdst argument in email.utils.localtime

New submission from Alexander Belopolsky: With the implementation of PEP 495, email.utils.localtime() does not need the isdst argument to disambiguate naive time. In fact the utility method itself is redundant given that astimezone() now works for naive instances. -- components:

[issue25478] Consider adding a normalize() method to collections.Counter()

Antoine Pitrou added the comment: The pitfall I imagine here is that if you continue adding elements after normalize() is called, the results will be nonsensical. -- nosy: +pitrou ___ Python tracker

[issue28148] [Patch] Also stop using localtime() in timemodule

Changes by Antoine Pitrou : -- nosy: -pitrou ___ Python tracker ___ ___ Python-bugs-list

[issue28148] [Patch] Also stop using localtime() in timemodule

Alexander Belopolsky added the comment: > I thought `[...]localtime_r()`'s way of ordering the arguments made most > sense here. Right. I keep forgetting which one is localtime_r and which is localtime_s. I don't think there is any preference in the Python codebase. (PEP 8 is silent on this

[issue28158] Implement LOAD_GLOBAL opcode cache

Changes by Guido van Rossum : -- nosy: -gvanrossum ___ Python tracker ___ ___

[issue28148] [Patch] Also stop using localtime() in timemodule

Ed Schouten added the comment: I've been brainwashed by https://google.github.io/styleguide/cppguide.html#Function_Parameter_Ordering over the last couple of years, which is why I thought `localtime()/localtime_r()`'s way of ordering the arguments made most sense here. ;-) --

[issue28158] Implement LOAD_GLOBAL opcode cache

Changes by Brett Cannon : -- nosy: +brett.cannon ___ Python tracker ___ ___

[issue28148] [Patch] Also stop using localtime() in timemodule

Alexander Belopolsky added the comment: I see that you picked localtime_s-like order of arguments. While I have no personal preference, I wonder why you prefer output to follow input. The usual UNIX/C convention is the opposite. Interfaces like sprintf, strcat, strftime and many other have

[issue28148] [Patch] Also stop using localtime() in timemodule

Alexander Belopolsky added the comment: Very nice. I'll give it a week or two for the others to chime in and commit if I don't hear any objections. -- keywords: +patch stage: patch review -> commit review versions: +Python 3.7 ___ Python tracker

[issue9334] argparse does not accept options taking arguments beginning with dash (regression from optparse)

Clint Olsen added the comment: I'm not sure if this is applicable to this bug, but one feature missing from argparse is the ability to snarf arbitrary options up to a terminating '--'. The purpose of this is to collect arguments for potential children you may spawn. An example:

[issue28158] Implement LOAD_GLOBAL opcode cache

New submission from Yury Selivanov: The attached patch implements an opcode cache for LOAD_GLOBAL opcode, making it 2x faster. The idea is to use the new co_extra field of code objects & PEP 509 to attach a cache structure pointing directly to the resolved global name. When globals or

[issue28148] [Patch] Also stop using localtime() in timemodule

Ed Schouten added the comment: Does this patch look all right to you? -- Added file: http://bugs.python.org/file44667/patch-pytime-localtime-gmtime ___ Python tracker

[issue28147] Unbounded memory growth resizing split-table dicts

Changes by INADA Naoki : Added file: http://bugs.python.org/file44666/fix-28147.patch ___ Python tracker ___

[issue28147] Unbounded memory growth resizing split-table dicts

INADA Naoki added the comment: This issue is caused by dictresize() and _PyObjectDict_SetItem() 1. a.__dict__.pop('a') convert the dict to combined table which has double keysize. 2. a.a = 1 converts the dict to split table again if there are no instances sharing key with class. As I wrote

[issue28147] Unbounded memory growth resizing split-table dicts

Changes by INADA Naoki : Added file: http://bugs.python.org/file44665/fix-28147.patch ___ Python tracker ___

[issue28147] Unbounded memory growth resizing split-table dicts

Xiang Zhang added the comment: > popitem() before does the same thing and should never cause a problem. Ahh, this seems not true. Test it in py3.5 also crash. -- ___ Python tracker

[issue28147] Unbounded memory growth resizing split-table dicts

Xiang Zhang added the comment: > I confirmed and investigated it. Thanks! I'll post patch including more test in 24 hours. Please wait a second. The cause of this problem is that attribute setting causes a combined table to be splitted (the code path is [0]->[1]->[2]->[3]). So every time you

[issue28148] [Patch] Also stop using localtime() in timemodule

Alexander Belopolsky added the comment: > Maybe we can just pick a prototype that's as Pythonesque as possible that > also fixes these shortcomings. Any thoughts? Yes, and just call it _PyTime_localtime without the ugly suffix. -- ___ Python

[issue28148] [Patch] Also stop using localtime() in timemodule

Ed Schouten added the comment: As a person who keeps a close eye on the Austin Group mailing lists (i.e., 'the POSIX working group'), my guess is that it's very unlikely that POSIX will ever add those *_s() extensions. Here's a discussion on Reddit that actually captures all of the arguments

[issue22799] wrong time.timezone

Changes by Alexander Belopolsky : -- superseder: -> Document time module constants (timezone, tzname, etc.) as deprecated. ___ Python tracker

[issue28157] Document time module constants (timezone, tzname, etc.) as deprecated.

New submission from Alexander Belopolsky: The time module defines timezone, altzone, tzname and daylight constants that store information about system timezone. This information is derived from the timezone rules that are in effect at the module loading time, but may be incorrect for the

[issue28147] Unbounded memory growth resizing split-table dicts

INADA Naoki added the comment: I confirmed and investigated it. Thanks! I'll post patch including more test in 24 hours. -- ___ Python tracker ___

[issue22799] wrong time.timezone

Alexander Belopolsky added the comment: Closing. See #22798 for the reasons why synchronizing C variables with the time module constants is not a solution. -- resolution: -> wont fix status: open -> closed ___ Python tracker

[issue26669] time.localtime(float("NaN")) does not raise a ValueError on all platforms

Changes by Alexander Belopolsky : -- assignee: -> belopolsky nosy: +belopolsky stage: -> needs patch type: -> behavior ___ Python tracker

[issue28148] [Patch] Also stop using localtime() in timemodule

Alexander Belopolsky added the comment: > we should likely introduce full wrappers that have a name starting with > _PyTime_, right? Yes, and I would like to give some thought to what the best API would be. The two choices are to emulate localtime_r on Windows or emulate localtime_s on

[issue28148] [Patch] Also stop using localtime() in timemodule

Ed Schouten added the comment: Hi Alexander, I'm absolutely no expert when it comes to the Python codebase, so I've got a question. If we're going to movein this to Include/pytime.h, we should likely introduce full wrappers that have a name starting with _PyTime_, right? This header seem to

[issue16384] import.c doesn't handle EOFError from PyMarshal_Read*

Sye van der Veen added the comment: I would also agree that failing to load the main codec should be an abort. This bug was specifically the race condition in writing the .pyc file. Thanks for all your help! -- ___ Python tracker

[issue28148] [Patch] Also stop using localtime() in timemodule

Alexander Belopolsky added the comment: Yes, I think this is a good idea. I was hesitant to make this change while #22798 was open because I thought we may end up exposing changes to tzname caused by localtime and friends. I also believe we can classify this as a bug-fix because side-effects

[issue28148] [Patch] Also stop using localtime() in timemodule

Alexander Belopolsky added the comment: > What would be the right location for [the Windows wrappers]? I would say Include/pytime.h: /** Symbols and macros to supply platform-independent interfaces to time related

[issue28156] [Patch] posixmodule: Make the presence of os.getpid() optional

New submission from Ed Schouten: CloudABI (https://mail.python.org/pipermail/python-dev/2016-July/145708.html) does not provide getpid(). Though this may sound quite silly at first, there is quite a good reason for this. One of the things that CloudABI wants to achieve is making large scale

[issue28148] [Patch] Also stop using localtime() in timemodule

Changes by Ed Schouten : -- title: Also stop using localtime() in timemodule -> [Patch] Also stop using localtime() in timemodule ___ Python tracker

[issue28155] Small typo in Json docs

Zachary Ware added the comment: See 05e8b25379a3, though; it may be worth a backport. Not to 3.3, though; it's docs are not being updated anymore. -- nosy: +zach.ware versions: -Python 3.3 ___ Python tracker

[issue28155] Small typo in Json docs

Changes by SilentGhost : -- status: open -> closed ___ Python tracker ___ ___

[issue28155] Small typo in Json docs

SilentGhost added the comment: The space between -m switch and module name is not mandatory as you should be able to see if you run those examples. -- nosy: +SilentGhost resolution: -> not a bug stage: -> resolved ___ Python tracker

[issue28155] Small typo in Json docs

New submission from Андрей Морозько: In Json module, example titled "Using json.tool from the shell to validate and pretty-print:" 5th line reads: echo '{1.2:3.4}' | python -mjson.tool should echo '{1.2:3.4}' | python -m json.tool -- assignee: docs@python components: Documentation

[issue28154] Core dump after importing lxml in Python3.6b

Filip Stefanov added the comment: My source was out of date... You are right now is working fine Sorry for the time wasted. :) -- resolution: -> out of date status: open -> closed ___ Python tracker

[issue28114] parse_envlist(): os.execve(), os.spawnve(), etc. crash in Python 3.6.0 when env contains byte strings

Berker Peksag added the comment: Eryk's patch looks good to me, thanks! I will wait for others to review the patch. -- ___ Python tracker ___

[issue28126] Py_MEMCPY: Use memcpy on Windows?

Steve Dower added the comment: > They might get a tiny bit faster on Windows, if they have used Py_MEMCPY() > for up to 16 bytes Even that's unlikely as the loop in the macro would have been unrolled in practically every case. This is about removing an unnecessary macro. Certainly no API

[issue28114] parse_envlist(): os.execve(), os.spawnve(), etc. crash in Python 3.6.0 when env contains byte strings

Changes by Eryk Sun : Added file: http://bugs.python.org/file44663/issue_28114_03.patch ___ Python tracker ___

[issue28153] [Patch] selectmodule: Make kqueue()'s event filters optional

Berker Peksag added the comment: Thanks! -- nosy: +berker.peksag resolution: -> fixed stage: -> resolved status: open -> closed type: -> behavior versions: +Python 3.7 ___ Python tracker

[issue28153] [Patch] selectmodule: Make kqueue()'s event filters optional

Roundup Robot added the comment: New changeset 57ff729e923f by Berker Peksag in branch '3.6': Issue #28153: Make kqueue()'s event filters optional https://hg.python.org/cpython/rev/57ff729e923f New changeset 6c5f9c6c25ea by Berker Peksag in branch 'default': Issue #28153: Merge from 3.6

[issue28154] Core dump after importing lxml in Python3.6b

Christian Heimes added the comment: I can't reproduce the problem with the latest checkout of Python 3.6. The crash might have been caused by #28120. Can you try again with a refresh checkout from hg.python.org? -- ___ Python tracker

[issue28154] Core dump after importing lxml in Python3.6b

Changes by Christian Heimes : -- nosy: +christian.heimes ___ Python tracker ___ ___

[issue28154] Core dump after importing lxml in Python3.6b

New submission from Filip Stefanov: fstefanov@lin-0360: ~/bin/python/vm/python3.6b/bin $ python Python 3.6.0b1 (default, Sep 14 2016, 11:15:36) [GCC 4.8.4] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import lxml as xxl *** Error in `python': free():

[issue28153] [Patch] selectmodule: Make kqueue()'s event filters optional

New submission from Ed Schouten: Just like the BSDs and Mac OS X, CloudABI (https://mail.python.org/pipermail/python-dev/2016-July/145708.html) provides support for kqueue(). Its implementation, however, is far more limited. It can only be used for polling on descriptors

[issue28135] assertRaises should return the exception in its simple form

R. David Murray added the comment: This has been proposed and rejected several times before. IMO, a strong reason to reject it is that no other assert methods return values. Consistency is important. Also note that cm survives the context manager, so you don't need that assignment

[issue28114] parse_envlist(): os.execve(), os.spawnve(), etc. crash in Python 3.6.0 when env contains byte strings

Eryk Sun added the comment: Thanks for the spawn test framework, Victor. I've added a use_bytes argument to encode the args and env using os.fsencode. It's encoding args as well because parse_arglist calls fsconvert_strdup, which was assuming Unicode strings on Windows instead of first

[issue28147] Unbounded memory growth resizing split-table dicts

Min RK added the comment: I pulled just now and saw changes in dictobject.c, and just wanted to confirm the memory growth bug is still in changeset 56294e03ad89 (I think I used the right hash, this time). -- ___ Python tracker

[issue28145] Fix whitespace in C source code

R. David Murray added the comment: A while ago Antoine fixed the leading tabs throughout the C source, after considerable debate about it. So we've been down this road before. Since I don't touch the C code often, I don't really have an opinion on this one way or the other :) --

[issue28135] assertRaises should return the exception in its simple form

Raymond Hettinger added the comment: -0 This doesn't feel Pythonic to me. -- nosy: +rhettinger ___ Python tracker ___

[issue28143] ASDL compatibility with Python 3 system interpreter

R. David Murray added the comment: It's probably not a bad thing to fix this, but you should be able to avoid the problem by using 'make touch' before building. It should not be necessary to have a running python to build python; all the build artifacts are checked in. Specifically, the

[issue23147] Possible error in _header_value_parser.py

Changes by Serhiy Storchaka : -- stage: -> test needed versions: +Python 3.6, Python 3.7 -Python 3.4 ___ Python tracker ___

[issue28147] Unbounded memory growth resizing split-table dicts

Min RK added the comment: > Ah, is the leak happen in 3.6b1? The leak happens in 3.6b1 and master as of an hour ago (git: 3c06edfe9463f1cf81bc34b702f165ad71ff79b8, hg:r103797) -- title: Memory leak in new 3.6 dictionary resize -> Unbounded memory growth resizing split-table dicts

[issue23148] Missing the charset parameter in as_encoded_word()

Changes by Serhiy Storchaka : -- stage: -> test needed versions: +Python 3.7 ___ Python tracker ___

[issue28147] Memory leak in new 3.6 dictionary resize

STINNER Victor added the comment: > According to > https://www.python.org/dev/peps/pep-0412/#split-table-dictionaries > `obj.__dict__` is always a split-table dict. Hum, this PEP is now probably outdated since Python 3.6 beta 1 :-) -- ___ Python

[issue28147] Memory leak in new 3.6 dictionary resize

Min RK added the comment: > dictresize() is called for converting split table to combined table. > How is it triggered many times? every `self.__dict__.pop` triggers a resize. According to https://www.python.org/dev/peps/pep-0412/#split-table-dictionaries `obj.__dict__` is always a

[issue28145] Fix whitespace in C source code

Mark Dickinson added the comment: It's also worth noting that "make patchcheck", which we're encouraged to use by the Python developer's guide, autofixes these whitespace issues. I find that somewhat annoying, since "make patchcheck" makes changes unrelated to the patch I'm committing, which

[issue28152] Clang warnings: code will never be executed

New submission from STINNER Victor: The issue #23545 enabled extra warnings on GCC. Clang on FreeBSD now complains about unreachable (dead) code: http://buildbot.python.org/all/builders/AMD64%20FreeBSD%20CURRENT%20Non-Debug%203.x/builds/281/steps/compile/logs/warnings%20%2814%29

[issue27599] Buffer overrun in binascii

Roundup Robot added the comment: New changeset 423ad3b14ee1 by Serhiy Storchaka in branch '3.5': Issue #27599: Fixed buffer overrun in binascii.b2a_qp() and binascii.a2b_qp(). https://hg.python.org/cpython/rev/423ad3b14ee1 New changeset fbc579ec36ab by Serhiy Storchaka in branch '2.7': Issue

[issue27599] Buffer overrun in binascii

Changes by Serhiy Storchaka : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: +Python 3.7 ___ Python tracker

[issue28145] Fix whitespace in C source code

Josh Rosenberg added the comment: Well, it's trading one person's style for the PEP7 official style, so it's not completely arbitrary. That said, I'm not sure it's justifiable to apply to the entire historic code base; my impression was that PEP7 was not intended to be applied retroactively

[issue28151] testPythonOrg() of test_robotparser fails on validating python.org HTTPS certificate

Berker Peksag added the comment: Note that I'm planning to rewrite the test to use pythontest.net. -- nosy: +berker.peksag stage: -> needs patch type: -> enhancement versions: +Python 3.6 ___ Python tracker

[issue28099] Drop Mac OS X Tiger support in Python 3.6

STINNER Victor added the comment: The "x86 Tiger 3.6" and "x86 Tiger 3.x" buildbots currently fail to compile Python: * http://buildbot.python.org/all/builders/x86%20Tiger%203.6 * http://buildbot.python.org/all/builders/x86%20Tiger%203.x -- ___

[issue28151] testPythonOrg() of test_robotparser fails on validating python.org HTTPS certificate

New submission from STINNER Victor: The "x86 Windows7 3.x" buildbot fails to validate python.org HTTPS certificate. The unit test uses the clear text HTTP URL, but http://www.python.org/robots.txt returns "301 Moved Permanently" with the new link: https://www.python.org/robots.txt Firefox

[issue28151] testPythonOrg() of test_robotparser fails on validating python.org HTTPS certificate

Changes by STINNER Victor : -- keywords: +buildbot nosy: +zach.ware ___ Python tracker ___

[issue28144] Decrease empty_keys_struct's dk_refcnt

INADA Naoki added the comment: Nice catch! -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue28151] testPythonOrg() of test_robotparser fails on validating python.org HTTPS certificate

STINNER Victor added the comment: A workaround is to catch the ssl.SSLError and skip the unit test... Another fix is to avoid completely network connection to the Internet and only uses the temporary HTTP server used by other unit tests. -- ___

[issue28125] identify cross builds by a more generic environment setting.

STINNER Victor added the comment: @Matthias Klose: I concur with Xavier, can you please behave as a professional and "keep exchanges on the bug tracker strictly on a technical level"? Personal attacks doesn't help us to contribute with you. I didn't follow the discussion, but I'm sure that we

[issue15369] pybench and test.pystone poorly documented

STINNER Victor added the comment: > I'd also like to request that you reword this dismissive line in the > performance package's readme: (...) Please report issues of the performance module on its own bug tracker: https://github.com/python/performance Can you please propose a new description?

[issue28125] identify cross builds by a more generic environment setting.

Xavier de Gaye added the comment: > please try to build extension modules with mismatching abi flags (pydebug is > the relevant one). Post your results for both mismatch cases. Hum, you are claiming that there is a problem with mismatching abi flags but don't care to explain why or to

  1   2   >