ftplib doesn't check close status after sending file
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- networking
Research direction
Start with the ftplib library implementation and inspect PR #30747, which is already associated with this issue. Review the existing behavior around sending a file and its close status, then use the repository's ftplib tests to verify the intended fix.
Written by the indexing model from the issue text.
Description
| BPO | 10202 |
|---|---|
| Nosy | @loewis, @gpshead, @pitrou, @giampaolo, @ethanfurman, @MaxwellDupre |
| PRs |
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 2010-10-26.19:04:47.990>
labels = ['type-bug', 'library', '3.9', '3.10', '3.11']
title = "ftplib doesn't check close status after sending file"
updated_at = <Date 2022-01-21.13:23:44.836>
user = 'https://bugs.python.org/nagle'
bugs.python.org fields:
activity = <Date 2022-01-21.13:23:44.836>
actor = 'mikecmcleod'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2010-10-26.19:04:47.990>
creator = 'nagle'
dependencies = []
files = []
hgrepos = []
issue_num = 10202
keywords = ['patch']
message_count = 10.0
messages = ['119638', '119652', '119658', '119669', '119685', '119720', '119788', '406207', '409157', '410644']
nosy_count = 8.0
nosy_names = ['loewis', 'gregory.p.smith', 'exarkun', 'nagle', 'pitrou', 'giampaolo.rodola', 'ethan.furman', 'mikecmcleod']
pr_nums = ['30747']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue10202'
versions = ['Python 3.9', 'Python 3.10', 'Python 3.11']
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
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.
More from python/cpython
-
docs pending
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
build type-bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
stdlib topic-email type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100