10-23-2013
Over the top. You are making many assumptions and of course you are making several incorrect statements. With that said, nothing wrong with putting together your own "world"... as long as it works and is well supported. So if you believe a python workflows (or whatever) is the "right answer", certainly you are free to do that. If you believe a workflow paradigm is the way the world should be crafted (even if not python based)... again, you are free to do that. There are many ways to solve problems. So I have no problem with a workflow paradigm.... but solutions should be able to implement whatever style best fits the situation.
I will never tell someone to stop writing scripts. Python, shell or otherwise.
Btw, it's a valid argument to say that Python is a lower level language than (Bourne) shell script. Just saying.
This User Gave Thanks to cjcox For This Post:
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello,
I don't know anything about scripting, and I want help on writing a script, which can help me doing my research.
Actually I have some ASCII format files formatted in a way looks like this
6 lines of text that is not important for me
File_header_name_number_1 <--... (1 Reply)
Discussion started by: geoquest
1 Replies
2. Shell Programming and Scripting
I am very new to Unix. I need to write a script that will grep some files, etc. When I write the script, do I need to know what shell I am using? If so, how do I do that? (1 Reply)
Discussion started by: ssmiths001
1 Replies
3. Shell Programming and Scripting
Hi,
I just learnt the shell scripting and got working on that right now. I have one problem.
Here i am having a java application that needs to be start and stop using two shell scripts, i.e., starting the java application using one shell script and stopping the application using another... (1 Reply)
Discussion started by: sadha
1 Replies
4. Shell Programming and Scripting
What would happen if I didn't use "./" before writing a script? (4 Replies)
Discussion started by: ebethea27703
4 Replies
5. Shell Programming and Scripting
#Define the Start/Stop/Status Scripts to include
SSS_SCRIPTS=( prog1 prog2 prog3 etc...... )
#Start the scripts
StartScripts()
{
for SSS in ${SSS_SCRIPTS}
do
./$SSS start
done
}
#Stop the Scripts
StopScripts()
{
for SSS in ${SSS_SCRIPTS}
do
./$SSS stop #<---I... (1 Reply)
Discussion started by: madasafish
1 Replies
6. Shell Programming and Scripting
Dear All,
Pls find my scripts for Agent services strat & stop.
EAMSROOT=/opt/panaces
export EAMSROOT
cd $EAMSROOT
nohup ./OracleAgent.sh start &
nohup ./PFRAgent.sh start &
nohup ./PFR.sh start &
nohup ./SolarisOSAgent.sh start &
exit 0
EAMSROOT=/opt/panaces
export EAMSROOT
cd... (0 Replies)
Discussion started by: starnaresh
0 Replies
7. AIX
Hi
My hacmp version is 5.4 and it is a active passive cluster.
Where can I find the startup and stop scripts?
Please assist. Thanks. (2 Replies)
Discussion started by: samsungsamsung
2 Replies
8. Red Hat
Hi there,
I am wondering if I could add start/stop ksh scripts provided by 3rd party to cluster... I read that script must be ocf/lsb compliant, however, in AIX I can just set up two separate scripts for starting and stopping application. Can similar be done under RH Linux cluster?
Cheers,
c (1 Reply)
Discussion started by: cyjan
1 Replies
9. Shell Programming and Scripting
I have a question. Actually I want to make two scripts, one is startup.sh and other is stopscript.sh
so for example, I have 5 servers.
Each server has two instances :-
abc111 - Masters
-cra4
abc222 -middle tear
-cra
abc333 -middle tear
-cra1
abc444 -middle tear
... (1 Reply)
Discussion started by: siddharthjain
1 Replies
10. UNIX for Advanced & Expert Users
Is there a way to stop root from writing to a directory? I already tried chattr but that did not seem to work.
chattr +i directory (12 Replies)
Discussion started by: cokedude
12 Replies
PYTHON(1) BSD General Commands Manual PYTHON(1)
NAME
python, pythonw -- an interpreted, interactive, object-oriented programming language
SYNOPSIS
python ...
pythonw ...
DESCRIPTION
To support multiple versions, the programs named python and pythonw now just select the real version of Python to run, depending on various
settings. (As of Python 2.5, python and pythonw are interchangeable; both execute Python in the context of an application bundle, which
means they have access to the Graphical User Interface; thus both can, when properly programmed, display windows, dialogs, etc.) The current
supported versions are 2.6 and 2.7, with the default being 2.6. Use
% man python2.6
% man python2.7
% man pythonw2.6
% man pythonw2.7
to see the man page for a specific version. Without a version specified,
% man pydoc
and the like, will show the man page for the (unmodified) default version of Python (2.6). To see the man page for a specific version, use,
for example,
% man pydoc2.7
CHANGING THE DEFAULT PYTHON
Using
% defaults write com.apple.versioner.python Version 2.7
will make version 2.7 the user default when running the both the python and pythonw commands (versioner is the internal name of the version-
selection software used).
To set a system-wide default, replace 'com.apple.versioner.python' with '/Library/Preferences/com.apple.versioner.python' (admin privileges
will be required).
The environment variable VERSIONER_PYTHON_VERSION can also be used to set the python and pythonw version:
% export VERSIONER_PYTHON_VERSION=2.7 # Bourne-like shells
or
% setenv VERSIONER_PYTHON_VERSION 2.7 # C-like shells
% python ...
This environment variable takes precedence over the preference file settings.
64-BIT SUPPORT
Versions 2.6 and 2.7 support 64-bit execution (which is on by default).
Like the version of Python, the python command can select between 32 and 64-bit execution (when both are available). Use:
% defaults write com.apple.versioner.python Prefer-32-Bit -bool yes
to make 32-bit execution the user default (using '/Library/Preferences/com.apple.versioner.python' will set the system-wide default). The
environment variable VERSIONER_PYTHON_PREFER_32_BIT can also be used (has precedence over the preference file):
% export VERSIONER_PYTHON_PREFER_32_BIT=yes # Bourne-like shells
or
% setenv VERSIONER_PYTHON_PREFER_32_BIT yes # C-like shells
Again, the preference setting and environmental variable applies to both python and pythonw.
USING A SPECIFIC VERSION
Rather than using the python command, one can use a specific version directly. For example, running python2.7 from the command line will run
the 2.7 version of Python, independent of what the default version of Python is.
One can use a specific version of Python on the #! line of a script, but that may have portability and future compatibility issues.
Note that the preference files and environment variable that apply to the python command, do not apply when running a specific version of
Python. In particular, running python2.6 will always default to 64-bit execution (unless one uses the arch(1) command to specifically select
a 32-bit architecture).
SEE ALSO
python2.6(1), python2.7(1), pythonw2.6(1), pythonw2.7(1), arch(1)
BSD
Aug 10, 2008 BSD