On Sep 25, 2013, at 10:20 PM, Hynek Schlawack wrote:
>> What tools actually make use of this file?
>
> pip install -r dev-requirements.txt
OK. If this is the way that this file is intended to be used, perhaps there
should be a comment explaining that at the top :).
-glyph_
On Sep 25, 2013, at 11:05 PM, Daniel Sank wrote:
> This isn't THAT bad. The client's requestMove is thin and unecessary (I put
> it there for illustration). Still I need to have two separate classes with
> corresponding methods to handle moving the piece.
That's OK. Don't try to reduce your n
Quick question about (sub)processes in twisted :
how bad is it to use the subprocess module ? ( in general / in this
application )
I have the following setup :
- Twisted Daemon that does 5 things (very well!)
- A new requirement -- to execute 2 scripts on the commandli
On Sep 26, 2013, at 6:51 PM, Jonathan Vanasco wrote:
>
> Quick question about (sub)processes in twisted :
>
> how bad is it to use the subprocess module ? ( in general / in this
> application )
It's pretty bad ;-).
> I have the following setup :
>
> - Twisted Daemon that does
> If anything, you should have an additional class to separate out your
remote_* responders and the actual internal state.
Indeed.
> I don't know if this is going to *directly* address any of your concerns,
but have you considered using twisted.spread.flavors.Cacheable?
This is funny. I read the
On Sep 26, 2013 8:18 PM, "Glyph" wrote:
>
>
> On Sep 26, 2013, at 6:51 PM, Jonathan Vanasco
wrote:
>
> Could you write up why you feel it's "annoying"? Maybe we can improve
spawnProcess so it works better for you in the future.
I'm also interested in what you feel is annoying. Please write this
Upon re-reading the Cacheable docs I still don't understand how to use
it. Can we take my previous home-brewed example and use that as a
launch point for illustrating how to use Cacheable? Here's the
example.
We assume the client has a PlayerClient instance with .server pointing
to a PlayerServer
