mars-project / mars-project/mars
Allow not to specify `dtypes` for `df.apply`, `df.groupby().apply` and so forth.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.7k
- Forks
- 325
- PR merge metrics
- No merged PRs in 30d
Description
For now, if dtypes not specified, and inference failed, user will be told to specify dtypes, otherwise error happens.
Now, we added the ability that if dtypes is unknown, an error be raised to ask user to trigger execute which introduced in #2355 , we can allow not to specify dtypes for df.apply and so forth.
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 by reading the df.apply and df.groupby().apply entry points, then review the execute behavior introduced in #2355. Trace what happens when dtypes is omitted or remains unknown, and use the existing inference-failure path to define the expected behavior. Done means these apply variants can omit dtypes and direct the user to execute when inference cannot determine them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100