[issue30999] statistics module: add "key" keyword argument to median, mode, ...

2017-07-24 Thread Mark Dickinson

Changes by Mark Dickinson :


--
nosy: +mark.dickinson

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue30993] IDLE: Document, fix, and complete configdialog font tests

2017-07-24 Thread Terry J. Reedy

Terry J. Reedy added the comment:


New changeset 1daeb259799d0664c9453a3bd8e80411e65b52c9 by Terry Jan Reedy in 
branch '3.6':
[3.6] bpo-30993: IDLE - Improve configdialog font page and tests. (GH-2831) 
(#2834)
https://github.com/python/cpython/commit/1daeb259799d0664c9453a3bd8e80411e65b52c9


--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue30993] IDLE: Document, fix, and complete configdialog font tests

2017-07-24 Thread Terry J. Reedy

Changes by Terry J. Reedy :


--
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue31001] IDLE: Add tests for configdialog highlight tab

2017-07-24 Thread Terry J. Reedy

Changes by Terry J. Reedy :


--
assignee: terry.reedy
components: IDLE
nosy: terry.reedy
priority: normal
severity: normal
stage: needs patch
status: open
title: IDLE: Add tests for configdialog highlight tab
type: enhancement
versions: Python 3.6, Python 3.7

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue31002] IDLE: Add tests for configdialog keys tab

2017-07-24 Thread Terry J. Reedy

Changes by Terry J. Reedy :


--
assignee: terry.reedy
components: IDLE
nosy: terry.reedy
priority: normal
severity: normal
stage: needs patch
status: open
title: IDLE: Add tests for configdialog keys tab
type: enhancement
versions: Python 3.6, Python 3.7

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue31003] IDLE: Add tests for help sources on configdialog general tab

2017-07-24 Thread Terry J. Reedy

Changes by Terry J. Reedy :


--
assignee: terry.reedy
components: IDLE
nosy: terry.reedy
priority: normal
severity: normal
stage: needs patch
status: open
title: IDLE: Add tests for help sources on configdialog general tab
type: enhancement
versions: Python 3.6, Python 3.7

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue29572] Upgrade installers to OpenSSL 1.0.2k

2017-07-24 Thread Ned Deily

Changes by Ned Deily :


--
pull_requests: +2882

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue29572] Upgrade installers to OpenSSL 1.0.2k

2017-07-24 Thread Ned Deily

Changes by Ned Deily :


--
pull_requests: +2883

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue29572] Upgrade installers to OpenSSL 1.0.2k

2017-07-24 Thread Ned Deily

Ned Deily added the comment:


New changeset 002f778ecab98f4725a08f35d68f78559a13e47a by Ned Deily in branch 
'3.5':
bpo-29572: Update macOS installer build to OpenSSL 1.0.2k (#457) (#2835)
https://github.com/python/cpython/commit/002f778ecab98f4725a08f35d68f78559a13e47a


--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue29572] Upgrade installers to OpenSSL 1.0.2k

2017-07-24 Thread Ned Deily

Ned Deily added the comment:


New changeset 8d41de62b9e21090c3a1ccb951ba7034a2b74180 by Ned Deily in branch 
'2.7':
bpo-29572: Update macOS installer build to OpenSSL 1.0.2k (#457) (#2836)
https://github.com/python/cpython/commit/8d41de62b9e21090c3a1ccb951ba7034a2b74180


--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue31004] IDLE, configdialog: Factor out FontTab class from ConfigDialog

2017-07-24 Thread Terry J. Reedy

New submission from Terry J. Reedy:

I want to follow the safe way to refactor (from a blog post), rather than the 
hacker way of refactoring 'in place'.
Step 0: Test code to be refactored.  Finished in 30993.

Step 1: Copy code to be refactored and modify as needed to isolate it from the 
working original.  For configdialog, add 'class FontPage' below ConfigDialog 
and copy font/tab methods, now collected together, below that.  For the test, 
copy class FontTest as FontPageTest and IndentTest as IndentOptionTest. The 
copies should pass as they will still be testing the original code.  Commit.

Step 2: Modify code as desired.  Modify test copy to test code copy.  For 
FontPage, this will require new tracer manager (#30853) to attach (activate) 
callbacks so tests will pass.  Commit.

Step 3: Switch from using original code to using modified code.  For this 
issue, calling FontPage instead of create_page_font_tab may be enough.  Skip 
original test; modify new test as needed to pass.  Commit.

Step 4: Once we are sure that we do not need the original code that has been 
replaced, delete it.  Rerun tests. Commit.

The separate commits will make review easier.  Create or update PRs as desired.

--
assignee: terry.reedy
components: IDLE
messages: 298933
nosy: terry.reedy
priority: normal
severity: normal
stage: needs patch
status: open
title: IDLE, configdialog: Factor out FontTab class from ConfigDialog
type: enhancement
versions: Python 3.6, Python 3.7

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue29572] Upgrade installers to OpenSSL 1.0.2k

2017-07-24 Thread Ned Deily

Changes by Ned Deily :


--
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue30780] IDLE: configdialog - add tests for ConfigDialog GUI.

2017-07-24 Thread Terry J. Reedy

Changes by Terry J. Reedy :


--
dependencies: +IDLE: Add tests for configdialog highlight tab, IDLE: Add tests 
for configdialog keys tab, IDLE: Add tests for help sources on configdialog 
general tab

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue17611] Move unwinding of stack for "pseudo exceptions" from interpreter to compiler.

2017-07-24 Thread Antoine Pitrou

Antoine Pitrou added the comment:

So, the approach of duplicating finally blocks tends to lead to a non-trivial 
bytecode increase.  There is even a potential combinatorial explosion with 
nested "try..finally" block:

def f():
try:
...
finally:
try:
...
finally:
# etc.

Such a chain of N nested "finally"s will emit O(2**N) opcodes.

I'm not sure it's a pratical concern but I find it is detrimental to the 
readibility of bytecode (which is a nice thing to have when doing low-level 
debugging or tweaking).  I think we can massage the PR to remove the "finally" 
block duplication while keeping the predictable stack effect.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue17611] Move unwinding of stack for "pseudo exceptions" from interpreter to compiler.

2017-07-24 Thread Antoine Pitrou

Antoine Pitrou added the comment:

For example we could generate the following bytecode:

SETUP_FINALLY L1
// ... stmt1
POP_BLOCK
JUMP_FINALLY  L1
L1:
// ... stmt2
RERAISE
JUMP_FORWARD  L2
L2:


JUMP_FINALLY would push 3 Nones on the stack.  RERAISE would raise only if 
non-None values are popped.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue30939] Sphinx 1.6.3 deprecation warning for sphinx.util.compat.Directive in docs builds

2017-07-24 Thread Ned Deily

Changes by Ned Deily :


--
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue31005] caught and stored exception creates a reference cycle outside its traceback

2017-07-24 Thread Vojtěch Fried

New submission from Vojtěch Fried:

I have this test case:

import gc
import sys
import traceback

def hold_world():
try:
raise Exception("test1")
except Exception as exc:
print("exc caught in frame: ", exc.__traceback__.tb_frame)
assert not exc.__traceback__.tb_next
#exc.__traceback__ = None #ok
tmp = exc
traceback.clear_frames(exc.__traceback__) #not enough

def use_obj( o ):
hold_world()
#o = None #needed to get rid of the reference in the frame

def main():
o = ["survivor"]
print(gc.get_referrers(o))
print(sys.getrefcount(o)) #2
use_obj( o )
print(gc.get_referrers(o))
print(sys.getrefcount(o)) #3
#o = None #needed to get rid of the reference in the frame

if __name__ == '__main__':
main()

The outpus is:
[]
2
exc caught in frame:  
[, ]
3

When either uncommenting the line "exc.__traceback__ = None" or uncommenting "o 
= None" lines, the output is like
[]
2
exc caught in frame:  
[]
2

It seems that "hold_world" function somehow manages to (indirectly) add a 
reference to "o" object. So "o" is not cleared at "main" end, but rather 
garbage collected.
Even though there is a reference cycle tmp -> traceback -> frame -> tmp, the 
frames outside "hold_world" should not be affected, but it looks like they are.

--
components: Interpreter Core
messages: 298936
nosy: vojtechfried
priority: normal
severity: normal
status: open
title: caught and stored exception creates a reference cycle outside its 
traceback
type: behavior
versions: Python 3.6

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue31006] typing.NamedTuple should add annotations to its constructor (__new__) parameters.

2017-07-24 Thread Antony Lee

New submission from Antony Lee:

Currently, the fields, types and defaults used to define a typing.NamedTuple 
need to be retrieved from three different attributes: `_fields`, 
`_field_types`, and `_field_defaults` (the first two are combined in 
`__annotations__`, but that still misses the defaults).

However, there is a place where all this information can be naturally combined: 
in the Signature of the constructor (as returned by `inspect.signature(cls)`).  
Currently, the Parameter objects in the signature have the information about 
the parameter names and defaults, but their annotation is not set.

Thus, I would like to propose setting the annotation of the Parameters in the 
Signature object as well.

--
components: Library (Lib)
messages: 298937
nosy: Antony.Lee
priority: normal
severity: normal
status: open
title: typing.NamedTuple should add annotations to its constructor (__new__) 
parameters.
versions: Python 3.6

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue31007] ERROR: test_pipe_handle (test.test_asyncio.test_windows_utils.PipeTests) expected ERROR_INVALID_HANDLE on x86 Windows7 3.x

2017-07-24 Thread STINNER Victor

New submission from STINNER Victor:

http://buildbot.python.org/all/builders/x86%20Windows7%203.x/builds/905/steps/test/logs/stdio

...
test_wait_for_handle (test.test_asyncio.test_windows_events.ProactorTests) ... 
ok
test_wait_for_handle_cancel 
(test.test_asyncio.test_windows_events.ProactorTests) ... ok
test_pipe_handle (test.test_asyncio.test_windows_utils.PipeTests) ... ERROR
test_pipe_overlapped (test.test_asyncio.test_windows_utils.PipeTests) ... ok
test_popen (test.test_asyncio.test_windows_utils.PopenTests) ... ok
...
==
ERROR: test_pipe_handle (test.test_asyncio.test_windows_utils.PipeTests)
--
Traceback (most recent call last):
  File 
"D:\cygwin\home\db3l\buildarea\3.x.bolen-windows7\build\lib\test\test_asyncio\test_windows_utils.py",
 line 128, in test_pipe_handle
raise RuntimeError('expected ERROR_INVALID_HANDLE')
RuntimeError: expected ERROR_INVALID_HANDLE

--
components: Tests, Windows, asyncio
keywords: buildbot
messages: 298938
nosy: haypo, paul.moore, steve.dower, tim.golden, yselivanov, zach.ware
priority: normal
severity: normal
status: open
title: ERROR: test_pipe_handle (test.test_asyncio.test_windows_utils.PipeTests) 
expected ERROR_INVALID_HANDLE on x86 Windows7 3.x
versions: Python 3.7

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue31008] FAIL: test_wait_for_handle (test.test_asyncio.test_windows_events.ProactorTests) on x86 Windows7 3.x

2017-07-24 Thread STINNER Victor

New submission from STINNER Victor:

http://buildbot.python.org/all/builders/x86%20Windows7%203.x/builds/905/steps/test/logs/stdio

...
test_double_bind (test.test_asyncio.test_windows_events.ProactorTests) ... ok
test_pipe (test.test_asyncio.test_windows_events.ProactorTests) ... ok
test_wait_for_handle (test.test_asyncio.test_windows_events.ProactorTests) ... 
FAIL
test_wait_for_handle_cancel 
(test.test_asyncio.test_windows_events.ProactorTests) ... ok
test_pipe_handle (test.test_asyncio.test_windows_utils.PipeTests) ... ok
...
==
FAIL: test_wait_for_handle (test.test_asyncio.test_windows_events.ProactorTests)
--
Traceback (most recent call last):
  File 
"D:\cygwin\home\db3l\buildarea\3.x.bolen-windows7\build\lib\test\test_asyncio\test_windows_events.py",
 line 121, in test_wait_for_handle
self.assertTrue(0.48 < elapsed < 0.9, elapsed)
AssertionError: False is not true : 0.45627471

--
components: Tests, Windows, asyncio
keywords: buildbot
messages: 298939
nosy: haypo, paul.moore, steve.dower, tim.golden, yselivanov, zach.ware
priority: normal
severity: normal
status: open
title: FAIL: test_wait_for_handle 
(test.test_asyncio.test_windows_events.ProactorTests) on x86 Windows7 3.x
versions: Python 3.7

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue30867] Add macro `HAVE_OPENSSL_VERIFY_PARAM` to avoid invalid function declaration

2017-07-24 Thread signal1587

Changes by signal1587 :


--
title: Add necessary macro that insure `HAVE_OPENSSL_VERIFY_PARAM` to avoid 
invalid function declaration -> Add macro `HAVE_OPENSSL_VERIFY_PARAM` to avoid 
invalid function declaration

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue31009] test_multiprocessing_spawn hangs randomly on AMD64 Windows10 3.x

2017-07-24 Thread STINNER Victor

New submission from STINNER Victor:

Same question as usual: why regrtest doesn't display the "running: 
test_multiprocessing_spawn (319 sec)" update every 30 seconds? Is regrtest main 
process also stuck?

http://buildbot.python.org/all/builders/AMD64%20Windows10%203.x/builds/973/steps/test/logs/stdio

...
Run tests in parallel using 2 child processes
...
0:47:28 [403/406] test_buffer passed (119 sec) -- running: 
test_multiprocessing_spawn (319 sec)
0:47:30 [404/406] test_turtle passed -- running: test_multiprocessing_spawn 
(321 sec)
0:47:32 [405/406] test_dynamic passed -- running: test_multiprocessing_spawn 
(323 sec)

command timed out: 1200 seconds without output running 
['Tools\\buildbot\\test.bat', '-x64', '-j2', '--timeout', '900'], attempting to 
kill
program finished with exit code 1
elapsedTime=4059.302000

--
components: Tests
keywords: buildbot
messages: 298940
nosy: davin, haypo, pitrou
priority: normal
severity: normal
status: open
title: test_multiprocessing_spawn hangs randomly on AMD64 Windows10 3.x
versions: Python 3.7

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue31009] test_multiprocessing_spawn hangs randomly on AMD64 Windows10 3.x and AMD64 Windows8 3.x

2017-07-24 Thread STINNER Victor

STINNER Victor added the comment:

Same bug on AMD64 Windows8 3.x buildbot:

http://buildbot.python.org/all/builders/AMD64%20Windows8%203.x/builds/943/steps/test/logs/stdio

Run tests in parallel using 2 child processes
...
1:03:06 [402/406] test_getargs2 passed -- running: test_multiprocessing_spawn 
(1203 sec)
1:03:09 [403/406] test_threadedtempfile passed -- running: 
test_multiprocessing_spawn (1205 sec)
1:03:11 [404/406] test_slice passed -- running: test_multiprocessing_spawn 
(1208 sec)
1:03:19 [405/406] test_tracemalloc passed -- running: 
test_multiprocessing_spawn (1215 sec)

command timed out: 1200 seconds without output running 
['Tools\\buildbot\\test.bat', '-x64', '-j2', '--timeout', '900'], attempting to 
kill
program finished with exit code 1
elapsedTime=5005.881000

--
title: test_multiprocessing_spawn hangs randomly on AMD64 Windows10 3.x -> 
test_multiprocessing_spawn hangs randomly on AMD64 Windows10 3.x and AMD64 
Windows8 3.x

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue31010] test_socketserver.test_ForkingTCPServer(): threading_cleanup() and reap_children() warnings on AMD64 FreeBSD 10.x Shared 3.x

2017-07-24 Thread STINNER Victor

New submission from STINNER Victor:

http://buildbot.python.org/all/builders/AMD64%20FreeBSD%2010.x%20Shared%203.x/builds/607/steps/test/logs/stdio

test_ForkingTCPServer (test.test_socketserver.SocketServerTest) ... creating 
server
ADDR = ('127.0.0.1', 42116)
CLASS = 
server running
test client 0
test client 1
test client 2
waiting for server
done
Warning -- threading_cleanup() failed to cleanup -1 threads after 4 sec (count: 
0, dangling: 1)
Warning -- reap_children() reaped child process 83130
ok
...
1 test altered the execution environment:
test_socketserver
...
Total duration: 11 min 56 sec
Tests result: ENV CHANGED
*** Error code 3

--
components: Tests
keywords: buildbot
messages: 298942
nosy: haypo
priority: normal
severity: normal
status: open
title: test_socketserver.test_ForkingTCPServer(): threading_cleanup() and 
reap_children() warnings on AMD64 FreeBSD 10.x Shared 3.x
type: resource usage
versions: Python 3.7

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue17611] Move unwinding of stack for "pseudo exceptions" from interpreter to compiler.

2017-07-24 Thread Antoine Pitrou

Antoine Pitrou added the comment:

Ok, I've pushed an update with removes the finally block duplication.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue30714] test_ssl fails with openssl 1.1.0f: test_alpn_protocols()

2017-07-24 Thread STINNER Victor

Changes by STINNER Victor :


--
title: test_ssl fails with openssl 1.1.0f -> test_ssl fails with openssl 
1.1.0f: test_alpn_protocols()

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue30714] test_ssl fails with openssl 1.1.0f: test_alpn_protocols()

2017-07-24 Thread STINNER Victor

STINNER Victor added the comment:

Test still fails. Failure on AMD64 Debian PGO 2.7:

http://buildbot.python.org/all/builders/AMD64%20Debian%20PGO%202.7/builds/243/steps/test/logs/stdio

==
FAIL: test_alpn_protocols (test.test_ssl.ThreadedTests)
--
Traceback (most recent call last):
  File 
"/var/lib/buildbot/slaves/enable-optimizations-bot/2.7.gps-debian-profile-opt.nondebug/build/Lib/test/test_ssl.py",
 line 2971, in test_alpn_protocols
self.assertIsInstance(stats, ssl.SSLError)
AssertionError: {'compression': None, 'client_npn_protocol': None, 'cipher': 
('ECDHE-RSA-AES256-GCM-SHA384', 'TLSv1.2', 256), 'peercert': {}, 
'server_npn_protocols': [None], 'client_alpn_protocol': None, 'version': 
u'TLSv1.2', 'server_alpn_protocols': [None]} is not an instance of 

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue30850] [2.7] bsddb3: test01_basic_replication() of test_bsddb3 fails randomly on AMD64 Windows8.1 Refleaks 2.7

2017-07-24 Thread STINNER Victor

STINNER Victor added the comment:

x86 Windows XP 2.7:

http://buildbot.python.org/all/builders/x86%20Windows%20XP%202.7/builds/240/steps/test/logs/stdio

==
FAIL: test04_lock_timeout2 (bsddb.test.test_lock.LockingTestCase)
--
Traceback (most recent call last):
  File 
"d:\cygwin\home\db3l\buildarea\2.7.bolen-windows\build\lib\bsddb\test\test_lock.py",
 line 132, in test04_lock_timeout2
self.assertGreaterEqual(end_time-start_time, 0.0999)
AssertionError: 0.0588773803711 not greater than or equal to 0.0999

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue30850] [2.7] bsddb3: test01_basic_replication() of test_bsddb3 fails randomly on AMD64 Windows8.1 Refleaks 2.7

2017-07-24 Thread STINNER Victor

Changes by STINNER Victor :


--
pull_requests: +2884

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue30850] [2.7] bsddb3: test01_basic_replication() of test_bsddb3 fails randomly on AMD64 Windows8.1 Refleaks 2.7

2017-07-24 Thread STINNER Victor

STINNER Victor added the comment:

I wrote https://github.com/python/cpython/pull/2840 to tolerate only 50 ms on 
Windows, whereas 100 ms are expected (the test expects 99 ms or greater).

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue30998] faulthandler: Show C stacktrace

2017-07-24 Thread STINNER Victor

STINNER Victor added the comment:

> While faulthandler's output is already quite useful when dealing with crashes 
> in C libraries, it'd be much more useful when it could also show a low-level 
> C/C++ stack.

It's a deliberate choice to not read the "C" backtrace: it requires complex 
non-portable libraries. faulthandler has a "simple" design, but the 
implementation is non trivial especially because it is designed to be 
async-signal-safe (no malloc, no printf, no lock, etc.).

faulthandler design is to read global Python internal structures and dumps them 
on stderr. The code is as portable as Python is: faulthandler works on all 
platforms! There are only tiny limitations on Windows on 
faulthandler.register(), but IMHO the main usage of faulthandler is to dump 
Python tracebacks on a crash and that works on Windows as well. By the way, I 
recently added support to Windows exceptions, so it uses better Windows native 
APIs.

You *can* write a Python module which depends on a specific library and only 
works on a limited set of platforms. But such module belongs to PyPI, I 
consider that it shouldn't be part of the Python stdlib. Usually, Python avoids 
dependencies whenever possible. Again, to get the maximum portability.


> As much as I like this idea I don't think implementing is going to be 
> possible and this is one of the points where you just have to attach a 
> debugger like gdb for good information.

While it's "nice" to have a "C" traceback, I also prefer to get a debugger like 
gdb to inspect more data: variables, registers, threads, etc.


> Maybe it would be useful to have an option to say always generate a core 
> dump? Something like the stuff listed here: 
> https://stackoverflow.com/questions/979141/how-to-programmatically-cause-a-core-dump-in-c-c

10 years ago, it was common to dump cores in the current directory. Nowadays, 
operating systems provide a program which collects core dumps, send them to a 
server to get a reliable stacktrace, automatically open a bug report, etc. 
Getting a core dump requires to configure your operating system.

I'm not a big fan of coredump. Coredumps are not portable at all. Don't try to 
open a Ubuntu coredump on Fedora. I wouldn't even try to open a Fedora 25 
coredump on Fedora 26.

On Linux, changing how where and how coredumps are written requires to be a 
root user. You may want to support coredumpctl, etc.

Again, it's a complex task and it's hard to get a portable behaviour.

If someone is interested to get this feature, please create a small project on 
PyPI. Come back later when you get enough user feedback and supports enough 
platforms to consider that it can be added to Python stdlib.

--
resolution: wont fix -> rejected
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue30758] test_pydoc hangs sometimes on 3.6 and master branches on ARMv7 Ubuntu 3.x

2017-07-24 Thread STINNER Victor

Changes by STINNER Victor :


--
title: test_pydoc hangs sometimes on 3.6 and master branches -> test_pydoc 
hangs sometimes on 3.6 and master branches on ARMv7 Ubuntu 3.x

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue30758] test_pydoc hangs sometimes on 3.6 and master branches on ARMv7 Ubuntu 3.x

2017-07-24 Thread STINNER Victor

STINNER Victor added the comment:

It seems like test_pydoc only hangs on ARMv7 Ubuntu 3.x. Why faulthandler 
doesn't dump a traceback? :-(

faulthandler is supposed to dump a traceback after 900 seconds. Here, regrtest 
was killed after 1200 seconds and test_pydoc was already running for 423 
seconds.

http://buildbot.python.org/all/builders/ARMv7%20Ubuntu%203.x/builds/1094/steps/test/logs/stdio

./python  ./Tools/scripts/run_tests.py -j 1 -u all -W --slowest 
--fail-env-changed --timeout=900 -j2 -j8
...
0:10:28 load avg: 6.21 [403/406] test_venv passed (34 sec) -- running: 
test_pydoc (400 sec), test_pickle (47 sec), test_tools (338 sec)
0:10:32 load avg: 5.95 [404/406] test_pickle passed (51 sec) -- running: 
test_pydoc (405 sec), test_tools (343 sec)
0:10:51 load avg: 4.83 [405/406] test_tools passed (361 sec) -- running: 
test_pydoc (423 sec)

command timed out: 1200 seconds without output running ['make', 'buildbottest', 
'TESTOPTS=-j2 -j8', 'TESTPYTHONOPTS=', 'TESTTIMEOUT=900'], attempting to kill
process killed by signal 9
program finished with exit code -1

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue17611] Move unwinding of stack for "pseudo exceptions" from interpreter to compiler.

2017-07-24 Thread Serhiy Storchaka

Serhiy Storchaka added the comment:

Great! I tried to update the patch myself, but there were too much conflicts. 
Thank you very much Antoine for taking this!

Seems there are bugs in frame_setlineno() related to code duplications. And 
deduplicating the 'finally' blocks doesn't solve all of them. See comments on 
GitHub.

I don't like the new END_ITER instruction. This complicates (and slows down) 
the evaluation loop and the peepholer. This also adds a limitation on the 
peepholer (END_ITER can't be optimized out). We can use other way for 
determaining the end of the 'for' block. The argument of the FOR_ITER 
instruction points to the end of the 'for' block. Just scan all addresses from 
0 to max_addr and count all FOR_ITER instructions and their targets in the 
range between min_addr and max_addr.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue17611] Move unwinding of stack for "pseudo exceptions" from interpreter to compiler.

2017-07-24 Thread STINNER Victor

Changes by STINNER Victor :


--
nosy:  -haypo

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue30876] SystemError on importing module from unloaded package

2017-07-24 Thread Ned Deily

Ned Deily added the comment:

When running tests from installed location, test_import now fails on master, 
3.6, and 3.5 (including v3.5.4rc1) with:

==
ERROR: test_import_from_unloaded_package (test.test_import.RelativeImportTests)
--
Traceback (most recent call last):
  File 
"/Users/nad/Projects/PyDev/active/dev/3x/root/uxd/lib/python3.7/test/test_import/__init__.py",
 line 704, in test_import_from_unloaded_package
import package2.submodule1
ModuleNotFoundError: No module named 'package2'

--
nosy: +ned.deily

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue30814] Import dotted name as alias breaks with concurrency

2017-07-24 Thread Ned Deily

Ned Deily added the comment:

When running tests from installed location, test_import now fails on master and 
3.6 with:

==
ERROR: test_concurrency (test.test_import.ImportTests)
--
Traceback (most recent call last):
  File 
"/Users/nad/Projects/PyDev/active/dev/3x/root/uxd/lib/python3.7/test/test_import/__init__.py",
 line 408, in test_concurrency
raise exc
  File 
"/Users/nad/Projects/PyDev/active/dev/3x/root/uxd/lib/python3.7/test/test_import/__init__.py",
 line 393, in run
import package
ModuleNotFoundError: No module named 'package'

--
nosy: +ned.deily

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue26762] test_multiprocessing_spawn leaves processes running in background

2017-07-24 Thread STINNER Victor

Changes by STINNER Victor :


--
pull_requests: +2885

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue26762] test_multiprocessing_spawn leaves processes running in background

2017-07-24 Thread STINNER Victor

STINNER Victor added the comment:

I'm not sure that the issue is really fixed. I applied my msg263461 patch and I 
still see the list of "python" processes growing but then also a little bit 
decreasing, and some zombi  processes.

The problem is that it's hard to guess if a growing "ps" list is a bug or not, 
since we only cleanup things in tearDownClass(), not in tearDown(). So it's ok 
to keep some child processes between two unit tests.

I wrote a first change to help debugging the issue. My change adds more 
warnings and calls support.reap_children():
https://github.com/python/cpython/pull/2841

With this PR, the following test fails:
---
haypo@selma$ ./python -u -m test -v --fail-env-changed 
--match=test.test_multiprocessing_spawn.WithThreadsTestPool.test_release_task_refs
 --match=test.test_multiprocessing_spawn.WithProcessesTestLogging.test_level 
test_multiprocessing_spawn 
== CPython 3.7.0a0 (heads/master:b364d9f, Jul 24 2017, 11:06:33) [GCC 6.3.1 
20161221 (Red Hat 6.3.1-1)]
== Linux-4.11.9-200.fc25.x86_64-x86_64-with-fedora-25-Twenty_Five little-endian
== hash algorithm: siphash24 64bit
== cwd: /home/haypo/prog/python/master/build/test_python_24433
== CPU count: 4
== encodings: locale=UTF-8, FS=utf-8
Testing with flags: sys.flags(debug=0, inspect=0, interactive=0, optimize=0, 
dont_write_bytecode=0, no_user_site=0, no_site=0, ignore_environment=0, 
verbose=0, bytes_warning=0, quiet=0, hash_randomization=1, isolated=0)
Run tests sequentially
0:00:00 load avg: 0.27 [1/1] test_multiprocessing_spawn
test_level (test.test_multiprocessing_spawn.WithProcessesTestLogging) ... ok
Warning -- reap_children() reaped child process 24437
test_release_task_refs (test.test_multiprocessing_spawn.WithThreadsTestPool) 
... ok
Warning -- reap_children() reaped child process 24438
Dangling processes: {, }

--
Ran 2 tests in 1.369s

OK
Warning -- multiprocessing.process._dangling was modified by 
test_multiprocessing_spawn
  Before: <_weakrefset.WeakSet object at 0x7fdc24f70058>
  After:  <_weakrefset.WeakSet object at 0x7fdc2a666260> 
test_multiprocessing_spawn failed (env changed)

1 test altered the execution environment:
test_multiprocessing_spawn

Total duration: 2 sec
Tests result: ENV CHANGED
---

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue27584] New addition of vSockets to the python socket module

2017-07-24 Thread Cathy Avery

Cathy Avery added the comment:

There is an outstanding review on my pull request at 
https://github.com/python/cpython/pull/2489 as there is an red X at changes 
requested by kushaldas and I believe I have made the necessary changes. 

Again please let me know if there is anything that I need to do as I am new to 
this process.

Thanks,

Cathy

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue26762] test_multiprocessing_spawn leaves processes running in background

2017-07-24 Thread STINNER Victor

Changes by STINNER Victor :


--
pull_requests: +2886

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue26762] test_multiprocessing_spawn leaves processes running in background

2017-07-24 Thread STINNER Victor

STINNER Victor added the comment:

> With this PR, the following test fails:

Ah, it seems like test_level() alone is enough to reproduce the bug and the 
following PR fixes it:
https://github.com/python/cpython/pull/2842

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue26762] test_multiprocessing_spawn leaves processes running in background

2017-07-24 Thread STINNER Victor

STINNER Victor added the comment:

With PR 2841 + PR 2842, there is still at least one test which leaks processes:

---
$ ./python -m test --match=test_notify_all -v test_multiprocessing_spawn
== CPython 3.7.0a0 (heads/master:b364d9f, Jul 24 2017, 11:06:33) [GCC 6.3.1 
20161221 (Red Hat 6.3.1-1)]
== Linux-4.11.9-200.fc25.x86_64-x86_64-with-fedora-25-Twenty_Five little-endian
== hash algorithm: siphash24 64bit
== cwd: /home/haypo/prog/python/master/build/test_python_28469
== CPU count: 4
== encodings: locale=UTF-8, FS=utf-8
Testing with flags: sys.flags(debug=0, inspect=0, interactive=0, optimize=0, 
dont_write_bytecode=0, no_user_site=0, no_site=0, ignore_environment=0, 
verbose=0, bytes_warning=0, quiet=0, hash_randomization=1, isolated=0)
Run tests sequentially
0:00:00 load avg: 0.44 [1/1] test_multiprocessing_spawn
test_notify_all (test.test_multiprocessing_spawn.WithManagerTestCondition) ... 
ok
test_notify_all (test.test_multiprocessing_spawn.WithProcessesTestCondition) 
... ok
Warning -- reap_children() reaped child process 28553
Warning -- reap_children() reaped child process 28557
Warning -- reap_children() reaped child process 28559
Warning -- reap_children() reaped child process 28561
test_notify_all (test.test_multiprocessing_spawn.WithThreadsTestCondition) ... 
ok
Dangling processes: {, 
, , 
}

--
Ran 3 tests in 3.772s

OK
Warning -- multiprocessing.process._dangling was modified by 
test_multiprocessing_spawn
  Before: <_weakrefset.WeakSet object at 0x7f2385200400>
  After:  <_weakrefset.WeakSet object at 0x7f238a8ff260> 
test_multiprocessing_spawn failed (env changed)

1 test altered the execution environment:
test_multiprocessing_spawn

Total duration: 4 sec
Tests result: SUCCESS
---

I looked at the code of the test: it's full of "p.daemon = True" and "t.daemon 
= True", whereas these processes and threads are not tracked in a list to be 
cleared manually, so I'm not surprised of the warnings.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue30516] Documentation for datetime substract operation incorrect?

2017-07-24 Thread Berker Peksag

Changes by Berker Peksag :


--
nosy: +belopolsky

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue30850] [2.7] bsddb3: test01_basic_replication() of test_bsddb3 fails randomly on AMD64 Windows8.1 Refleaks 2.7

2017-07-24 Thread STINNER Victor

STINNER Victor added the comment:


New changeset 0fc940a09ae6636e78f94ecf6436b8de14bd1c45 by Victor Stinner in 
branch '2.7':
test_bsddb3 tolerates smaller timeout on Windows (#2840)
https://github.com/python/cpython/commit/0fc940a09ae6636e78f94ecf6436b8de14bd1c45


--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue26762] test_multiprocessing_spawn leaves processes running in background

2017-07-24 Thread STINNER Victor

STINNER Victor added the comment:


New changeset 06634950c553f8df83330ed468c11483b857b7dc by Victor Stinner in 
branch 'master':
bpo-26762: Avoid daemon process in _test_multiprocessing (#2842)
https://github.com/python/cpython/commit/06634950c553f8df83330ed468c11483b857b7dc


--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue30814] Import dotted name as alias breaks with concurrency

2017-07-24 Thread STINNER Victor

STINNER Victor added the comment:

> When running tests from installed location, test_import now fails on master 
> and 3.6 with:

Which Git revisions are you testing? On master, do you have my latest commit 
e72b1359f81d1dd42bd8a5c5cc2b3928b74f8023 ?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue26762] test_multiprocessing_spawn leaves processes running in background

2017-07-24 Thread STINNER Victor

STINNER Victor added the comment:

If you want to use --fail-env-changed with PR 2841, for example to use 
test.bisect, you may want this extra patch:

diff --git a/Lib/test/_test_multiprocessing.py 
b/Lib/test/_test_multiprocessing.py
index f2342c3..5f9e5c3 100644
--- a/Lib/test/_test_multiprocessing.py
+++ b/Lib/test/_test_multiprocessing.py
@@ -4352,6 +4352,7 @@ class ManagerMixin(object):
   "children after %s seconds"
   % (multiprocessing.active_children(), dt),
   file=sys.stderr)
+test.support.environment_altered = True
 break
 
 gc.collect()   # do garbage collection
@@ -4359,6 +4360,7 @@ class ManagerMixin(object):
 # This is not really an error since some tests do not
 # ensure that all processes which hold a reference to a
 # managed object have been joined.
+test.support.environment_altered = True
 print('Warning -- Shared objects which still exist at manager '
   'shutdown:')
 print(cls.manager._debug_info())

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue17611] Move unwinding of stack for "pseudo exceptions" from interpreter to compiler.

2017-07-24 Thread Antoine Pitrou

Antoine Pitrou added the comment:

> I don't like the new END_ITER instruction. This complicates (and slows down) 
> the evaluation loop and the peepholer.

I don't think it slows down anything in the eval loop.  I agree it adds a bit 
of complexity.

> This also adds a limitation on the peepholer (END_ITER can't be optimized 
> out).

It's an unconditional backedge, how could you optimize it?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue31005] caught and stored exception creates a reference cycle outside its traceback

2017-07-24 Thread Mark Dickinson

Mark Dickinson added the comment:

It's the f_back reference from the inner frame that's keeping the outer frame 
alive.

Here's a picture of the create garbage: http://imgur.com/a/OCRe3

And here's the script that created it:


import gc
import refcycle
import sys
import traceback

def hold_world():
try:
raise Exception("test1")
except Exception as exc:
tmp = exc

def use_obj( o ):
hold_world()

def main():
gc.disable()
gc.collect()
o = ["survivor"]
use_obj( o )
garbage = refcycle.garbage()
garbage.export_image()


if __name__ == '__main__':
main()

--
nosy: +mark.dickinson

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue31005] caught and stored exception creates a reference cycle outside its traceback

2017-07-24 Thread Mark Dickinson

Mark Dickinson added the comment:

BTW, I don't think that this counts as a Python bug: Python is behaving as 
designed here. Not closing just yet, though: it may be that there's an 
opportunity for improved documentation, or a wider discussion on how to solve 
such issues in general.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue30516] Documentation for datetime substract operation incorrect?

2017-07-24 Thread Alexander Belopolsky

Alexander Belopolsky added the comment:

I agree.  The documentation can be improved here.  The note about x - y not 
being quite the same as x + (-y) belongs to the timedelta - timedelta 
operation. It should be removed from both date - timedelta and 
datetime-timedelta footnotes.

--
assignee:  -> docs@python
components: +Documentation
nosy: +docs@python
stage:  -> needs patch
versions: +Python 3.7

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue31011] Users (except from the one who installed) not able to see python in add remove programs.

2017-07-24 Thread Debarshi Goswami

New submission from Debarshi Goswami:

When Python (64 bit) is installed for all users from an admin account on 
Windows, it gets installed correctly for all users , but it does not appear in 
add remove program for users other than one who installed it.


Command used : python-3.6.1-amd64.exe /quiet InstallAllUsers=1 PrependPath=1 
TargetDir=C:\apps\Python36

Work around: Repair the installation by launching Python installer again.

--
components: Installation
messages: 298965
nosy: Debarshi.Goswami
priority: normal
severity: normal
status: open
title: Users (except from the one who installed) not  able to see python in add 
remove programs.
type: behavior
versions: Python 3.6

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue31005] caught and stored exception creates a reference cycle outside its traceback

2017-07-24 Thread Vojtěch Fried

Vojtěch Fried added the comment:

Ok. As an input for a potential discussion:

Should all cases in the std library that store an exception be reported as a 
bug (because it can potentially mess with reference counting?) One such case is 
function create_connection in socket.py.

If "hold_world" is a function in an external code and the reference cycle 
problem only appears in an exceptional case it is hard to debug and it can 
hardly be easily fixed.

If "hold_world" is in an external code, it may be impossible to deal with. You 
can only diligently set to None or del in each function on the stack. But if 
you have a factory function that actually produces an object you don't want to 
be garbage collected, you can't set the reference to None before returning it.

It is surprising that the object is affected by a function that does not know 
about it. It is not stored globally, it is not passed to it. It just happens to 
be at a wrong time at a wrong place.

Should traceback.clear_frames clear the "back referenced" frames?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue31011] Users (except from the one who installed) not able to see python in add remove programs.

2017-07-24 Thread Debarshi Goswami

Changes by Debarshi Goswami :


--
nosy: +manddy221

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue30188] test_nntplib: random EOFError in setUpClass()

2017-07-24 Thread STINNER Victor

STINNER Victor added the comment:

Similar but different error (ssl.SSLEOFError) on AMD64 FreeBSD CURRENT 
Non-Debug 3.5:

http://buildbot.python.org/all/builders/AMD64%20FreeBSD%20CURRENT%20Non-Debug%203.5/builds/211/steps/test/logs/stdio

==
ERROR: setUpClass (test.test_nntplib.NetworkedNNTP_SSLTests)
--
Traceback (most recent call last):
  File 
"/usr/home/buildbot/python/3.5.koobs-freebsd-current.nondebug/build/Lib/test/test_nntplib.py",
 line 291, in setUpClass
usenetrc=False)
  File 
"/usr/home/buildbot/python/3.5.koobs-freebsd-current.nondebug/build/Lib/nntplib.py",
 line 1077, in __init__
self.sock = _encrypt_on(self.sock, ssl_context, host)
  File 
"/usr/home/buildbot/python/3.5.koobs-freebsd-current.nondebug/build/Lib/nntplib.py",
 line 292, in _encrypt_on
return context.wrap_socket(sock, server_hostname=hostname)
  File 
"/usr/home/buildbot/python/3.5.koobs-freebsd-current.nondebug/build/Lib/ssl.py",
 line 385, in wrap_socket
_context=self)
  File 
"/usr/home/buildbot/python/3.5.koobs-freebsd-current.nondebug/build/Lib/ssl.py",
 line 760, in __init__
self.do_handshake()
  File 
"/usr/home/buildbot/python/3.5.koobs-freebsd-current.nondebug/build/Lib/ssl.py",
 line 996, in do_handshake
self._sslobj.do_handshake()
  File 
"/usr/home/buildbot/python/3.5.koobs-freebsd-current.nondebug/build/Lib/ssl.py",
 line 641, in do_handshake
self._sslobj.do_handshake()
ssl.SSLEOFError: EOF occurred in violation of protocol (_ssl.c:719)

--
resolution: fixed -> 
status: closed -> open

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue30188] test_nntplib: random EOFError in setUpClass()

2017-07-24 Thread STINNER Victor

Changes by STINNER Victor :


--
pull_requests: +2887

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue31012] suggestion: allow termination argument in argparse to be specified as argument

2017-07-24 Thread Leon Avery

New submission from Leon Avery:

In the argparse module, the argument '--' is interpreted as a signal that 
everything after it is a positional argument. '--' is literally written into 
the argparse code, in _parse_known_args. This means that a user who wishes to 
use '--' in some other way is out of luck. 

I suggest the addition of an argument to __init__ (or a method call, or 
something) that allows '--' to be replaced with some string of the user's 
choice.

--
components: Library (Lib)
messages: 298967
nosy: Leon Avery
priority: normal
severity: normal
status: open
title: suggestion: allow termination argument in argparse to be specified as 
argument
type: enhancement
versions: Python 3.6

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue30850] [2.7] bsddb3: test01_basic_replication() of test_bsddb3 fails randomly on AMD64 Windows8.1 Refleaks 2.7

2017-07-24 Thread STINNER Victor

STINNER Victor added the comment:

The test fails randomly. Since I'm unable to reproduce the bug, I close the 
bug. (If the bug is not fixed, I will reopen the issue.)

--
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue31012] suggestion: allow termination argument in argparse to be specified as argument

2017-07-24 Thread Steven D'Aprano

Steven D'Aprano added the comment:

> This means that a user who wishes to use '--' in some other way is out of 
> luck. 

I think that's a feature, not a limitation.

Command line arguments should use broadly consistent conventions. I don't want 
one program to use '--' for "end of options" and another program to use it for 
"something else".

Suppose you want to use '--' for "foo", and '%%' (say) as the end of options 
terminator. Whatever foo is. Okay, just swap them -- keep the usual convention 
where '--' is the options terminator, and use '%%' for foo. That way your users 
won't be surprised and confused by your application working differently from 
the great bulk of commandline applications. (Users never read the manual.)

But maybe I'll change my mind if you can show that there's already a very 
common, and useful, alternative convention of '--' for foo, for some definition 
of foo.

--
nosy: +steven.daprano

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue30908] test_os.TestSendfile.test_keywords() leaks dangling threads

2017-07-24 Thread STINNER Victor

Changes by STINNER Victor :


--
pull_requests: +2888

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue30908] test_os.TestSendfile.test_keywords() leaks dangling threads

2017-07-24 Thread STINNER Victor

Changes by STINNER Victor :


--
pull_requests: +2889

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue30892] _elementtree: assertion error if stdlib copy module is overriden

2017-07-24 Thread STINNER Victor

STINNER Victor added the comment:

Python 2.7 doesn't seem to be affected:

$ python2
Python 2.7.13+ (heads/2.7:598f26b, Jul 21 2017, 01:18:41) 
[GCC 6.3.1 20161221 (Red Hat 6.3.1-1)] on linux2
>>> import _elementtree
Traceback (most recent call last):
  File "", line 1, in 
  File "", line 1, in 
ImportError: cannot import name copy

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue30892] _elementtree: assertion error if stdlib copy module is overriden

2017-07-24 Thread STINNER Victor

Changes by STINNER Victor :


--
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue30908] test_os.TestSendfile.test_keywords() leaks dangling threads

2017-07-24 Thread STINNER Victor

STINNER Victor added the comment:

Serhiy Storchaka: If you would like to enhance the unittest module, please open 
a new issue. I prefer to keep this one for the very specific test_os bug.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue17611] Move unwinding of stack for "pseudo exceptions" from interpreter to compiler.

2017-07-24 Thread Antoine Pitrou

Antoine Pitrou added the comment:

Ok, I've now gotten rid of END_ITER.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue31013] gcc7 throws warning when pymem.h development header is used

2017-07-24 Thread Gabriel Somlo

New submission from Gabriel Somlo:

C programs using PyMem_MALLOC in pymem.h generate a warning when 
-Wint-in-bool-context is enabled (typically through -Wall). In places where 
-Werror is enabled (such as RPM build), this causes the build to fail with an 
error that looks like:

...
In file included from /usr/include/python2.7/Python.h:78:0,
 from netnsmodule.c:16:
netnsmodule.c: In function 'netns_nsexecvp':
/usr/include/python2.7/pymem.h:97:30: error: '*' in boolean context, suggest 
'&&' instead [-Werror=int-in-bool-context]
  ( (type *) PyMem_MALLOC((n) * sizeof(type)) ) )
  ^
/usr/include/python2.7/pymem.h:75:15: note: in definition of macro 
'PyMem_MALLOC'
 : malloc((n) ? (n) : 1))
   ^
netnsmodule.c:61:10: note: in expansion of macro 'PyMem_NEW'
   argv = PyMem_NEW(char *, argc + 1);
  ^
cc1: all warnings being treated as errors
error: command 'gcc' failed with exit status 1
...

I'm attaching a patch that fixes the issue, please consider applying!

Thanks,
--Gabriel

--
files: Python-2.7.13-pymem-gcc7.patch
keywords: patch
messages: 298973
nosy: Gabriel Somlo
priority: normal
severity: normal
status: open
title: gcc7 throws warning when pymem.h development header is used
versions: Python 2.7
Added file: http://bugs.python.org/file47035/Python-2.7.13-pymem-gcc7.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue31013] gcc7 throws warning when pymem.h development header is used

2017-07-24 Thread Gabriel Somlo

Gabriel Somlo added the comment:

This attachment illustrates how the problem is triggered. The file is part of 
the CORE network emulator (github.com/coreemu/core). Compile with "gcc -Wall 
-I/usr/include/python2.7 -c netnsmodule.c".

--
Added file: http://bugs.python.org/file47036/netnsmodule.c

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue31013] gcc7 throws warning when pymem.h development header is used

2017-07-24 Thread STINNER Victor

Changes by STINNER Victor :


--
nosy: +haypo

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue31013] gcc7 throws warning when pymem.h development header is used

2017-07-24 Thread STINNER Victor

STINNER Victor added the comment:

> /usr/include/python2.7/pymem.h:97:30: error: '*' in boolean context, suggest 
> '&&' instead [-Werror=int-in-bool-context]

I don't understand this error. I would be curious to see the output of the 
preprocessor. Try maybe to use gcc -E?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue31014] webbrowser._synthesize uses outdated calling signature for webbrowser.register

2017-07-24 Thread John Still

New submission from John Still:

The function `register` of the `webbrowser` module was updated a little while 
back to use the newish keyword-only argument syntax; however, the function 
`_synthesize` (also in `webbrowser`) is still using the outdated positional 
arguments only calling convention; leading a pair of tests in 
`Lib/tests/test_webbrowser.py` to fail.  I've issued a PR that fixes the 
function call to use the more modern calling convention.

--
components: Library (Lib)
messages: 298976
nosy: jmsdvl
priority: normal
pull_requests: 2890
severity: normal
status: open
title: webbrowser._synthesize uses outdated calling signature for 
webbrowser.register
type: behavior
versions: Python 3.7

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue31013] gcc7 throws warning when pymem.h development header is used

2017-07-24 Thread Gabriel Somlo

Gabriel Somlo added the comment:

output of "gcc -E -Wall -I/usr/include/python2.7 -c netnsmodule.c > foo.c"

I think gcc7 is a bit more paranoid about whether some expression evaluating to 
an int can/should in itself be used as a Boolean (i.e., without being compared 
to 0).

--
Added file: http://bugs.python.org/file47037/foo.c

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue31013] gcc7 throws warning when pymem.h development header is used

2017-07-24 Thread STINNER Victor

STINNER Victor added the comment:

> malloc(((argc + 1) * sizeof(char *)) ? ((argc + 1) * sizeof(char *)) : 1)) ) 
> );

Ah ok, the "(n)?" expression is "((argc + 1) * sizeof(char *)) ? " and yes it 
contains "*".

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue31015] PyErr_WriteUnraisable should be more verbose in Python 2.7

2017-07-24 Thread Christian Aguilera

New submission from Christian Aguilera:

When an exception is raised in a __del__ method or a finalizer (i.e. a
weakref callback), only the exception name is printed out.

Unfortunately, arbitrarily complex code can be involved which makes
debugging quite tedious. It would be nice to display the full traceback,
so that these errors are easier to diagnose.

The same bug was reported in the past, but it was fixed for Python 3.3 onwards.

Since it is trivial to get this fix in Python 2.7, I'm adding the patch for it 
here.

--
components: Library (Lib)
files: PyErr_WriteUnraisable.patch
keywords: patch
messages: 298979
nosy: christian.aguil...@foundry.com
priority: normal
severity: normal
status: open
title: PyErr_WriteUnraisable should be more verbose in Python 2.7
type: enhancement
versions: Python 2.7
Added file: http://bugs.python.org/file47038/PyErr_WriteUnraisable.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue1644818] Allow built-in packages and submodules as well as top-level modules

2017-07-24 Thread Eric Snow

Changes by Eric Snow :


--
nosy: +eric.snow

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue31016] [Regression] sphinx shows an EOF error when using python2.7 from the trunk

2017-07-24 Thread Matthias Klose

New submission from Matthias Klose:

[forwarded from https://bugs.debian.org/869098 and]

sphinx shows an EOF error when using python2.7 from the trunk. Last successful 
build was with the 2.7.13 release.

It looks like this is triggered only when using the parallel mode in sphinx.  I 
haven't yet worked on this issue, Sphinx is v1.4.9.

sphinx-build -b html -d _build/doctrees  -n -j 4 . _build/html
Running Sphinx v1.4.9
making output directory...
loading pickled environment... not yet created
loading intersphinx inventory from https://docs.python.org/2/objects.inv...
building [mo]: targets for 0 po files that are out of date
building [html]: targets for 91 source files that are out of date
updating environment: 91 added, 0 changed, 0 removed
reading sources... [100%] test-repositories .. writing-tests
  
waiting for workers...

Exception occurred:
  File "/usr/lib/python2.7/dist-packages/sphinx/util/parallel.py", line 97, in 
_join_one
exc, result = pipe.recv()
EOFError

--
components: Library (Lib)
messages: 298980
nosy: doko
priority: normal
severity: normal
status: open
title: [Regression] sphinx shows an EOF error when using python2.7 from the 
trunk
versions: Python 2.7

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue29930] Waiting for asyncio.StreamWriter.drain() twice in parallel raises an AssertionError when the transport stopped writing

2017-07-24 Thread Марк Коренберг

Марк Коренберг added the comment:

Triggered almost the same error. Minimal proof:

Documentation did not say that .drain() can't be called simultaneously.

===
async def do_nothing(client_reader, client_writer):
await asyncio.sleep(1)

mb = b'*' * (4096*4)
async def write_cmd(writer):
writer.write(mb)
await writer.drain()

async def amain():
srv = await asyncio.start_unix_server(do_nothing, b'\x00qwe')
(reader, writer) = await asyncio.open_unix_connection(b'\x00qwe')
await asyncio.gather(*(write_cmd(writer) for i in range(200)))

loop = asyncio.get_event_loop()
loop.run_until_complete(amain())
===

--
nosy: +socketpair

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue27099] IDLE: turn builting extensions into regular modules

2017-07-24 Thread Terry J. Reedy

Terry J. Reedy added the comment:

I am still thinking about how to handle user customization of key defs and 
values.

The current extensions tab does not enable custom key defs, so that would be a 
new feature, and hence could be handled separately, and normally.  I have not 
yet looked at the patch to see if it does anything in this regard.

I would like to move custom values to config-main.  But if we do that, existing 
customizations would be ignored and new customization will not be seen by older 
versions.  A second possibility is to write changes to both config-main and 
config-extensions, but reading them from both places would be a nuisance.  A 
third is to keep those options on config-extensions and ignore the enable 
fields even though idleConf would continue to read them. Whatever we do, we 
will need additions to config help and a 'see help' message.

Complicating the decision is that the extension tab was first added, two years 
ago I think, as a separate dialog with a separate system for handling user 
changes.  When we moved it to a new tab, we did *not* convert it to using the 
existing system.  Another existing deficiency is that there is no validity 
check on entries.

Fortunately, the decision of where to display is separate from where to store.  
But if displays are moved, the machinery for extension display will have to be 
changed to ignore values displayed elsewhere.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue30908] test_os.TestSendfile.test_keywords() leaks dangling threads

2017-07-24 Thread STINNER Victor

STINNER Victor added the comment:


New changeset 157b6ad677b7b330d30b2bb5ffbb2edac77b78cb by Victor Stinner in 
branch '3.5':
bpo-30908: Fix dangling thread in test_os.TestSendfile (#2680) (#2845)
https://github.com/python/cpython/commit/157b6ad677b7b330d30b2bb5ffbb2edac77b78cb


--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue30908] test_os.TestSendfile.test_keywords() leaks dangling threads

2017-07-24 Thread STINNER Victor

STINNER Victor added the comment:


New changeset bb33ccfc5a216eff753b10a8dc59ec0277f1e1fb by Victor Stinner in 
branch '3.6':
bpo-30908: Fix dangling thread in test_os.TestSendfile (#2680) (#2844)
https://github.com/python/cpython/commit/bb33ccfc5a216eff753b10a8dc59ec0277f1e1fb


--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue30188] test_nntplib: random EOFError in setUpClass()

2017-07-24 Thread STINNER Victor

STINNER Victor added the comment:


New changeset 5b4feb7e86ecb813b2c56560f86cda2fd46b9579 by Victor Stinner in 
branch 'master':
bpo-30188: test_nntplib catch also ssl.SSLEOFError (#2843)
https://github.com/python/cpython/commit/5b4feb7e86ecb813b2c56560f86cda2fd46b9579


--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue30728] IDLE: Modernize configdialog code.

2017-07-24 Thread Terry J. Reedy

Changes by Terry J. Reedy :


--
dependencies:  -test_bsddb3 crash on x86 Windows XP 2.7

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue31014] webbrowser._synthesize uses outdated calling signature for webbrowser.register

2017-07-24 Thread Serhiy Storchaka

Serhiy Storchaka added the comment:

Is it possible to write a test?

--
nosy: +daves, ncoghlan, serhiy.storchaka

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue31014] webbrowser._synthesize uses outdated calling signature for webbrowser.register

2017-07-24 Thread John Still

John Still added the comment:

What would a new test be testing? I only found this behaviour because two 
existing tests were failing (with the PR they pass, of course). I'm happy to 
write a test, I'm just not sure what the test should be testing that the 
existing tests don't already test.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue31013] gcc7 throws warning when pymem.h development header is used

2017-07-24 Thread Charalampos Stratakis

Changes by Charalampos Stratakis :


--
nosy: +cstratak

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue26762] test_multiprocessing_spawn leaves processes running in background

2017-07-24 Thread STINNER Victor

STINNER Victor added the comment:

Antoine Pitrou: "I'm not able to reproduce.  Can you try again with latest 
master?"

Oh, maybe I found why... There is a tearDownModule() function which hides bugs. 
Try following change:

diff --git a/Lib/test/_test_multiprocessing.py 
b/Lib/test/_test_multiprocessing.py
index 88e2eb3..ae77468 100644
--- a/Lib/test/_test_multiprocessing.py
+++ b/Lib/test/_test_multiprocessing.py
@@ -4432,8 +4432,8 @@ def install_tests_in_module_dict(remote_globs, 
start_method):
 def tearDownModule():
 multiprocessing.set_start_method(old_start_method[0], force=True)
 # pause a bit so we don't get warning about dangling threads/processes
-time.sleep(0.5)
-multiprocessing.process._cleanup()
+# time.sleep(0.5)
+# multiprocessing.process._cleanup()
 gc.collect()
 tmp = set(multiprocessing.process._dangling) - set(dangling[0])
 if tmp:

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue31014] webbrowser._synthesize uses outdated calling signature for webbrowser.register

2017-07-24 Thread Serhiy Storchaka

Serhiy Storchaka added the comment:

These tests are not failing on our buildbots and developer's computers. Seems 
they are failing only in special environment. This path of execution is not 
tested in more common environments, therefore possible regression couldn't be 
caught until somebody run tests in similar special environment. New test should 
test this path of execution in common environments.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue30304] TestCase.assertMultiLineEqual only registered for Unicode strings in 2.7

2017-07-24 Thread Aditya Hase

Changes by Aditya Hase :


--
pull_requests: +2891

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue30304] TestCase.assertMultiLineEqual only registered for Unicode strings in 2.7

2017-07-24 Thread Aditya Hase

Aditya Hase added the comment:

Hi, I'm new to python development community.
I've created a GitHub PR that fixes this issue.

--
nosy: +adityahase

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue30999] statistics module: add "key" keyword argument to median, mode, ...

2017-07-24 Thread Steven D'Aprano

Steven D'Aprano added the comment:

Thanks for explaining your use-case.

Although the median_* functions don't perform arithmetic on their data, 
they are still conceptually mathematical functions that operate on 
numbers and I'm reluctant to support arbitrary objects with a key 
function without a solid reason. In your example, I think there are 
existing ways to get the result you want:

(1) Use a dict:

data = dict([(1, ['Anna']), (3, ['Paul', 'Henry']), (4, ['Kate'])])
people = data[median_low(data)]

(2) Use a custom numeric type with associated data:

class MyNum(int):
def __new__(cls, num, data):
instance = super().__new__(cls, num)
instance.data = data
return instance

data = [MyNum(1, ['Anna']), MyNum(3, ['Paul', 'Henry']), 
MyNum(4, ['Kate'])]

people = median_low(data).data

As for your second example, do you have a use-case for wanting to know 
the position of the median in the original, unsorted list? When would 
that be useful?

One other reason for my reluctance: although median_low and median_high 
guarantee to only return an actual data point, that's a fairly special 
case. There are other order statistics (such as quartiles, quantiles, 
etc) which are conceptually related to median but don't necessarily 
return a data value. Indeed, the regular median() function doesn't 
always do so. I would be reluctant for median() and median_low() to have 
different signatures without an excellent reason.

I'm not completely ruling this out. One thing which might sway me is if 
there are other languages or statistics libraries which offer this 
feature. (I say *might*, not that it definitely will.)

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue30304] TestCase.assertMultiLineEqual only registered for Unicode strings in 2.7

2017-07-24 Thread Mariatta Wijaya

Changes by Mariatta Wijaya :


--
stage: needs patch -> patch review
versions: +Python 3.5, Python 3.6, Python 3.7

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue30304] TestCase.assertMultiLineEqual only registered for Unicode strings in 2.7

2017-07-24 Thread Serhiy Storchaka

Serhiy Storchaka added the comment:

This is related only to 2.7. All correct in 3.x.

--
nosy: +serhiy.storchaka
versions:  -Python 3.5, Python 3.6, Python 3.7

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue30714] test_ssl fails with openssl 1.1.0f: test_alpn_protocols()

2017-07-24 Thread R. David Murray

R. David Murray added the comment:

Well, the reason one *might* consider a test failure as a release blocker (and 
I'm not saying you should, I'm just explaining the possible logic) is that 
distros would understandably like the test suite to pass before they include a 
release in their distribution.

--
nosy: +r.david.murray

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue31017] gcc 7 fallthrough warnings

2017-07-24 Thread Charalampos Stratakis

New submission from Charalampos Stratakis:

On gcc 7 the new -Wimplicit-fallthrough option was introduced which produces 
warnings about switch cases that can fall through.

The easiest way to silence these warnings is to add the comment /* Falls 
through. */ for those cases. More information here [0]

Attaching the stderr output from compilation from the master branch.

[0] 
https://developers.redhat.com/blog/2017/03/10/wimplicit-fallthrough-in-gcc-7/

--
files: fallthrough36
messages: 298996
nosy: cstratak
priority: normal
severity: normal
status: open
title: gcc 7 fallthrough warnings
versions: Python 3.7
Added file: http://bugs.python.org/file47039/fallthrough36

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue30304] TestCase.assertMultiLineEqual only registered for Unicode strings in 2.7

2017-07-24 Thread Mariatta Wijaya

Mariatta Wijaya added the comment:

Thanks Serhiy.

Aditya, your PR was made against the master branch. Can you make the change 
against the 2.7 branch?

Thanks.

--
nosy: +Mariatta

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue30304] TestCase.assertMultiLineEqual only registered for Unicode strings in 2.7

2017-07-24 Thread Aditya Hase

Changes by Aditya Hase :


--
pull_requests: +2893

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue31017] gcc 7 fallthrough warnings

2017-07-24 Thread Zachary Ware

Zachary Ware added the comment:

This is a duplicate of bpo-30923.

--
nosy: +zach.ware
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> Add -Wimplicit-fallthrough=0 to Makefile ?

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue30923] Add -Wimplicit-fallthrough=0 to Makefile ?

2017-07-24 Thread Charalampos Stratakis

Changes by Charalampos Stratakis :


--
nosy: +cstratak

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue30916] Pre-build OpenSSL and Tcl/Tk for Windows

2017-07-24 Thread Segev Finer

Changes by Segev Finer :


--
pull_requests: +2894

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue30304] TestCase.assertMultiLineEqual only registered for Unicode strings in 2.7

2017-07-24 Thread Aditya Hase

Aditya Hase added the comment:

I've fixed that.

--
versions: +Python 3.5, Python 3.6, Python 3.7

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



  1   2   >