It appears to be an issue specifically with VLC, not subprocess. Thank you guys. The remote interface works through sockets, which is perfectly fine... if I create a local socket, I can have it connect to the socket with command line arguments.
On Fri, Jun 19, 2009 at 9:30 AM, Tyler Laing <trinio...@gmail.com> wrote: > Sorry, XD. I'll ask the VLC people if they happen to know why VLC won't > open up the remote interface. > > -Tyler > > On Fri, Jun 19, 2009 at 9:09 AM, Mike Kazantsev <mk.frag...@gmail.com>wrote: > >> On Fri, 19 Jun 2009 22:00:28 +0600 >> Mike Kazantsev <mk.frag...@gmail.com> wrote: >> >> > On Fri, 19 Jun 2009 08:28:17 -0700 >> > Tyler Laing <trinio...@gmail.com> wrote: >> > >> > > Thanks mike, the idea that maybe some of the info isn't being passed >> is >> > > certainly interesting. >> > > >> > > Here's the output of os.environ and sys.argv: >> > > >> > ... >> > >> > I'm afraid these doesn't make much sense without the output from the >> > second results, from py itself. My suggestion was just to compare them >> > - pop the py shell, eval the outputs into two sets, do the diff and >> > you'll see it at once. >> > If there's an empty set then I guess it's pretty safe to assume that >> > python creates subprocess in the same way the shell does. >> >> Just thought of one more really simple thing I've missed: vlc might >> expect it's remote to work with tty, so when py shoves it a pipe >> instead, it automatically switches to non-interactive mode. >> >> You can remedy that a bit by superclassing subprocess.Popen, replacing >> pipes with pty, but they are quite hard to work with, prehaps pexpect >> module would be of some use there: >> >> http://pypi.python.org/pypi/pexpect/ >> >> -- >> Mike Kazantsev // fraggod.net >> >> -- >> http://mail.python.org/mailman/listinfo/python-list >> >> > > > -- > Visit my blog at http://oddco.ca/zeroth/zblog > -- Visit my blog at http://oddco.ca/zeroth/zblog
-- http://mail.python.org/mailman/listinfo/python-list
