Consider a possible "methods-based" interface.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4.8k
- Forks
- 254
- Avg merge
- 10h 35m
- Merged PRs (30d)
- 9
Description
I have heard it said that plotnine is "not Pythonic". I explore this claim here and I conclude that perhaps the claim is strongest with the need to either say from plotnine import * (or at least from plotnine import [lots of things]) or make the code ugly with import plotnine as p9 and then p9.ggplot(p9.aes()) + p9.geom() + ....
With the help of Codex, I made a feature branch that provides a more "methods-based" interface on a fork here. The code changes seem quite non-invasive.
I think the "methods-based" code looks quite Pythonic. I also made a demo site here and everything seems to "just work" so far.
Contributor guide
No contributing guide indexed for this repository
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 reviewing the linked codex-fluent-api feature branch and the demo site, then compare its methods-based interface with plotnine's current public API. The issue provides no repository files or tests to target; done would require defining and agreeing on the intended interface and its scope before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-visualization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100