04-26-2019
The initialization warnings are due to the variable not being assigned an initial value in the code. That's just the way it's been written and you can ignore those warnings.
The failed to build module is a fundamental (show stopper) error which is a known bug; reported and resolved though I cannot find the published solution at the moment but it must be out there.
Issue 34385: Failed to build these modules: _ctypes on Solaris 10 - Python tracker
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi
We had 3 server -hp112and hp146 here hp112 is production server and hp146 is staging server used for load.
when i am trying to run follwing command
rcp abc hp112:/dnbusr1/gbid/gbid02 it's trowing an error :-
remshd: Login incorrect.
But same command is working wise versa -
rcp abc... (1 Reply)
Discussion started by: ashish_panpalia
1 Replies
2. UNIX for Dummies Questions & Answers
how can i make one script fail if some condition is not satisfied.i m writing if ..else logic in script.i need some standard command to do that ,, (1 Reply)
Discussion started by: dr46014
1 Replies
3. Shell Programming and Scripting
Hi Guys,
I am trying a simple for loop which is throwing an error.
Below is my code:
#/bin/sh
set -A array "are" "you" "there";
for ( i = 0 ; i < ${#array} ; i++ )
do
echo ${array}
done
I am getting this error
tci001wasd02 $ sh -vx array_for.sh
#/bin/sh
set -A array "are"... (6 Replies)
Discussion started by: mac4rfree
6 Replies
4. Solaris
Hello guys,
Im trying to install a monitoring software on my solaris10 machine and im getting an error doing so. Can someone please help.
ld: fatal: Symbol referencing errors. No output written to ../client/xymond_client
collect2: ld returned 1 exit status
gmake: *** Error 1
gmake:... (1 Reply)
Discussion started by: hemo21
1 Replies
5. Shell Programming and Scripting
All ,
I am trying to install POCO lib on Solaris server.
When I do make -s,I am getting the following error.
make: Fatal error in reader: Makefile, line 10: Unexpected end of line seen
Few of the content:
#
# Makefile
#
# The global Makefile for POCO
#
#sinclude config.make
... (0 Replies)
Discussion started by: prasperl
0 Replies
6. Shell Programming and Scripting
Dear all,
I would like to count the no;of word "INFORMATION" in a file called alt.lst and output to a unix variable INFORMATION.so to do this I wrote the below code
INFORMATION=echo 'INFORMATION' | tr -cs 'A-Za-z' '\n' < /app/tisq005/01/home/tisq005b/scripts/alt.lst | grep -c "INFORMATION"... (2 Replies)
Discussion started by: Kiransagar
2 Replies
7. Shell Programming and Scripting
Hi all,
I have below code
sqlplus -s ext/exo@TIS << EOF
whenever sqlerror exit failure rollback;
set echo off
set head off
set serveroutput on
set termout on
set trimspool on
SPOOL $SPOOL_FILE
select 'ROWS '|| ' '||decode((count(Part_no)),0,'With greater values not... (3 Replies)
Discussion started by: Kiransagar
3 Replies
8. Shell Programming and Scripting
Hi All
I have two shell scripts where the second is getting invoked from the first. E.g.
test1.sh and test2.sh Within test1, the code is something like this:
#!/bin/bash
. test2.sh
usage() {
echo "..."
echo "....."
}
SRC=$1
DEST=$2
case "$3" in
tran) doTran ;;
*)... (7 Replies)
Discussion started by: swasid
7 Replies
9. Shell Programming and Scripting
Hello Gurus,
I am writing one script at linux.
The logic is
There is a find command which will find some specific files daily and store at a variable
Then echo that variable .
Now when I am trying to read the variable by using for loop it is throwing error as below:cat: CKDT.dat: No such... (5 Replies)
Discussion started by: pokhraj_d
5 Replies
10. Solaris
Hi,
Prustat is throwing error only in zones. But it is working fine in global.
dtrace: invalid probe specifier
/*
** The following is a trimmed version of two seperate DTrace scripts:
**
** socketsnoop.d - snoop TCP network socket traffic by process.
** This is intended to identify the... (3 Replies)
Discussion started by: Sumanthsv
3 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