os.popen('alias')

[Belebele]

>From an interactive python shell, I execute the following:

import os
for line in os.popen('alias').readlines():
print line
No aliases are printed.

I started python from an bash environment that had many aliases
defined. I expected to see the list of aliases from within the
interactive python shell. What could I do to see those aliases defined
in the shell from where I started python?

Thanks:

Belebele

[Lars Kellogg-Stedman]

> import os

for line in os.popen('alias').readlines():
print line
No aliases are printed.

I started python from an bash environment that had many aliases
defined. I expected to see the list of aliases from within the
interactive python shell. What could I do to see those aliases defined
in the shell from where I started python?

You can't, really. The 'alias' command is a shell built-in, not an external
command, so you can't meaningfully run it from a Python script (and any
aliases defined in your shell will probably not be available to Python).

Matters are complicated a little bit because when you use os.popen(),
your command line is actually passed to *a* shell, usually /bin/sh, so
the final command line looks like this:

/bin/sh -c 'alias'

However, even if /bin/sh is actually bash, dotfiles such as .profile and
..bashrc aren't read when using the '-c' option.

If you really want to do something to your bash aliases with python, you
could pipe them into a python command:

$ alias | python myscript.py

-- Lars

--
Lars Kellogg-Stedman <82*************@jetable.net>
This email address will expire on 2005-11-23.

[Lars Kellogg-Stedman]

> import os

for line in os.popen('alias').readlines():
print line
No aliases are printed.

I started python from an bash environment that had many aliases
defined. I expected to see the list of aliases from within the
interactive python shell. What could I do to see those aliases defined
in the shell from where I started python?

You can't, really. The 'alias' command is a shell built-in, not an external
command, so you can't meaningfully run it from a Python script (and any
aliases defined in your shell will probably not be available to Python).

Matters are complicated a little bit because when you use os.popen(),
your command line is actually passed to *a* shell, usually /bin/sh, so
the final command line looks like this:

/bin/sh -c 'alias'

However, even if /bin/sh is actually bash, dotfiles such as .profile and
..bashrc aren't read when using the '-c' option.

If you really want to do something to your bash aliases with python, you
could pipe them into a python command:

$ alias | python myscript.py

-- Lars

--
Lars Kellogg-Stedman <82*************@jetable.net>
This email address will expire on 2005-11-23.

[Chris F.A. Johnson]

On 2005-11-18, Belebele wrote:

From an interactive python shell, I execute the following:
import os
for line in os.popen('alias').readlines():
print line
No aliases are printed.

I started python from an bash environment that had many aliases
defined. I expected to see the list of aliases from within the
interactive python shell.

Since bash does not export aliases, they cannot be seen by a child
process.
What could I do to see those aliases defined in the shell from where
I started python?

Store them in a file before calling python, and read that file.

--
Chris F.A. Johnson, author | <http://cfaj.freeshell.org>
Shell Scripting Recipes: | My code in this post, if any,
A Problem-Solution Approach | is released under the
2005, Apress | GNU General Public Licence

[Chris F.A. Johnson]

On 2005-11-18, Belebele wrote:

From an interactive python shell, I execute the following:
import os
for line in os.popen('alias').readlines():
print line
No aliases are printed.

I started python from an bash environment that had many aliases
defined. I expected to see the list of aliases from within the
interactive python shell.

Since bash does not export aliases, they cannot be seen by a child
process.
What could I do to see those aliases defined in the shell from where
I started python?

Store them in a file before calling python, and read that file.

--
Chris F.A. Johnson, author | <http://cfaj.freeshell.org>
Shell Scripting Recipes: | My code in this post, if any,
A Problem-Solution Approach | is released under the
2005, Apress | GNU General Public Licence

[Chris F.A. Johnson]

On 2005-11-19, Chris F.A. Johnson wrote:

On 2005-11-18, Belebele wrote:

From an interactive python shell, I execute the following:

import os
for line in os.popen('alias').readlines():
print line
No aliases are printed.

I started python from an bash environment that had many aliases
defined. I expected to see the list of aliases from within the
interactive python shell.

Since bash does not export aliases, they cannot be seen by a child
process.

What could I do to see those aliases defined in the shell from where
I started python?

Store them in a file before calling python, and read that file.

Or redefine them as functions and use:

import os
for line in os.popen('typeset -f').readlines():
print line

--
Chris F.A. Johnson, author | <http://cfaj.freeshell.org>
Shell Scripting Recipes: | My code in this post, if any,
A Problem-Solution Approach | is released under the
2005, Apress | GNU General Public Licence

[Chris F.A. Johnson]

On 2005-11-19, Chris F.A. Johnson wrote:

On 2005-11-18, Belebele wrote:

From an interactive python shell, I execute the following:

import os
for line in os.popen('alias').readlines():
print line
No aliases are printed.

I started python from an bash environment that had many aliases
defined. I expected to see the list of aliases from within the
interactive python shell.

Since bash does not export aliases, they cannot be seen by a child
process.

What could I do to see those aliases defined in the shell from where
I started python?

Store them in a file before calling python, and read that file.

Or redefine them as functions and use:

import os
for line in os.popen('typeset -f').readlines():
print line

--
Chris F.A. Johnson, author | <http://cfaj.freeshell.org>
Shell Scripting Recipes: | My code in this post, if any,
A Problem-Solution Approach | is released under the
2005, Apress | GNU General Public Licence