tcpserver should document non-threaded long-living connections

Open
#57,563 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
documentation

Research direction

Start by reviewing Python's existing tcpserver documentation and the migrated BPO issue 13354 to identify the relevant documentation entry point and the missing behavior description. Done means the documentation clearly explains non-threaded, long-lived connections; the payload names no specific file or test to run.

Written by the indexing model from the issue text.

Description

docs topic-socket type-feature
BPO 13354
Nosy @vadmium

Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

Show more details

GitHub fields:

assignee = None
closed_at = None
created_at = <Date 2011-11-06.09:10:11.132>
labels = ['type-feature', 'docs']
title = 'tcpserver should document non-threaded long-living connections'
updated_at = <Date 2016-02-20.08:48:52.038>
user = 'https://bugs.python.org/shevek'

bugs.python.org fields:

activity = <Date 2016-02-20.08:48:52.038>
actor = 'shevek'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2011-11-06.09:10:11.132>
creator = 'shevek'
dependencies = []
files = []
hgrepos = []
issue_num = 13354
keywords = []
message_count = 6.0
messages = ['147147', '221787', '260534', '260546', '260558', '260562']
nosy_count = 3.0
nosy_names = ['shevek', 'docs@python', 'martin.panter']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue13354'
versions = ['Python 3.2']

Dominant language
Python
Stars
77.2k
Forks
36k
Avg merge
1d 9h
Merged PRs (30d)
558

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.

More from python/cpython

All issues in python/cpython

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.