announce that backend switches based on display capabilities and/or allow override
- Lingua principale
- Julia
- Stelle
- 488
- Fork
- 90
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
Even though I've been using PyPlot for a long time, I was caught by surprise today. I'm running it in Juno, but for whatever reason, PyPlot's output was not being displayed in the Juno plot pane. I was trying to manually set the backend, but it gets overriden by the following
https://github.com/JuliaPy/PyPlot.jl/blob/c1943a96b6754134c7ae1e3147d901011aa7326d/src/init.jl#L211-L214
I don't really know a great way to handle this, because the switching behavior is certainly aiming to give a user-friendly it-just-works experience. So perhaps it would just be good to be able to override the override of the backend, regardless of the display capabilities.
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Direzione di ricerca
Start by reading src/init.jl around lines 211-214, where the backend is selected based on display capabilities. Trace how that selection affects PyPlot output in Juno and determine how a user override should interact with it; done means the requested backend can be preserved or the switching behavior is clearly announced.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- julia, python
- Ambito
- data-visualization
- Tipo di issue
- Funzionalità
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 35/100