U ÷Õ/eã@sNddlmZddlZddlmZGdd„dƒZdd„Zedd „ƒZd d „ZdS) é)Ú annotationsN)Úwithout_property_validationc@s eZdZdZdd„Zdd„ZdS)ÚDashboardComponentaTBase class for Dask.distributed UI dashboard components. This class must have two attributes, ``root`` and ``source``, and one method ``update``: * source: a Bokeh ColumnDataSource * root: a Bokeh Model * update: a method that consumes the messages dictionary found in distributed.bokeh.messages cCsd|_d|_dS©N)ÚsourceÚroot)Úself©r úM/tmp/pip-unpacked-wheel-g426oqom/distributed/dashboard/components/__init__.pyÚ__init__szDashboardComponent.__init__cCsdS)z=Reads from bokeh.distributed.messages and updates self.sourceNr )rÚmessagesr r r ÚupdateszDashboardComponent.updateN)Ú__name__Ú __module__Ú __qualname__Ú__doc__r r r r r r rs rcs,t |¡‰| ‡fdd„|¡t||ƒdS)a²Add periodic callback to doc in a way that avoids reference cycles If we instead use ``doc.add_periodic_callback(component.update, 100)`` then the component stays in memory as a reference cycle because its method is still around. This way we avoid that and let things clean up a bit more nicely. TODO: we still have reference cycles. Docs seem to be referred to by their add_periodic_callback methods. cstˆƒSr©r r ©Úrefr r Ú)óz'add_periodic_callback..N)ÚweakrefrÚadd_periodic_callbackÚ_attach)ÚdocÚ componentÚintervalr rr rs rcCs|ƒ}|dk r| ¡dSrr)rÚcompr r r r -sr cCs"t|dƒstƒ|_|j |¡dS)NÚ components)ÚhasattrÚsetrÚadd)rrr r r r4s r) Ú __future__rrZbokeh.core.propertiesrrrr rr r r r Ús