JuliaPy / JuliaPy/PythonPlot.jl
only use tkagg or agg backends?
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 85
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
Nowadays the Tk backend works pretty well and is available everywhere. Maybe we should just use it (or the Agg backend for non-interactive code) and drop support for all of the other backends (which complicate the code a lot for not much benefit).
@PaulSoderlind, you mentioned wanting the Qt5 backend; could you elaborate?
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
No files, tests, or entry points are named. First clarify whether the project should support only Tk and Agg or also Qt5, then review how backend selection currently works. The work is complete only when the supported-backend policy is decided and its implications for existing backend support are addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia, matplotlib
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100