public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "merv" <merv@spidernet.com.cy>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] initscripts in python
Date: Wed, 16 Apr 2003 11:49:15 +0300	[thread overview]
Message-ID: <3E9D433B.31052.7EDE153@localhost> (raw)
In-Reply-To: <Pine.GSO.4.40.0304160123260.21363-100000@ucsub.colorado.edu>

Sure could. Can see the logic of the argument.  And then there could 
be the implementation of a "*.psh" for a python-lang shell script.  Just 
ideas, but this could be an option too. Then we are starting to address 
script files and runtime shell interaction.

Anyone have any thoughts on how to get the shell to accept Python 
commands/arguments/statements and what-not in runtime from the 
prompt?  Would it be a big undertaking to use C-level translation of a 
new set of Python macros/symbols passed to the the kernel?  I 
suppose that a decision at that point would involve some consideration 
of whether the objective was to incorporate the Python languages itself 
(to greater or lesser extent) into the shell  or whether it was the syntax 
and structure of Python that was to be *lifted*.  Another way to see it 
would be the potential for bloating scripts with *import*s as a result of 
Python languages transplantation on the one hand, while having such 
useful things as f.tell() and f.seek() available on the other hand.  If the 
syntax were incorporated into the shell, would there be a neat way of 
by-passing the need for a full-blown python interpreter?  I think this 
could be worth some serious attention, but I just wonder if anyone has 
any cool ideas or some time to share on this admittedly vague (so far) 
possibility.



On 16 Apr 2003 at 1:25, Jeff Rose wrote:

> Could you use a hybrid of both bash scripts and python by using the
> '-c' argument to run single python commands?
> 
> -Jeff


--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-04-16  8:38 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-16  1:29 [gentoo-dev] initscripts in python Justin Whitney
2003-04-16  4:09 ` Daniel Armyr
2003-04-16  5:38 ` merv
2003-04-16  7:25   ` Jeff Rose
2003-04-16  8:49     ` merv [this message]
2003-04-16  8:19   ` Paul de Vrieze
2003-04-16  8:52     ` Sven Vermeulen
2003-04-16 20:54       ` Justin Whitney
2003-04-17 20:05         ` merv
2003-04-17  5:49     ` Joseph Carter
2003-04-17  6:27       ` George Shapovalov
2003-04-17 18:25         ` merv
2003-04-17  7:42       ` Paul de Vrieze
2003-04-16 22:44   ` Abhishek Amit
2003-04-17  6:45     ` Sven Vermeulen
2003-04-17 20:56       ` merv
2003-04-17 22:26         ` Caleb Shay
2003-04-17 23:32           ` merv
2003-04-17 18:18     ` merv
2003-04-16 21:08 ` Brad Laue
2003-04-17  6:47   ` Sven Vermeulen
  -- strict thread matches above, loose matches on Subject: below --
2003-04-16 11:13 merv

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3E9D433B.31052.7EDE153@localhost \
    --to=merv@spidernet.com.cy \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox