> I'll probably need a bit of guidance on intent here.
The intent is to pull the fake-juju bits out of txjuju.testing and into a more useful fakejuju library here.
> # seems to pull in fakejuju/__init__.py fine into the build directory.
> cd python; python setup.py build
>
>
> although python setup.py test chokes trying to find a distribution of txjuju,
> how will we be pulling txjuju dependencies?
"python setup.py test"? Does that come for free? There aren't any tests in this patch. You are correct that setup.py won't work as-is. I'm okay with that. :) As long as the deb package works we're fine. The setup.py is mostly informational and useful for building the initial deb packaging code.
> I'll probably need a bit of guidance on intent here.
The intent is to pull the fake-juju bits out of txjuju.testing and into a more useful fakejuju library here.
> # seems to pull in fakejuju/ __init_ _.py fine into the build directory.
> cd python; python setup.py build
>
>
> although python setup.py test chokes trying to find a distribution of txjuju,
> how will we be pulling txjuju dependencies?
"python setup.py test"? Does that come for free? There aren't any tests in this patch. You are correct that setup.py won't work as-is. I'm okay with that. :) As long as the deb package works we're fine. The setup.py is mostly informational and useful for building the initial deb packaging code.