Deal with the case when `.attrs`/`.uns` are not JSON-serializable
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 394
- Forks
- 95
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 7
Description
See context here: #data-structures > JSON in `uns`.
Status:
.attrsinpandas(hence ingeopandasanddask.dataframe) are JSON-serializable, as shown here.- In
SpatialDatawe can enforce that. - In
xarraythis needs to be investigated. - In
AnnDatathis will be the case only if a certain option is toggled, see discussion here#data-structures > JSON in `uns` @ 💬.
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 linked Zulip discussions and the issue's notes on pandas, SpatialData, xarray, and AnnData. Investigate how non-JSON-serializable values in .attrs and .uns should be handled across these cases, then define and test the agreed behavior; the issue is complete when the supported policy is implemented and its constraints are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- pandas, python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100