IronLanguages / IronLanguages/ironpython3

Closing a socket does not clear the fileno

Open
#1,221 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

module-socket
Dominant language
C#
Stars
2.8k
Forks
316
Avg merge
1d 9h
Merged PRs (30d)
1

Description

To reproduce:

import _socket
s = _socket.socket()
s.close()
assert s.fileno() == -1

Causes failures in test_socket and test_socketserver.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the _socket.socket close and fileno behavior shown in the reproduction, then run the affected test_socket and test_socketserver tests to observe the failures. Done means a closed socket reports fileno() as -1 and both tests pass.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, python
Domain
networking
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.