Re: Accessible Command Output using self.stdout & self.stderr

2010-08-01 Thread maxweld
On Aug 1, 6:47 pm, Eric Holscher wrote: > You need to pass in your custom stdout into the call_command function. You > can see[1] where it takes those inputs and assigns them to your provided > values. Thanks Eric - that made sense and test is now working. Is there any way to supply a response

Re: Accessible Command Output using self.stdout & self.stderr

2010-08-01 Thread Eric Holscher
> > > Q1. Should I create a separate, new module with my tests in it, or > just add tests to an existing module? If an existing one, how do I > determine which one? > It depends if your work is similar to anything else that is already in the repository. I don't think that the stdout and stdin chan

Re: Accessible Command Output using self.stdout & self.stderr

2010-08-01 Thread maxweld
Hi Russ Ok - so I have a Git repository with Django trunk in it, and have proceeded to change the commands. Following the changes there are no failures in the regression tests. I am now trying to add new tests to prove that my changes actually work. Here is where I run into a few problems, no dou

Re: Accessible Command Output using self.stdout & self.stderr

2010-07-16 Thread burc...@gmail.com
Hi guys, To support http://code.djangoproject.com/ticket/13476 , it'd be great if someone converted current prints to use self.stdout and self.stderr. Alternative suggestions are welcome... On Fri, Jul 16, 2010 at 6:38 AM, Russell Keith-Magee wrote: > On Fri, Jul 16, 2010 at 5:39 AM, Gregor Mü

Re: Accessible Command Output using self.stdout & self.stderr

2010-07-15 Thread Russell Keith-Magee
On Fri, Jul 16, 2010 at 5:39 AM, Gregor Müllegger wrote: > Related to the issue with stdout/stderr: > > I'm aware that Russ is not a big fan of Monkeypatching :) True :-) > but I think this > would be a legal case - since there is no other way of intercepting the real > stdout output (I'm not su

Re: Accessible Command Output using self.stdout & self.stderr

2010-07-15 Thread Gregor Müllegger
Related to the issue with stdout/stderr: It is ofcourse possible to have wrapper in the Command class for stdout and stderr output that redirect all data to system's stdout in most cases. But this might not work for all output since we don't have control about all management commands of thirdparty

Re: Accessible Command Output using self.stdout & self.stderr

2010-07-13 Thread Russell Keith-Magee
On Tue, Jul 13, 2010 at 2:23 PM, maxweld wrote: > I would like to propose that all commands in core.management be > modified to enable command output to be directed to self.stdout and > self.stderr so that the command output can be captured and made > accessible to an application. > > I use a virt

Accessible Command Output using self.stdout & self.stderr

2010-07-13 Thread maxweld
I would like to propose that all commands in core.management be modified to enable command output to be directed to self.stdout and self.stderr so that the command output can be captured and made accessible to an application. I use a virtual web hosting environment where no shell access is permitt