ambiguous _max_size parameter in SpooledTemporaryFile
Open
Nobody has claimed this yet.
3.7 (EOL)
3.8 (EOL)
3.9 (EOL)
docs
stdlib
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 34446 |
|---|---|
| Nosy | @brettcannon, @lurch |
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 2018-08-20.19:47:35.501>
labels = ['type-bug', '3.8', '3.9', '3.7', 'library', 'docs']
title = 'ambiguous _max_size parameter in SpooledTemporaryFile'
updated_at = <Date 2019-07-07.15:58:26.019>
user = 'https://bugs.python.org/jcc2220'
bugs.python.org fields:
activity = <Date 2019-07-07.15:58:26.019>
actor = 'lurchman'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation', 'Library (Lib)']
creation = <Date 2018-08-20.19:47:35.501>
creator = 'jcc2220'
dependencies = []
files = []
hgrepos = []
issue_num = 34446
keywords = []
message_count = 4.0
messages = ['323809', '323845', '323850', '347475']
nosy_count = 4.0
nosy_names = ['brett.cannon', 'docs@python', 'lurchman', 'jcc2220']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue34446'
versions = ['Python 2.7', 'Python 3.5', 'Python 3.6', 'Python 3.7', 'Python 3.8', 'Python 3.9']
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the documentation entry for tempfile.SpooledTemporaryFile and review how the _max_size parameter is described. Clarify the parameter's meaning and behavior so readers can distinguish its purpose; done means the documentation is no longer ambiguous. Check the existing documentation build or relevant library documentation tests if available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100