On Sun, Apr 22, 2012 at 10:37 AM, Daniel Gonzalez <[email protected]> wrote:
> Is there a mechanism to force fabric to *not* use stdin?
Not at present -- there's an option to abort if it tries to do other
stdin-using things such as prompting the user for hostnames or
passwords, but it's not tied into the general interactivity feature
which is what's trying to open stdin in your case.
One thing that does bother me about your traceback, is that the
sys.stdin.read() line causing the IOError should only be firing if the
`select` statement on sys.stdin implied there's data to be read:
https://github.com/fabric/fabric/blob/1.4/fabric/io.py#L154
I would have expected that to not be the case if sys.stdin is actually
unavailable/not a tty. It would be great if we could get more info
about what's happening there in your scenario.
I agree that in normal circumstances Fabric should not attempt to
access stdin if it's not actually there, so if nothing seems wrong
with the way we're using `select` then I'd be open to patching the
inner block to detect & avoid read()ing from a non-functioning stdin.
Best,
Jeff
--
Jeff Forcier
Unix sysadmin; Python/Ruby engineer
http://bitprophet.org
_______________________________________________
Fab-user mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/fab-user
