Fair enough. I've updated my two forks with an extra option in the
setup.cfg file that uses a different build directory to solve that problem.
I have no issue with using pants or or not (so long as vanilla setuptools
works), though I was having issues getting pants to use these forks (via
the git s
They can be installed via setuptools -- the repositories have setup.py
files included at the root so that source distributions can be made.
Nothing's been published to pypi yet though, since I don't feel they're
even ready for an 0.1 release. I pantsified the repositories to make it
easier to run
R.E Python 3.3;
It doesn't actually require it, but it's importing asyncio directly instead of
using the standard try/catch around the import and falling back to trollius
(the Python2 port). We can probably import via tornado, which does this
try/catch for us.
Right now both compactor and peso
Hey!
Thanks for the reply. After a painful few days I managed to narrow it down to
an error (that was being swallowed, grr!!) as a result of an implementation bug
in Tornado (the python library we're using for the libprocess http service).
I've since submitted a patch here
https://github.com/t
Hi, Tom!
I would gladly help you to debug if you could provide some information
about your setup. Is it localhost only communication? Any code snippet to
reproduce the problem?
P.S. I'm trying to setup pesos and it seems like python3.3 is a requirement
but it isn't mentioned anywhere.
On Tue, Ju
Hey,
I've started to try and finish off the work @wickman started around pesos[1]
and compactor[2] - pure language bindings for mesos and libprocess in Python.
It's currently far from finished, but have fun into a brick wall around
libprocess. If anyone could shed any light that'd be great.
To
