Improving link and dlink
- Lingua principale
- Python
- Stelle
- 653
- Fork
- 217
- Merge medio
- 2g 21h
- PR unite (30g)
- 2
Descrizione
`link` and `dlink` are good for simple uses, but lack certain features
1) They are not compatible with `Output` widgets, making debugging a lot harder, see https://github.com/jupyter-widgets/ipywidgets/issues/2306
2) They contain redundant code
3) They are built around the "lock" pattern, but in an ad-hoc way: there's no context manager. Such a thing would be quite useful for a user needing a slightly more sophisticated linking pattern, say, linking a 2-Tuple trait with 2 Tuple traits, etc.
Is there any interest adding some optional arguments to link and dlink, and creating a `Lock` context manager?
I would be happy to do a PR
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Start by reviewing the current `link` and `dlink` implementations and the Output compatibility discussion in ipywidgets#2306. Compare their duplicated locking behavior, then clarify the optional-argument and `Lock` API scope with maintainers; completion would require an agreed design and corresponding tests.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- python
- Ambito
- tooling
- Tipo di issue
- Funzionalità
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 25/100