[issue30844] selector_events.py lacks exceptional event support

[Pim Klanke]

New submission from Pim Klanke:

To be able to use GPIO Sysfs Interface on our embedded platforms we require 
exceptional event support.

--
components: asyncio
messages: 297629
nosy: pklanke, yselivanov
priority: normal
severity: normal
status: open
title: selector_events.py lacks exceptional event support
type: enhancement
versions: Python 3.4, 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

[issue30844] selector_events.py lacks exceptional event support

[Pim Klanke]

Changes by Pim Klanke :


--
pull_requests: +2629

___
Python tracker 

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

[issue30837] Mac OS High Sierra Beta - Python Crash

[Ronald Oussoren]

Ronald Oussoren added the comment:

Joshua: does your script use os.fork(), or multiprocessing? 

In that case this is a known issue made worse on High Sierra: _scproxy uses 
Cocoa libraries, and those cause problems when using for without exec. In High 
Sierra the Cocoa libraries are more strict and are hence more likely to cause 
problems like this.

There's not much we can do about that, other than avoiding using _scproxy. If 
you don't use a proxy server setting "no_proxy" in your shell environment 
should do the trick.

--

___
Python tracker 

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

[issue1751519] curses - new window methods: addchstr and addchnstr

[Vegard]

Vegard added the comment:

Bump, I just found out addchstr() is unsupported, which is unfortunate as there 
doesn't seem to be any other easy way to prevent line wrapping if you submit 
too long strings to addstr() without keeping track of the x location and/or the 
string length by hand.

--
nosy: +vegard

___
Python tracker 

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

[issue29796] [2.7] test_weakref hangs on Python 2.7 on Windows

[STINNER Victor]

STINNER Victor added the comment:

Another option is to change time.sleep() rounding, but it would impact all 
Python2 code using sleep()... I dislike this option. I expect many complains 
from users about such backward incompatible change in a minor
release.

--

___
Python tracker 

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

[issue30843] [2.7] Lib/test/site.py conflicts with Lib/site.py when running tests

[STINNER Victor]

STINNER Victor added the comment:

This bug only impacts the Python test suite.

I see two options:

* Add "from __future__ import absolute_import" to all .py files in Lib/... I 
would prefer to not modify too many files to fix a regression caused by a new 
debug tool

* Rename Lib/test/bisect.py to Lib/test/bisectcmd.py.

I prefer the second option :-)

--

___
Python tracker 

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

[issue30843] [2.7] Lib/test/bisect.py conflicts with Lib/bisect.py when running tests

[STINNER Victor]

Changes by STINNER Victor :


--
title: [2.7] Lib/test/site.py conflicts with Lib/site.py when running tests -> 
[2.7] Lib/test/bisect.py conflicts with Lib/bisect.py when running tests

___
Python tracker 

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

[issue30843] [2.7] Lib/test/bisect.py conflicts with Lib/bisect.py when running tests

[STINNER Victor]

Changes by STINNER Victor :


--
pull_requests: +2630

___
Python tracker 

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

[issue29796] [2.7] test_weakref hangs on Python 2.7 on Windows

[STINNER Victor]

STINNER Victor added the comment:


New changeset 1fef0154d97bd7f01c5bc59954a278bacf1a3f0e by Victor Stinner in 
branch '2.7':
bpo-29796: test_weakref: Fix collect_in_thread() on Windows (#2553)
https://github.com/python/cpython/commit/1fef0154d97bd7f01c5bc59954a278bacf1a3f0e


--

___
Python tracker 

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

[issue29796] [2.7] test_weakref hangs on Python 2.7 on Windows

[STINNER Victor]

STINNER Victor added the comment:

I looked at test_weakref duration on buildbots before my change:

* AMD64 Windows7 SP1 2.7: (less than 30 seconds)
* AMD64 Windows8 2.7: 36 sec
* AMD64 Windows8.1 Non-Debug 2.7: 450.6 sec

Hum. That's strange. I don't understand why sometimes test_weakref hangs, 
whereaas sometimes it pass in less than 60 seconds?

--

___
Python tracker 

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

[issue30843] [2.7] Lib/test/bisect.py conflicts with Lib/bisect.py when running tests

[STINNER Victor]

STINNER Victor added the comment:


New changeset 28b72baf3c1e57af0c9338fb41c89d62aa47a355 by Victor Stinner in 
branch '2.7':
bpo-30843: Rename Lib/test/bisect.py to Lib/test/bisectcmd.py (#2563)
https://github.com/python/cpython/commit/28b72baf3c1e57af0c9338fb41c89d62aa47a355


--

___
Python tracker 

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

[issue30843] [2.7] Lib/test/bisect.py conflicts with Lib/bisect.py when running tests

[STINNER Victor]

STINNER Victor added the comment:

Fixed: I renamed Lib/test/bisect.py to Lib/test/bisectcmd.py.

--
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

[issue29796] [2.7] test_weakref hangs on Python 2.7 on Windows

[STINNER Victor]

STINNER Victor added the comment:

Oh wow! The commit 1fef0154d97bd7f01c5bc59954a278bacf1a3f0e fixed PGO 
compilation on Python 2.7: 
http://buildbot.python.org/all/builders/AMD64%20Debian%20PGO%202.7/builds/227 
is the first successful build since June 20. I didn't notice that the PGO 
buildbot was also stuck in running test_weakref in the compile step: job killed 
after 30 min.
---
...
0:06:01 [380/400] test_warnings
0:06:02 [381/400] test_wave
0:06:02 [382/400] test_weakref

command timed out: 1200 seconds without output running ['make', 'all'], 
attempting to kill
process killed by signal 9
program finished with exit code -1
elapsedTime=1699.00
---

While build 206 was green, the buildbot started to fail in build 207:

http://buildbot.python.org/all/builders/AMD64%20Debian%20PGO%202.7/builds/207

The strange thing is that this change only contains two small changes:
* commit b39a7481ee7e6166d6d2b252a7a514b1f6553dfa
* commit d4324baca4c03eb8d55446cd1b74b32ec5633af5

I fail to understand how these changes make test_weakref hangs.

Well, at least the good news is that it's now fixed ;-)

--

___
Python tracker 

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

[issue30845] [3.5] test_first_completed_some_already_completed() of test_concurrent_futures.ProcessPoolWaitTests: time.sleep() fails with "sleep length must be non-negative" in setUp() on x86 Tiger 3.

[STINNER Victor]

New submission from STINNER Victor:

Code of the setUp() method:

class ExecutorMixin:
worker_count = 5

def setUp(self):
self.t1 = time.time()
try:
self.executor = self.executor_type(max_workers=self.worker_count)
except NotImplementedError as e:
self.skipTest(str(e))
self._prime_executor()

def _prime_executor(self):
# Make sure that the executor is ready to do work before running the
# tests. This should reduce the probability of timeouts in the tests.
futures = [self.executor.submit(time.sleep, 0.1)
   for _ in range(self.worker_count)]

for f in futures:
f.result()


I don't understand how the child process can fail with ValueError("sleep length 
must be non-negative") when running time.sleep(0.1). Code of the sleep function:

static PyObject *
time_sleep(PyObject *self, PyObject *obj)
{
_PyTime_t secs;
if (_PyTime_FromSecondsObject(&secs, obj, _PyTime_ROUND_CEILING))
return NULL;
if (secs < 0) {
PyErr_SetString(PyExc_ValueError,
"sleep length must be non-negative");
return NULL;
}
if (pysleep(secs) != 0)
return NULL;
Py_INCREF(Py_None);
return Py_None;
}

Can it be a major rounding issue in time_sleep()? Or concurrent.futures failed 
completely to serialized the floating point number 0.1?


http://buildbot.python.org/all/builders/x86%20Tiger%203.5/builds/324/steps/test/logs/stdio

0:27:59 load avg: 1.54 [211/398/1] test_concurrent_futures
test_cancel (test.test_concurrent_futures.FutureTests) ... ok
test_cancelled (test.test_concurrent_futures.FutureTests) ... ok
test_done (test.test_concurrent_futures.FutureTests) ... ok
test_done_callback_already_cancelled (test.test_concurrent_futures.FutureTests) 
... ok
test_done_callback_already_failed (test.test_concurrent_futures.FutureTests) 
... ok
test_done_callback_already_successful 
(test.test_concurrent_futures.FutureTests) ... ok
test_done_callback_raises (test.test_concurrent_futures.FutureTests) ... ok
test_done_callback_with_cancel (test.test_concurrent_futures.FutureTests) ... ok
test_done_callback_with_exception (test.test_concurrent_futures.FutureTests) 
... ok
test_done_callback_with_result (test.test_concurrent_futures.FutureTests) ... ok
test_exception_with_success (test.test_concurrent_futures.FutureTests) ... ok
test_exception_with_timeout (test.test_concurrent_futures.FutureTests) ... ok
test_repr (test.test_concurrent_futures.FutureTests) ... ok
test_result_with_cancel (test.test_concurrent_futures.FutureTests) ... ok
test_result_with_success (test.test_concurrent_futures.FutureTests) ... ok
test_result_with_timeout (test.test_concurrent_futures.FutureTests) ... ok
test_running (test.test_concurrent_futures.FutureTests) ... ok
test_duplicate_futures 
(test.test_concurrent_futures.ProcessPoolAsCompletedTests) ... 2.20s ok
test_no_timeout (test.test_concurrent_futures.ProcessPoolAsCompletedTests) ... 
0.18s ok
test_zero_timeout (test.test_concurrent_futures.ProcessPoolAsCompletedTests) 
... 2.20s ok
test_killed_child (test.test_concurrent_futures.ProcessPoolExecutorTest) ... 
0.21s ok
test_map (test.test_concurrent_futures.ProcessPoolExecutorTest) ... 0.20s ok
test_map_chunksize (test.test_concurrent_futures.ProcessPoolExecutorTest) ... 
0.21s ok
test_map_exception (test.test_concurrent_futures.ProcessPoolExecutorTest) ... 
0.19s ok
test_map_timeout (test.test_concurrent_futures.ProcessPoolExecutorTest) ... 
6.18s ok
test_max_workers_negative 
(test.test_concurrent_futures.ProcessPoolExecutorTest) ... 0.21s ok
test_no_stale_references (test.test_concurrent_futures.ProcessPoolExecutorTest) 
... 0.20s ok
test_shutdown_race_issue12456 
(test.test_concurrent_futures.ProcessPoolExecutorTest) ... 0.19s ok
test_submit (test.test_concurrent_futures.ProcessPoolExecutorTest) ... 0.18s ok
test_submit_keyword (test.test_concurrent_futures.ProcessPoolExecutorTest) ... 
0.21s ok
test_traceback (test.test_concurrent_futures.ProcessPoolExecutorTest) ... 0.20s 
ok
test_context_manager_shutdown 
(test.test_concurrent_futures.ProcessPoolShutdownTest) ... 0.10s ok
test_del_shutdown (test.test_concurrent_futures.ProcessPoolShutdownTest) ... 
0.10s ok
test_hang_issue12364 (test.test_concurrent_futures.ProcessPoolShutdownTest) ... 
1.09s ok
test_interpreter_shutdown 
(test.test_concurrent_futures.ProcessPoolShutdownTest) ... 2.13s ok
test_processes_terminate (test.test_concurrent_futures.ProcessPoolShutdownTest) 
... 0.09s ok
test_run_after_shutdown (test.test_concurrent_futures.ProcessPoolShutdownTest) 
... 0.00s ok
test_all_completed (test.test_concurrent_futures.ProcessPoolWaitTests) ... 
0.20s ok
test_first_completed (test.test_concurrent_futures.ProcessPoolWaitTests) ... 
1.69s ok
test_first_completed_some_already_completed 
(test.test_concurrent_futures.ProcessPoolWaitTests) ... ERROR
test_first_exception (test.test_concurrent_futures.ProcessPoolWa

[issue29868] multiprocessing.dummy missing cpu_count

[STINNER Victor]

STINNER Victor added the comment:

multiprocessing.dummy lacks many symbols:

>>> set(multiprocessing.__all__) - set(multiprocessing.dummy.__all__)
{'RawArray', 'set_forkserver_preload', 'ProcessError', 'RawValue', 
'BufferTooShort', 'reducer', 'set_executable', 'Array', 'cpu_count', 
'get_all_start_methods', 'get_start_method', 'AuthenticationError', 'Value', 
'set_start_method', 'allow_connection_pickling', 'get_logger', 'SimpleQueue', 
'TimeoutError', 'log_to_stderr', 'get_context'}

--
nosy: +haypo

___
Python tracker 

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

[issue30845] [3.5] test_first_completed_some_already_completed() of test_concurrent_futures.ProcessPoolWaitTests: time.sleep() fails with "sleep length must be non-negative" in setUp() on x86 Tiger 3.

[STINNER Victor]

Changes by STINNER Victor :


--
pull_requests: +2631

___
Python tracker 

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

[issue30846] test_rapid_restart() of test_multiprocessing_fork fails randomly on AMD64 Debian PGO 3.6

[STINNER Victor]

New submission from STINNER Victor:

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

==
ERROR: test_rapid_restart 
(test.test_multiprocessing_fork.WithProcessesTestManagerRestart)
--
Traceback (most recent call last):
  File 
"/var/lib/buildbot/slaves/enable-optimizations-bot/3.6.gps-debian-profile-opt.nondebug/build/Lib/test/_test_multiprocessing.py",
 line 2410, in test_rapid_restart
manager.start()
  File 
"/var/lib/buildbot/slaves/enable-optimizations-bot/3.6.gps-debian-profile-opt.nondebug/build/Lib/multiprocessing/managers.py",
 line 517, in start
self._address = reader.recv()
  File 
"/var/lib/buildbot/slaves/enable-optimizations-bot/3.6.gps-debian-profile-opt.nondebug/build/Lib/multiprocessing/connection.py",
 line 250, in recv
buf = self._recv_bytes()
  File 
"/var/lib/buildbot/slaves/enable-optimizations-bot/3.6.gps-debian-profile-opt.nondebug/build/Lib/multiprocessing/connection.py",
 line 407, in _recv_bytes
buf = self._recv(4)
  File 
"/var/lib/buildbot/slaves/enable-optimizations-bot/3.6.gps-debian-profile-opt.nondebug/build/Lib/multiprocessing/connection.py",
 line 383, in _recv
raise EOFError
EOFError
(...)
Re-running test 'test_multiprocessing_fork' in verbose mode
(...)
test_rapid_restart 
(test.test_multiprocessing_fork.WithManagerTestManagerRestart) ... ok

--
components: Library (Lib)
messages: 297641
nosy: davin, haypo
priority: normal
severity: normal
status: open
title: test_rapid_restart() of test_multiprocessing_fork fails randomly on 
AMD64 Debian PGO 3.6
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

[issue30846] [3.6] test_rapid_restart() of test_multiprocessing_fork fails randomly on AMD64 Debian PGO 3.6

[STINNER Victor]

Changes by STINNER Victor :


--
title: test_rapid_restart() of test_multiprocessing_fork fails randomly on 
AMD64 Debian PGO 3.6 -> [3.6] test_rapid_restart() of test_multiprocessing_fork 
fails randomly on AMD64 Debian PGO 3.6

___
Python tracker 

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

[issue30845] [3.5] test_first_completed_some_already_completed() of test_concurrent_futures.ProcessPoolWaitTests: time.sleep() fails with "sleep length must be non-negative" in setUp() on x86 Tiger 3.

[STINNER Victor]

STINNER Victor added the comment:


New changeset 3df9dec425b0254df1cdf41922fd8d6b08bf47e4 by Victor Stinner in 
branch 'master':
bpo-30845: Enhance test_concurrent_futures cleanup (#2564)
https://github.com/python/cpython/commit/3df9dec425b0254df1cdf41922fd8d6b08bf47e4


--

___
Python tracker 

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

[issue30844] selector_events.py lacks exceptional event support

[STINNER Victor]

Changes by STINNER Victor :


--
nosy: +neologix

___
Python tracker 

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

[issue30844] selectors and asyncio: add_excepter(), 3rd argument of select.select()

[STINNER Victor]

Changes by STINNER Victor :


--
title: selector_events.py lacks exceptional event support -> selectors and 
asyncio: add_excepter(), 3rd argument of select.select()
versions:  -Python 3.4, Python 3.5, Python 3.6

___
Python tracker 

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

[issue30319] Change socket.close() to ignore ECONNRESET

[STINNER Victor]

STINNER Victor added the comment:

I propose to ignore ECONNRESET in socket.close() and ENOTCONN and WSAEINVAL on 
socket.shutdown(). If we see more failures later, we can extend these lists.


asyncore also ignores ENOTCONN on socket.close(), but I don't trust this module 
at this point: it seems like asyncore also handles pipes, not only 
socket.socket.


Errors seen on buildbots:

* ECONNRESET (ConnectionResetError) on socket.close()
* ENOTCONN and WSAEINVAL on socket.shutdown() -- that's why I ignored these 
errors in poplib and imaplib


The Python standard library already ignores some errors on socket.shutdown() 
and socket.close() depending on the module:

* poplib, imaplib: ignore ENOTCONN and WSAEINVAL on socket.shutdown()

* asyncore: ignore ENOTCONN and EBADF on socket.close(). asyncore ignores much 
more errors on functions doing read, write or close (depending on the received 
event): ECONNRESET, ENOTCONN, ESHUTDOWN, ECONNABORTED, EPIPE, EBADF. In a 
function doing read+close, it says "winsock sometimes raises ENOTCONN".

* asyncio: don't log a fatal error for EPIPE, ESHUTDOWN, ECONNRESET, 
ECONNABORTED errors. Lib/asyncio/base_events.py:

# Exceptions which must not call the exception handler in fatal error
# methods (_fatal_error())
_FATAL_ERROR_IGNORE = (BrokenPipeError, ConnectionResetError, 
ConnectionAbortedError)


Mapping of exceptions to error codes:

* BrokenPipeError: EPIPE, ESHUTDOWN
* ConnectionResetError: ECONNRESET
* ConnectionAbortedError: ECONNABORTED

--

___
Python tracker 

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

[issue30319] Change socket.close() to ignore ECONNRESET

[Antoine Pitrou]

Antoine Pitrou added the comment:

shutdown() is not the same thing as close().  If you want to ignore errors on 
shutdown() you should open a separate issue (and argument for it, because "I 
saw the error on the buildbots" is not a sufficient reason IMHO).

--

___
Python tracker 

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

[issue30319] Change socket.close() to ignore ECONNRESET

[STINNER Victor]

Changes by STINNER Victor :


--
pull_requests: +2632

___
Python tracker 

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

[issue30319] Change socket.close() to ignore ECONNRESET

[STINNER Victor]

STINNER Victor added the comment:

Antoine Pitrou: "shutdown() is not the same thing as close()."

I consider that the bug is similar to socket.close() error, since we also get 
an exception because the peer closed the connection. It's just the error code 
which is different.


Antoine Pitrou: "If you want to ignore errors on shutdown() you should open a 
separate issue (and argument for it, because "I saw the error on the buildbots" 
is not a sufficient reason IMHO)."

bpo-4473 modified poplib to ignore ENOTCONN on shutdown(), patch by Lorenzo 
Catucci committed by you :-) Commit d89824b0e2fa9a44b56394a5185de737a6527ea7. 
Commit 81c87c5e9a81728f4c7b022e3786ce11d53ed3c9 modified impalib to ignore 
ENOTCONN, commit written and pushed by you ;-)

In the bpo-30329, I modified poplib and imaplib to also ignore WSAEINVAL on 
shutdown().

I don't see the need to separate socket.close() and socket.shutdown() error 
handling in two issues.

--

___
Python tracker 

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

[issue30319] Change socket.close() to ignore ECONNRESET

[STINNER Victor]

STINNER Victor added the comment:

I wrote https://github.com/python/cpython/pull/2565

* socket.close() now ignores ECONNRESET error
* socket.shutdown() now ignores ENOTCONN and WSAEINVAL errors

--

___
Python tracker 

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

[issue29796] [2.7] test_weakref hangs on Python 2.7 on Windows

[STINNER Victor]

STINNER Victor added the comment:

With commit 1fef0154d97bd7f01c5bc59954a278bacf1a3f0e, test_weakref takes 11 
seconds on my Windows VM.

Without this fix, test_weakref runs for longer than 2 hour and 19 min on my 
Windows VM. I decided to kill the test, I don't want to burn my CPU too long :-)

So at least, on my Windows VM, the bug is trivial to reproduce!

--

___
Python tracker 

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

[issue30789] Redesign PyCodeObject.co_extras to use a single memory block, instead of two

[STINNER Victor]

STINNER Victor added the comment:


New changeset 378ebb6578b9d709f38b888d23874c0b18125249 by Victor Stinner 
(Serhiy Storchaka) in branch 'master':
bpo-30789: Use a single memory block for co_extra. (#2555)
https://github.com/python/cpython/commit/378ebb6578b9d709f38b888d23874c0b18125249


--

___
Python tracker 

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

[issue30319] Change socket.close() to ignore ECONNRESET

[Antoine Pitrou]

Antoine Pitrou added the comment:

Le 04/07/2017 à 14:00, STINNER Victor a écrit :
> 
> Antoine Pitrou: "shutdown() is not the same thing as close()."
> 
> I consider that the bug is similar to socket.close() error,
> [...]

First, let's not call it a bug when an error is reported to the user.  A
bug would be to silence all errors just because they annoy one core
developer.

Second, close() and shutdown() are different functions operating at
different levels.  close() operates at the OS level and releases
resources associated with the given file descriptor.  It might, but
might not, do any I/O (such as flush buffers or send a TCP RST) -- for
example, if you duplicated a fd after fork(), calling close() on only
one of them will do absolutely nothing at the I/O level.

shutdown() operates at the transport level.  Someone who calls
shutdown() *must* be notified that the shutdown went wrong, because
that's the only thing shutdown() does.  shutdown() does nothing at the
OS level.

It makes sense to silence some errors in close() because, most of the
time, people call close() to release resources and they don't care
whether the other end of the connection was notified in time.  It
doesn't make sense to do the same for shutdown().

--

___
Python tracker 

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

[issue30789] Redesign PyCodeObject.co_extras to use a single memory block, instead of two

[Serhiy Storchaka]

Changes by Serhiy Storchaka :


--
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

[issue30319] Change socket.close() to ignore ECONNRESET

[STINNER Victor]

STINNER Victor added the comment:

Ok, I rewrote my PR to only ignore ECONNRESET in socket.close().

--

___
Python tracker 

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

[issue30844] selectors: add_excepter(), 3rd argument of select.select()

[Pim Klanke]

Changes by Pim Klanke :


--
components:  -asyncio
title: selectors and asyncio: add_excepter(), 3rd argument of select.select() 
-> selectors: add_excepter(), 3rd argument of select.select()

___
Python tracker 

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

[issue30319] Change socket.close() to ignore ECONNRESET

[STINNER Victor]

STINNER Victor added the comment:

I wrote https://github.com/python/cpython/pull/2565 because the 
ConnectionResetError error on socket.close() is more and more a cause of 
failures on FreeBSD buildbots. I mean that I fixed enough other bugs to start 
to only see one specific bug more often ;-) (Before we had dozens of random 
bugs.)

--

___
Python tracker 

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

[issue30231] test_imaplib needs a TLS server accepting self-signed certificates

[STINNER Victor]

Changes by STINNER Victor :


--
pull_requests: +2634

___
Python tracker 

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

[issue30844] selectors: Add exceptional urgent data event

[Pim Klanke]

Changes by Pim Klanke :


--
title: selectors: add_excepter(), 3rd argument of select.select() -> selectors: 
Add exceptional urgent data event

___
Python tracker 

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

[issue30847] asyncio: selector_events: add_excepter(), 3rd argument of select.select()

[Pim Klanke]

New submission from Pim Klanke:

depends on bpo-30844

--
components: asyncio
messages: 297652
nosy: pklanke, yselivanov
priority: normal
severity: normal
status: open
title: asyncio: selector_events: add_excepter(), 3rd argument of select.select()
type: enhancement
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

[issue30847] asyncio: selector_events: add_excepter(), 3rd argument of select.select()

[STINNER Victor]

STINNER Victor added the comment:

Please elaborate the description :-)

--
nosy: +haypo

___
Python tracker 

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

[issue30847] asyncio: selector_events: add_excepter(), 3rd argument of select.select()

[STINNER Victor]

STINNER Victor added the comment:

Does the Windows Proactor event loop has a similar concept of "excepter"?

--

___
Python tracker 

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

[issue30847] asyncio: selector_events: add_excepter(), 3rd argument of select.select()

[Pim Klanke]

Pim Klanke added the comment:

To be able to use GPIO Sysfs Interface with asyncio on our embedded platforms, 
we require exceptional event support in asyncio.

depends on bpo-30844

--

___
Python tracker 

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

[issue30319] Change socket.close() to ignore ECONNRESET

[STINNER Victor]

STINNER Victor added the comment:


New changeset 67e1478dba6efe60b8e1890192014b8b06dd6bd9 by Victor Stinner in 
branch 'master':
bpo-30319: socket.close() now ignores ECONNRESET (#2565)
https://github.com/python/cpython/commit/67e1478dba6efe60b8e1890192014b8b06dd6bd9


--

___
Python tracker 

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

[issue26685] Raise errors from socket.close()

[STINNER Victor]

STINNER Victor added the comment:


New changeset 67e1478dba6efe60b8e1890192014b8b06dd6bd9 by Victor Stinner in 
branch 'master':
bpo-30319: socket.close() now ignores ECONNRESET (#2565)
https://github.com/python/cpython/commit/67e1478dba6efe60b8e1890192014b8b06dd6bd9


--

___
Python tracker 

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

[issue30319] Change socket.close() to ignore ECONNRESET

[STINNER Victor]

Changes by STINNER Victor :


--
pull_requests: +2635

___
Python tracker 

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

[issue26685] Raise errors from socket.close()

[STINNER Victor]

Changes by STINNER Victor :


--
pull_requests: +2636

___
Python tracker 

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

[issue30843] [2.7] Lib/test/bisect.py conflicts with Lib/bisect.py when running tests

[STINNER Victor]

Changes by STINNER Victor :


--
pull_requests: +2637

___
Python tracker 

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

[issue26685] Raise errors from socket.close()

[STINNER Victor]

STINNER Victor added the comment:


New changeset 580cd5cd3603317d294a881628880a92ea221334 by Victor Stinner in 
branch '3.6':
bpo-30319: socket.close() now ignores ECONNRESET (#2565) (#2566)
https://github.com/python/cpython/commit/580cd5cd3603317d294a881628880a92ea221334


--

___
Python tracker 

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

[issue30319] Change socket.close() to ignore ECONNRESET

[STINNER Victor]

STINNER Victor added the comment:


New changeset 580cd5cd3603317d294a881628880a92ea221334 by Victor Stinner in 
branch '3.6':
bpo-30319: socket.close() now ignores ECONNRESET (#2565) (#2566)
https://github.com/python/cpython/commit/580cd5cd3603317d294a881628880a92ea221334


--

___
Python tracker 

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

[issue30543] test_timeout fails on AMD64 FreeBSD CURRENT Debug 3.x: ConnectionResetError: [Errno 54] Connection reset by peer

[STINNER Victor]

Changes by STINNER Victor :


--
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> Change socket.close() to ignore ECONNRESET

___
Python tracker 

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

[issue30319] Change socket.close() to ignore ECONNRESET

[STINNER Victor]

STINNER Victor added the comment:

Ok. I modified socket.close() to ignore ECONNRESET in Python 3.6 and 3.7. I 
will leave the issue open a few days to see if it helps to reduce buildbot 
failure rate.

--

___
Python tracker 

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

[issue30328] test_ssl.test_connect_with_context(): ConnectionResetError on AMD64 FreeBSD 9.x 3.6

[STINNER Victor]

STINNER Victor added the comment:

Duplicate of bpo-30319.

--
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> Change socket.close() to ignore ECONNRESET

___
Python tracker 

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

[issue30315] test_ftplib.TestTLS_FTPClass: "[Errno 54] Connection reset by peer" on "AMD64 FreeBSD CURRENT Debug 3.x" buildbot

[STINNER Victor]

STINNER Victor added the comment:

This issue seems like a duplicate of bpo-30319. While I'm not 100% confident, 
I'm quite sure that ignoring ECONNRESET in socket.close() should help ;-)

--
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> Change socket.close() to ignore ECONNRESET

___
Python tracker 

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

[issue30106] test_asyncore: test_handle_write() fails in tearDown()

[STINNER Victor]

STINNER Victor added the comment:

File 
"/usr/home/buildbot/python/3.x.koobs-freebsd-current.nondebug/build/Lib/socket.py",
 line 411, in _real_close
_ss.close(self)
ConnectionResetError: [Errno 54] Connection reset by peer


This bug was fixed by bpo-30319.

--

___
Python tracker 

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

[issue27784] Random failure of test_TCPServer() of test.test_socketserver.SocketServerTest and test_handle_accept() of test.test_asyncore.TestAPI_UseIPv6Select on FreeBSD buildbots

[STINNER Victor]

Changes by STINNER Victor :


--
resolution: out of date -> duplicate
superseder:  -> Change socket.close() to ignore ECONNRESET

___
Python tracker 

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

[issue30319] Change socket.close() to ignore ECONNRESET

[STINNER Victor]

STINNER Victor added the comment:

I don't see the link between this issue and bpo-30652 or bpo-30391, I removed 
these dependencies.

I marked bpo-27784, bpo-30328, bpo-30543 and bpo-30315 as duplicates of this 
issue.

bpo-30106 was already fixed, differently, but I mentioned this issue in it.

--
dependencies:  -Random failure of test_TCPServer() of 
test.test_socketserver.SocketServerTest and test_handle_accept() of 
test.test_asyncore.TestAPI_UseIPv6Select on FreeBSD buildbots, test_asyncore: 
test_handle_write() fails in tearDown(), test_ftplib.TestTLS_FTPClass: "[Errno 
54] Connection reset by peer" on "AMD64 FreeBSD CURRENT Debug 3.x" buildbot, 
test_ssl.test_connect_with_context(): ConnectionResetError on AMD64 FreeBSD 9.x 
3.6, test_threading_handled() of test_socketserver hangs randomly on AMD64 
FreeBSD 10.x Shared 3.6, test_threading_not_handled() of test_socketserver 
hangs randomly on AMD64 FreeBSD 10.x Shared 3.6, test_timeout fails on AMD64 
FreeBSD CURRENT Debug 3.x: ConnectionResetError: [Errno 54] Connection reset by 
peer

___
Python tracker 

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

[issue30652] test_threading_not_handled() of test_socketserver hangs randomly on AMD64 FreeBSD 10.x Shared 3.6

[STINNER Victor]

STINNER Victor added the comment:

While the traceback is not identify, this issue really looks like a duplicate 
of bpo-30391.

--
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> test_threading_handled() of test_socketserver hangs randomly on 
AMD64 FreeBSD 10.x Shared 3.6

___
Python tracker 

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

[issue30391] test_threading_handled() and test_threading_not_handled() of test_socketserver hangs randomly on AMD64 FreeBSD 10.x Shared 3.6

[STINNER Victor]

STINNER Victor added the comment:

I marked bpo-30652 as duplicate of this issue. Copy of the first message 
msg295903:

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

0:16:16 [405/405] test_socketserver crashed
Timeout (0:15:00)!
Thread 0x000802006400 (most recent call first):
  File "/usr/home/buildbot/python/3.6.koobs-freebsd10/build/Lib/threading.py", 
line 295 in wait
  File "/usr/home/buildbot/python/3.6.koobs-freebsd10/build/Lib/threading.py", 
line 551 in wait
  File 
"/usr/home/buildbot/python/3.6.koobs-freebsd10/build/Lib/test/test_socketserver.py",
 line 369 in wait_done
  File 
"/usr/home/buildbot/python/3.6.koobs-freebsd10/build/Lib/test/test_socketserver.py",
 line 341 in __init__
  File 
"/usr/home/buildbot/python/3.6.koobs-freebsd10/build/Lib/test/test_socketserver.py",
 line 362 in __init__
  File 
"/usr/home/buildbot/python/3.6.koobs-freebsd10/build/Lib/test/test_socketserver.py",
 line 312 in test_threading_not_handled
  File 
"/usr/home/buildbot/python/3.6.koobs-freebsd10/build/Lib/unittest/case.py", 
line 601 in run
  File 
"/usr/home/buildbot/python/3.6.koobs-freebsd10/build/Lib/unittest/case.py", 
line 649 in __call__
  File 
"/usr/home/buildbot/python/3.6.koobs-freebsd10/build/Lib/unittest/suite.py", 
line 122 in run
  File 
"/usr/home/buildbot/python/3.6.koobs-freebsd10/build/Lib/unittest/suite.py", 
line 84 in __call__
  File 
"/usr/home/buildbot/python/3.6.koobs-freebsd10/build/Lib/unittest/suite.py", 
line 122 in run
  File 
"/usr/home/buildbot/python/3.6.koobs-freebsd10/build/Lib/unittest/suite.py", 
line 84 in __call__
  File 
"/usr/home/buildbot/python/3.6.koobs-freebsd10/build/Lib/unittest/suite.py", 
line 122 in run
  File 
"/usr/home/buildbot/python/3.6.koobs-freebsd10/build/Lib/unittest/suite.py", 
line 84 in __call__
  File 
"/usr/home/buildbot/python/3.6.koobs-freebsd10/build/Lib/unittest/runner.py", 
line 176 in run
  File 
"/usr/home/buildbot/python/3.6.koobs-freebsd10/build/Lib/test/support/__init__.py",
 line 1889 in _run_suite
  File 
"/usr/home/buildbot/python/3.6.koobs-freebsd10/build/Lib/test/support/__init__.py",
 line 1923 in run_unittest
  File 
"/usr/home/buildbot/python/3.6.koobs-freebsd10/build/Lib/test/libregrtest/runtest.py",
 line 164 in test_runner
  File 
"/usr/home/buildbot/python/3.6.koobs-freebsd10/build/Lib/test/libregrtest/runtest.py",
 line 165 in runtest_inner
  File 
"/usr/home/buildbot/python/3.6.koobs-freebsd10/build/Lib/test/libregrtest/runtest.py",
 line 119 in runtest
  File 
"/usr/home/buildbot/python/3.6.koobs-freebsd10/build/Lib/test/libregrtest/runtest_mp.py",
 line 71 in run_tests_slave
  File 
"/usr/home/buildbot/python/3.6.koobs-freebsd10/build/Lib/test/libregrtest/main.py",
 line 475 in _main
  File 
"/usr/home/buildbot/python/3.6.koobs-freebsd10/build/Lib/test/libregrtest/main.py",
 line 468 in main
  File 
"/usr/home/buildbot/python/3.6.koobs-freebsd10/build/Lib/test/libregrtest/main.py",
 line 532 in main
  File 
"/usr/home/buildbot/python/3.6.koobs-freebsd10/build/Lib/test/regrtest.py", 
line 46 in _main
  File 
"/usr/home/buildbot/python/3.6.koobs-freebsd10/build/Lib/test/regrtest.py", 
line 50 in 
  File "/usr/home/buildbot/python/3.6.koobs-freebsd10/build/Lib/runpy.py", line 
85 in _run_code
  File "/usr/home/buildbot/python/3.6.koobs-freebsd10/build/Lib/runpy.py", line 
193 in _run_module_as_main

--
title: test_threading_handled() of test_socketserver hangs randomly on AMD64 
FreeBSD 10.x Shared 3.6 -> test_threading_handled() and 
test_threading_not_handled() of test_socketserver hangs randomly on AMD64 
FreeBSD 10.x Shared 3.6

___
Python tracker 

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

[issue30319] Change socket.close() to ignore ECONNRESET

[Alex Gaynor]

Changes by Alex Gaynor :


--
nosy:  -alex

___
Python tracker 

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

[issue27784] Random failure of test_TCPServer() of test.test_socketserver.SocketServerTest and test_handle_accept() of test.test_asyncore.TestAPI_UseIPv6Select on FreeBSD buildbots

[STINNER Victor]

STINNER Victor added the comment:

Duplicate of bpo-30319.

--

___
Python tracker 

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

[issue30844] selectors: Add exceptional urgent data event

[STINNER Victor]

STINNER Victor added the comment:

> To be able to use GPIO Sysfs Interface on our embedded platforms we require 
> exceptional event support.

Antoine Pitrou noticed that "exception" term can be confusion in Python, since 
exceptions are like "raise ValueError(...)".

The manual page mentions "out-of-band (OOB) data".

http://man7.org/linux/man-pages/man2/select_tut.2.html

   exceptfds
  This set is watched for "exceptional conditions".  In
  practice, only one such exceptional condition is common: the
  availability of out-of-band (OOB) data for reading from a TCP
  socket.  See recv(2), send(2), and tcp(7) for more details
  about OOB data.  (One other less common case where select(2)
  indicates an exceptional condition occurs with pseudoterminals
  in packet mode; see ioctl_tty(2).)  After select() has
  returned, exceptfds will be cleared of all file descriptors
  except for those for which an exceptional condition has
  occurred.

Is it what you need for a GPIO? GPIO is unrelated to TCP, right?

--
nosy: +haypo

___
Python tracker 

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

[issue30844] selectors: Add exceptional urgent data event

[STINNER Victor]

STINNER Victor added the comment:

http://man7.org/linux/man-pages/man7/tcp.7.html



   Sockets API
   TCP provides limited support for out-of-band data, in the form of (a
   single byte of) urgent data.  In Linux this means if the other end
   sends newer out-of-band data the older urgent data is inserted as
   normal data into the stream (even when SO_OOBINLINE is not set).
   This differs from BSD-based stacks.

   Linux uses the BSD compatible interpretation of the urgent pointer
   field by default.  This violates RFC 1122, but is required for
   interoperability with other stacks.  It can be changed via
   /proc/sys/net/ipv4/tcp_stdurg.

   It is possible to peek at out-of-band data using the recv(2) MSG_PEEK
   flag.

   Since version 2.4, Linux supports the use of MSG_TRUNC in the flags
   argument of recv(2) (and recvmsg(2)).  This flag causes the received
   bytes of data to be discarded, rather than passed back in a caller-
   supplied buffer.  Since Linux 2.4.4, MSG_TRUNC also has this effect
   when used in conjunction with MSG_OOB to receive out-of-band data.

--

___
Python tracker 

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

[issue30844] selectors: Add exceptional urgent data event

[STINNER Victor]

STINNER Victor added the comment:

I don't know anything about OOB data, so I continue to add more pointers :-)

https://en.wikipedia.org/wiki/Out-of-band_data

"Out of band data is a logically independent transmission channel between a 
pair of connected stream sockets."

--

___
Python tracker 

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

[issue30844] selectors: Add exceptional conditions event

[Pim Klanke]

Changes by Pim Klanke :


--
title: selectors: Add exceptional urgent data event -> selectors: Add 
exceptional conditions event

___
Python tracker 

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

[issue30848] test_multiprocessing_forkserver hangs on AMD64 FreeBSD CURRENT Debug 3.x

[STINNER Victor]

New submission from STINNER Victor:

http://buildbot.python.org/all/builders/AMD64%20FreeBSD%20CURRENT%20Debug%203.x/builds/546/steps/test/logs/stdio

...
0:23:06 load avg: 0.73 [402/406] test_multiprocessing_fork passed (84 sec) -- 
running: test_multiprocessing_forkserver (287 sec)
0:23:06 load avg: 0.73 [403/406] test_yield_from passed -- running: 
test_multiprocessing_forkserver (288 sec)
0:23:07 load avg: 0.73 [404/406] test_codecencodings_kr passed -- running: 
test_multiprocessing_forkserver (288 sec)
0:23:09 load avg: 0.84 [405/406] test_urllib2_localnet passed -- running: 
test_multiprocessing_forkserver (291 sec)

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

--
components: Tests
messages: 297671
nosy: haypo
priority: normal
severity: normal
status: open
title: test_multiprocessing_forkserver hangs on AMD64 FreeBSD CURRENT Debug 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

[issue12910] urrlib.quote quotes too many chars, e.g., '()'

[Jörn Hees]

Changes by Jörn Hees :


--
pull_requests: +2638

___
Python tracker 

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

[issue30848] test_multiprocessing_forkserver hangs on AMD64 FreeBSD CURRENT Debug 3.x

[STINNER Victor]

STINNER Victor added the comment:

This buildbot run uses --timeout=900, so test_multiprocessing_forkserver was 
supposed to be killed after 15 minutes by faulthandler, but buildbot had to 
kill it after 20 min. Moreover, the main regrtest process is supposed to log 
"running: ..." messages every 30 secondes, it didn't...

--

___
Python tracker 

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

[issue12910] urrlib.quote quotes too many chars, e.g., '()'

[Jörn Hees]

Jörn Hees added the comment:

It's been a while... nowadays I would mostly change the documentation of the 
quote function to point out that it is likely to quote more characters than 
absolutely necessary by SPEC. The function is in place for so long, (even in 
py3) that people will rely on the behavior.

I made an attempt to update the docstring accordingly in 
https://github.com/python/cpython/pull/2568


What i think is most confusing is the current docs mentioning the reserved 
chars (which are btw. definitely wrong wrt. RFC3986). Actually as one can see 
in the code the reserved chars don't play any role for quote, but much more the 
unreserved chars (called _ALWAYS_SAFE 
https://github.com/python/cpython/blob/master/Lib/urllib/parse.py#L716 ).

   unreserved= ALPHA / DIGIT / "-" / "." / "_" / "~"

The current quote function's approach is to simply quote everything that is not 
in unreserved + safe (per arg).

In that aspect it is quite close to the old javascript.escape function: 
https://www.w3schools.com/jsref/jsref_escape.asp


quick links
py2.7: https://github.com/python/cpython/blob/2.7/Lib/urllib.py#L1261
py3: https://github.com/python/cpython/blob/master/Lib/urllib/parse.py#L745
RFC3986: https://tools.ietf.org/html/rfc3986#appendix-A

--

___
Python tracker 

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

[issue30849] test_stress_delivery_dependent() randomly fails on AMD64 Debian root 3.6

[STINNER Victor]

New submission from STINNER Victor:

Antoine: I told you that such stess-test is going to require work to polish it. 
So here is another example of failure. Enjoy :-)

http://buildbot.python.org/all/builders/AMD64%20Debian%20root%203.6/builds/534/steps/test/logs/stdio


== CPython 3.6.2rc1+ (heads/3.6:580cd5c, Jul 5 2017, 00:47:42) [GCC 4.9.2]
== Linux-3.16.0-4-amd64-x86_64-with-debian-8.7 little-endian
...
== CPU count: 1
...
Run tests in parallel using 2 child processes
0:11:40 load avg: 1.29 [383/405/1] test_signal failed -- running: test_datetime 
(38 sec)
...
==
FAIL: test_stress_delivery_dependent (test.test_signal.StressTest)
--
Traceback (most recent call last):
  File 
"/root/buildarea/3.6.angelico-debian-amd64/build/Lib/test/test_signal.py", line 
1053, in test_stress_delivery_dependent
self.assertEqual(len(sigs), N, "Some signals were lost")
AssertionError: 4602 != 1 : Some signals were lost

==
FAIL: test_stress_delivery_simultaneous (test.test_signal.StressTest)
--
Traceback (most recent call last):
  File 
"/root/buildarea/3.6.angelico-debian-amd64/build/Lib/test/test_signal.py", line 
1086, in test_stress_delivery_simultaneous
self.assertEqual(len(sigs), N, "Some signals were lost")
AssertionError: 8206 != 1 : Some signals were lost

--
assignee: pitrou
components: Tests
messages: 297674
nosy: haypo, pitrou
priority: normal
severity: normal
status: open
title: test_stress_delivery_dependent() randomly fails on AMD64 Debian root 3.6
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

[STINNER Victor]

New submission from STINNER Victor:

See also bpo-30778: "test_bsddb3 crash on x86 Windows XP 2.7".

http://buildbot.python.org/all/builders/AMD64%20Windows8.1%20Refleaks%202.7/builds/40/steps/test/logs/stdio

1:07:30 [145/403/1] test_bsddb3 failed -- running: test_weakref (4038 sec), 
test_io (2487 sec), test_mmap (1406 sec)
test_bsddb3 still working, be patient...
  test_bsddb3 still working, be patient...
  test_bsddb3 still working, be patient...
Berkeley DB 4.7.25: (May 15, 2008)
Test path prefix:  d:\temp\z-test_bsddb3-5156
XXX: timeout happened beforestartup was confirmed - see issue 3892
test test_bsddb3 failed -- Traceback (most recent call last):
  File 
"D:\buildarea\2.7.ware-win81-release.refleak\build\lib\bsddb\test\test_replication.py",
 line 384, in test01_basic_replication
self.assertTrue(time.time()

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

[issue12910] urrlib.quote quotes too many chars, e.g., '()'

[Jörn Hees]

Changes by Jörn Hees :


--
versions: +Python 2.7, Python 3.4, 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

[issue30844] selectors: Add exceptional conditions event

[Antoine Pitrou]

Antoine Pitrou added the comment:

About naming: it is true that the manpage for select() uses the wording 
"exceptional condition".  But the Linux man page for poll() (and by extension 
epoll_wait()) does not use that wording, it says "There is urgent data to 
read".  The POSIX man page for poll() says "High-priority data may be read 
without blocking".

I would not argue about this if this weren't for the fact that "exception" 
already has a different meaning in Python land.  Re-using the term for 
something else is confusing.  Since "urgent data" and "high-priority data" are 
already accepted elsewhere for the same concept, reusing one of them should be 
ok.

--
nosy: +pitrou

___
Python tracker 

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

[issue29406] asyncio SSL contexts leak sockets after calling close with certain Apache servers

[Yury Selivanov]

Yury Selivanov added the comment:

> Yury, based on the most recent comments, can this issue be closed now?

Not sure, I'm reviewing the patch for #30698, let's see if it fixes the problem.

--

___
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

[Brett Cannon]

Brett Cannon added the comment:

My guess is the import of package has completed but package.submodule hasn't (I 
don't know what state it would be in, but obviously before the module is 
assigned as an attribute on the package), a context switch occurs, and then the 
assignment fails due to package.submodule not being set on package yet.

I wonder if package.submodule is in sys.modules when the AttributeError is 
triggered? I don't remember when the assignment of a submodule to an attriute 
on a package occurs, but this suggests it's rather late and that's why this is 
failing. Maybe the assignment is outside of the per-module lock being released 
and that is what's causing this?

Hey, at least importing in a thread doesn't deadlock anymore like it used to. ;)

--

___
Python tracker 

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

[issue30828] Out of bounds write in _asyncio_Future_remove_done_callback

[Yury Selivanov]

Changes by Yury Selivanov :


--
pull_requests: +2640

___
Python tracker 

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

[issue30726] [Windows] Warnings in elementtree due to new expat

[Segev Finer]

Changes by Segev Finer :


--
pull_requests: +2641

___
Python tracker 

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

[issue30726] [Windows] Warnings in elementtree due to new expat

[Segev Finer]

Changes by Segev Finer :


--
pull_requests: +2642

___
Python tracker 

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

[issue30726] [Windows] Warnings in elementtree due to new expat

[Segev Finer]

Segev Finer added the comment:

Python 2.7 diverged 
https://github.com/python/cpython/commit/ab3b0ade505ce07a3d5ec4fbc991a154242732e6.
 It's only missing _CRT_SECURE_NO_WARNINGS. :P

--

___
Python tracker 

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

[issue30726] [Windows] Warnings in elementtree due to new expat

[Segev Finer]

Changes by Segev Finer :


--
pull_requests: +2643

___
Python tracker 

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

[issue30794] Add multiprocessing.Process.kill()

[Vitor Pereira]

Vitor Pereira added the comment:

Hey, I submitted a PR and just signed the CLA. If you could please take a look. 
Thanks!

--

___
Python tracker 

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

[issue30726] [Windows] Warnings in elementtree due to new expat

[STINNER Victor]

STINNER Victor added the comment:


New changeset d02c8416fe1b29b3322004b73133bf6c8a2e353a by Victor Stinner (Segev 
Finer) in branch '3.6':
[3.6] bpo-30726: Also fix pyexpat.vcxproj (GH-2375) (#2570)
https://github.com/python/cpython/commit/d02c8416fe1b29b3322004b73133bf6c8a2e353a


--

___
Python tracker 

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

[issue30726] [Windows] Warnings in elementtree due to new expat

[STINNER Victor]

STINNER Victor added the comment:


New changeset d0ae4be443332d63fafb304944842fbaece734a3 by Victor Stinner (Segev 
Finer) in branch '2.7':
bpo-30726: Add _CRT_SECURE_NO_WARNINGS to _elementtree and pyexpat projects 
(#2572)
https://github.com/python/cpython/commit/d0ae4be443332d63fafb304944842fbaece734a3


--

___
Python tracker 

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

[issue30726] [Windows] Warnings in elementtree due to new expat

[STINNER Victor]

STINNER Victor added the comment:


New changeset 320ee67f981f766ff55c55ef87d5ef17ce297824 by Victor Stinner (Segev 
Finer) in branch '3.5':
[3.5] bpo-30726: Also fix pyexpat.vcxproj (GH-2375) (#2571)
https://github.com/python/cpython/commit/320ee67f981f766ff55c55ef87d5ef17ce297824


--

___
Python tracker 

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

[issue30794] Add multiprocessing.Process.kill()

[Antoine Pitrou]

Antoine Pitrou added the comment:

Thank you Vitor! I posted some review comments on your PR.

--

___
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

[Antoine Pitrou]

Changes by Antoine Pitrou :


--
priority: normal -> high

___
Python tracker 

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

[issue30726] [Windows] Warnings in elementtree due to new expat

[STINNER Victor]

STINNER Victor added the comment:

Thanks Segev Finer for backports.

--

___
Python tracker 

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

[issue30726] [Windows] Warnings in elementtree due to new expat

[STINNER Victor]

Changes by STINNER Victor :


--
resolution:  -> fixed
stage: backport needed -> 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

[issue30726] [Windows] Warnings in elementtree due to new expat

[STINNER Victor]

STINNER Victor added the comment:

> It doesn't even fix a warning - only suppresses it. Since there is no 
> behavior change at all, I'm not inclined to backport any further than is 
> trivial.

I like decreasing the number of warnings. It helps to detect new warnings, and 
so to prevent bugs.

--

___
Python tracker 

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

[issue30726] [Windows] Warnings in elementtree due to new expat

[Steve Dower]

Steve Dower added the comment:

> I like decreasing the number of warnings. It helps to detect new warnings, 
> and so to prevent bugs.

The approach used to suppress this warning will also suppress other warnings 
that might be fixable. Hard to say it's definitely a good thing in this case, 
though in general I agree that selectively suppressing warnings that cannot be 
fixed is a good thing.

--

___
Python tracker 

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

[issue30726] [Windows] Warnings in elementtree due to new expat

[Segev Finer]

Segev Finer added the comment:

> The approach used to suppress this warning will also suppress other warnings 
> that might be fixable. Hard to say it's definitely a good thing in this case, 
> though in general I agree that selectively suppressing warnings that cannot 
> be fixed is a good thing.

Most secure CRT warnings are a bit useless in portable code since you are 
unlikely to really use strcpy_s and friends...

--

___
Python tracker 

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

[issue1612262] Class Browser doesn't show internal classes

[Cheryl Sabella]

Changes by Cheryl Sabella :


--
pull_requests: +2644

___
Python tracker 

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

[issue27636] Refactor IDLE htest

[Terry J. Reedy]

Terry J. Reedy added the comment:

Htest should extract version from __file__, and module from spec, and display 
both.

--
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

[issue21624] Idle: Improve htests

[Terry J. Reedy]

Terry J. Reedy added the comment:

Current htest issues from this and two other issues, notes, and running htests 
with htest.py.

(Default master window placement is ok.  Can move.)

h1. At least one test window overlaps the test window. Others are not centered 
(y-position). Fix by passing _htest and changing geometry accordingly.  Use 
f-strings.  Develop formula for centering?

(Test messages "might use editing" is too vague.  Ditto for EditorWindow 'might 
be split'.)

h2. All widgets should be displayed.  A couple of htests test behavior in 
widgets otherwise displayed, and *these* should be unittested if possible.

h3. Force focus to opened widget window.  Probably still needed.

h4. Putting imports only needed by htest functions in the function is a good 
idea.  Introducing a regression by mistake is not.  Do this when edit after 
thorough tests.

h5. # htest # is present on all current htest functions. Check that is 
documented, including .coveragerc entry.

h6. What is left from #22629 after patch applied?

h7. #27636: incapsulate common features in classes defined in htest.py.

3 Specific TODOs in htest.py:

h8. Improve message for dyn_option_menu.

h9. Improve wrapper for EditorWindow.

h10. Update GetKeysDialog test now that #21519 closed.

h11. My note: Get keys dialog prints blank line to console, something prints 
'None'. Check when run all tests.

h12. Test window should show version and module (from __file__).  Make part of 
#27636.

--
dependencies: +Idle: update htest.py and htests, Refactor IDLE htest
title: Idle: polish htests -> Idle: Improve htests

___
Python tracker 

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

[issue30851] IDLE: configdialog -- fix tkinter Variables

[Terry J. Reedy]

New submission from Terry J. Reedy:

As part of #30777, Cheryl Sabella listed Variables defined for a tab page, and 
the use thereof, in the docstring for the tab page.  This revealed some 
anomalies.

Duplicate: font_name is defined on font and highlight pages.  The first 
StringVariable should be attached to a widget before the name is rebound.  We 
should investigate after there are tests for the two pages.

Unused: for anything deleted, make sure that there is no corresponding trace 
function left.

binding_target (keys) sounds like something that was never an external option 
but just an internal implementation detail; delete.

encoding (general) *is* an external option, but I believe used only by 2.x.  
Recheck (in config.py also) and probably delete.

user_help_browser and help_browser (general) may have once been options.  We 
now use the system browser, which, at least on some systems, users can set.  
Delete.

--
assignee: terry.reedy
components: IDLE
messages: 297692
nosy: csabella, terry.reedy
priority: normal
severity: normal
stage: needs patch
status: open
title: IDLE: configdialog -- fix tkinter Variables
type: behavior
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

[issue30851] IDLE: configdialog -- fix tkinter Variables

[Terry J. Reedy]

Changes by Terry J. Reedy :


--
dependencies: +IDLE: configdialog - add tests for ConfigDialog GUI.

___
Python tracker 

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

[issue30777] IDLE: configdialog -- add docstrings and improve comments

[Terry J. Reedy]

Terry J. Reedy added the comment:


New changeset 7eb5883ac59833bf63f0e1f7fb95671a1ac1ee08 by terryjreedy 
(csabella) in branch 'master':
bpo-30777: IDLE: configdialog - add docstrings and improve comments (#2440)
https://github.com/python/cpython/commit/7eb5883ac59833bf63f0e1f7fb95671a1ac1ee08


--

___
Python tracker 

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

[issue21624] Idle: Improve htests

[Terry J. Reedy]

Changes by Terry J. Reedy :


--
pull_requests: +2645

___
Python tracker 

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

[issue21624] Idle: Improve htests

[Terry J. Reedy]

Terry J. Reedy added the comment:


New changeset 2000150c569941584994ec4ec59171961209bec3 by terryjreedy in branch 
'master':
bpo-21624: IDLE -- minor htest fixes (#2575)
https://github.com/python/cpython/commit/2000150c569941584994ec4ec59171961209bec3


--

___
Python tracker 

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

[issue30777] IDLE: configdialog -- add docstrings and improve comments

[Terry J. Reedy]

Changes by Terry J. Reedy :


--
pull_requests: +2646

___
Python tracker 

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

[issue30777] IDLE: configdialog -- add docstrings and improve comments

[Terry J. Reedy]

Changes by Terry J. Reedy :


--
pull_requests: +2647

___
Python tracker 

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

[issue21624] Idle: Improve htests

[Terry J. Reedy]

Changes by Terry J. Reedy :


--
pull_requests: +2648

___
Python tracker 

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

[issue30777] IDLE: configdialog -- add docstrings and improve comments

[Terry J. Reedy]

Changes by Terry J. Reedy :


--
pull_requests: +2649

___
Python tracker 

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

[issue30441] os.environ raises RuntimeError: dictionary changed size during iteration

[Osvaldo Santana Neto]

Osvaldo Santana Neto added the comment:

Hi Serhiy Storchaka,

I need to thank you for your valuable guidance.

--

___
Python tracker 

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