On Wed, Jul 27, 2011 at 5:42 PM, James Westby <email address hidden> wrote:
> Review: Needs Fixing
> 6 -test_command=python -m subunit.run $IDLIST
> 7 +test_command=PYTHONPATH=`pwd` python -m subunit.run $IDLIST
>
> Is that not implicit?
>
Well, sort of. It's there so that the spawned backend scripts will
have the top-level of the tree in their PYTHONPATH, so that they will
use the development version of pkgme libs instead of the system
installed one.
> 41 + stdout, stderr = proc.communicate()
>
> Perhaps we want to do something with the returncode? Also reporting the
> stdout, stderr if it fails?
>
> Also, I think it should use that new logging framework that some bright spark
> wrote to log a message about what it is doing.
>
Good calls both. Will address.
> We're going to want to do something with GPG keys as well, but I'm fine deferring
> that for now.
>
On Wed, Jul 27, 2011 at 5:42 PM, James Westby <email address hidden> wrote: python -m subunit.run $IDLIST PYTHONPATH= `pwd` python -m subunit.run $IDLIST
> Review: Needs Fixing
> 6 -test_command=
> 7 +test_command=
>
> Is that not implicit?
>
Well, sort of. It's there so that the spawned backend scripts will
have the top-level of the tree in their PYTHONPATH, so that they will
use the development version of pkgme libs instead of the system
installed one.
> 41 + stdout, stderr = proc.communicate()
>
> Perhaps we want to do something with the returncode? Also reporting the
> stdout, stderr if it fails?
>
> Also, I think it should use that new logging framework that some bright spark
> wrote to log a message about what it is doing.
>
Good calls both. Will address.
> We're going to want to do something with GPG keys as well, but I'm fine deferring
> that for now.
>
Agreed. Was thinking that. Should have said it.
jml