IRC Logs for #circuits Thursday, 2013-01-03

*** irclogger_ has joined #circuits07:48
*** Osso has joined #circuits07:53
*** Osso has quit IRC10:42
*** Osso has joined #circuits10:50
*** Osso has quit IRC10:59
jgiorgi....12:53
jgiorgiinteresting12:53
jgiorgiprologic: so call/wait is stable? is circuits-dev relatively bug free?14:00
*** Osso has joined #circuits14:30
*** Osso has quit IRC14:35
prologicjgiorgi, it is15:42
prologicand by relatively we mean all unit tests pass15:42
prologicwe always focus on keeping unit tests passing15:42
jgiorgiso the proper way to get the result of an event is...?16:48
prologicx = self.fire(...)18:55
jgiorgiyes but if i recall correctly that isnt an instantaneous return19:30
jgiorgiit returns a Value object which until the event propagates has no value19:30
prologiccorrect20:39
prologicit's called a promise20:39
prologicyou have to wait until the event has fired20:39
prologicyield self.wait(...)20:39
prologicor explicitly call it with20:39
prologicyield self.call(...)20:40
prologicotherwise you can set .notify = True on the event object and listen for the foo_changed event20:40
prologichttp://pypi.python.org/pypi/pulsar21:06
prologic*sigh*21:06
prologicsometimes I wonder what need circuits fills21:06
prologichah!21:15
prologicpulsar's hello world wsgi app21:15
prologic193reqs/s concurrency 10021:15
prologiccircuits.web 503req/s same concurrency21:15
prologiccircuits obviously is pure python all the way21:15
prologicpulsar has a C http_parser module21:16
prologichah!21:16
jgiorgigot disconnected, not sure which, if any of my messages actually got sent21:23
jgiorgi<jgiorgi> so x = yield self.call(Event())21:23
jgiorgi<jgiorgi> would get the Value object (x) and wait until the event had propagated before continuing with the application?21:23
jgiorgi<jgiorgi> s/application/handler21:23
prologicwell21:24
prologicbefore resuming at that point in the handler - yes21:24
prologicthe system still lives on21:24
prologichttp://codepad.org/2fcVDS5i21:28
prologic^^^ For example21:28
prologicOr:21:30
prologichttp://codepad.org/KZPVijgb21:30
*** platzhirsch has joined #circuits23:20
platzhirschcandy got me here23:20
platzhirschprologic: so what would be the class/function I have to look for when I want to watch a file?23:21
platzhirschlooks like I need circuits.io.file.File23:24
prologichaha23:34
prologiccandy23:34
prologicI'm back23:34
prologiccircuits.io.Notify is what you want23:34
prologicit's a Component that wraps the pyinotify functionality23:34
prologicobviously only works on systems that support inotify23:35
prologicso I hope you don't plan on running this on Windows :023:35
platzhirschwish there would be some more examples in the docs :)23:35
prologicnot in docs23:35
platzhirschno, motion is only available in unix as far as I know23:35
prologicbut in examples/dirwatch.py23:35
prologicjust a simple directory watcher23:35
prologicand just spits out the events as they come in23:35
prologiceg:23:35
prologicpython examples/dirwatch.py /tmp23:36
prologicecho "1" > /tmp/foo23:36
prologicdocs only covers most of the circuits.core and circuits.web23:36
prologicI imagine you'll want to be using23:38
prologiccircuits.web with a simple set of controlelrs23:38
prologicplus the circuits.io.Notify component23:38
prologicand maybe think about (if not already) separating out your logic in distinct components23:38
platzhirschthat's really nice, covers most of the requirements23:39
prologicwe try23:40
prologicthe only con for circuits right now is networking protocols23:40
prologicof which we have few23:40
prologicand if you succeed with circuits + <your app>23:41
prologicyou must tell us about it so we can write up a bit of a blurb :)23:41
platzhirsch:)23:45

Generated by irclog2html.py 2.11.0 by Marius Gedminas - find it at mg.pov.lt!