get/set_payload deprecated, but get_set_content do not provide full replacement functionality
Open
Nobody has claimed this yet.
3.10
topic-email
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 41599 |
|---|---|
| Nosy | @warsaw, @bitdancer |
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 2020-08-20.09:40:49.607>
labels = ['type-bug', 'expert-email', '3.10']
title = 'get/set_payload deprecated, but get_set_content do not provide full replacement functionality'
updated_at = <Date 2020-08-20.09:40:49.607>
user = 'https://bugs.python.org/equaeghe'
bugs.python.org fields:
activity = <Date 2020-08-20.09:40:49.607>
actor = 'equaeghe'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['email']
creation = <Date 2020-08-20.09:40:49.607>
creator = 'equaeghe'
dependencies = []
files = []
hgrepos = []
issue_num = 41599
keywords = []
message_count = 1.0
messages = ['375696']
nosy_count = 3.0
nosy_names = ['barry', 'r.david.murray', 'equaeghe']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue41599'
versions = ['Python 3.10']
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
The payload names get/set_payload and get_set_content in the email component but identifies no files or tests. Start by tracing these APIs and comparing the deprecated behavior with the proposed replacement methods. The intended missing functionality and compatibility expectations need clarification before completion can be verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100