There is no way to json encode object to str.
Open
Nobody has claimed this yet.
stdlib
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 42791 |
|---|---|
| Nosy | @rhettinger, @ezio-melotti, @iritkatriel |
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-12-30.20:22:51.914>
labels = ['library']
title = 'There is no way to json encode object to str.'
updated_at = <Date 2021-08-31.20:34:24.741>
user = 'https://bugs.python.org/kaltovichartyom'
bugs.python.org fields:
activity = <Date 2021-08-31.20:34:24.741>
actor = 'iritkatriel'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2020-12-30.20:22:51.914>
creator = 'kaltovichartyom'
dependencies = []
files = []
hgrepos = []
issue_num = 42791
keywords = []
message_count = 2.0
messages = ['384085', '400776']
nosy_count = 4.0
nosy_names = ['rhettinger', 'ezio.melotti', 'iritkatriel', 'kaltovichartyom']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue42791'
versions = []
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 issue names only the Library (Lib) component and does not identify a file, test, or expected API. Start by reviewing the standard-library JSON encoding entry points and the original BPO discussion; clarify the desired object-to-string behavior and define tests that demonstrate the intended result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100