bpo-31647: Fix write_eof() after close() for SelectorSocketTransport by twisteroidambassador · Pull Request #7149 · python/cpython

twisteroidambassador

added 2 commits

May 28, 2018 18:41

Fixed bug where calling write_eof() on a _SelectorSocketTransport after
it's already closed raises AttributeError.

Added a test case for calling write_eof() after close() on
_SelectorSocketTransport.

twisteroidambassador changed the title ~~bpo-31467: Fix write_eof() after close() for SelectorSocketTransport~~ bpo-31647: Fix write_eof() after close() for SelectorSocketTransport

May 28, 2018

1st1 approved these changes May 28, 2018

miss-islington pushed a commit to miss-islington/cpython that referenced this pull request

May 28, 2018

…ythonGH-7149)

Fixed bug where calling write_eof() on a _SelectorSocketTransport after
it's already closed raises AttributeError.
(cherry picked from commit 23f587e)

Co-authored-by: twisteroid ambassador <twisteroidambassador@users.noreply.github.com>

miss-islington pushed a commit to miss-islington/cpython that referenced this pull request

May 28, 2018

…ythonGH-7149)

Fixed bug where calling write_eof() on a _SelectorSocketTransport after
it's already closed raises AttributeError.
(cherry picked from commit 23f587e)

Co-authored-by: twisteroid ambassador <twisteroidambassador@users.noreply.github.com>

1st1 pushed a commit that referenced this pull request

May 28, 2018

…H-7149) (GH-7153)

Fixed bug where calling write_eof() on a _SelectorSocketTransport after
it's already closed raises AttributeError.
(cherry picked from commit 23f587e)

Co-authored-by: twisteroid ambassador <twisteroidambassador@users.noreply.github.com>

1st1 pushed a commit that referenced this pull request

May 28, 2018

…H-7149) (#7154)

Fixed bug where calling write_eof() on a _SelectorSocketTransport after
it's already closed raises AttributeError.
(cherry picked from commit 23f587e)

Co-authored-by: twisteroid ambassador <twisteroidambassador@users.noreply.github.com>