Python on Crays

[Carrie Farberow]

I am trying to build a statically-linked Python based on directions at:

http://yt.enzotools.org/wiki/CrayXT5Installation

I have tried this on multiple systems. The first time I attempt to build python, 'make' runs fine but 'make install' fails with the following error:

Sorry: UnicodeError: ("\\N escapes not supported (can't load unicodedata module)",)

Any help regarding the source of this error and possible fixes would be appreciated.

Carrie

 

[Mark Dickinson]

I am trying to build a statically-linked Python based on directions at:

http://yt.enzotools.org/wiki/CrayXT5Installation

I have tried this on multiple systems.  The first time I attempt to build python, 'make' runs fine but 'make install' fails with the following error:

Sorry: UnicodeError: ("\\N escapes not supported (can't load unicodedata module)",)

Any help regarding the source of this error and possible fixes would be appreciated.

Hmm. There's not a lot of information to go on here.
What version of Python is this? Python 2.6.2?
Have you tried Googling for that exact error message?

The following issue looks as though it might be relevant:

http://bugs.python.org/issue1594809

especially since it looks as though the directions you linked
to involve messing with the PYTHONPATH environment variable.

If you could post a log somewhere[*] showing the exact commands
that you executed, along with all the output (and especially
all the output from 'make' and 'make install'), that might help
someone diagnose the problem further.

Mark

[*] I'm not sure where, though. Posting all that output directly
in a newsgroup message might not be considered very friendly.

 

[Carrie Farberow]

Ok, here are links to word documents outlining the commands I executed as well as the make.log file and the make_install.log file

instructions/commands:
https://mywebspace.wisc.edu/xythoswfs/webui/_xy-29018965_1-t_dSnfEm5b

make.log:
https://mywebspace.wisc.edu/xythoswfs/webui/_xy-29018966_1-t_zjqLuV5v
javascriptarent.send('smtp')
make_install.log:
https://mywebspace.wisc.edu/xythoswfs/webui/_xy-29018967_1-t_n8aqH2P

The issue referred to in the previous message (http://bugs.python.org/issue1594809) sounds similar - however I do not think that I can just build the shared unicodedata module and have it work properly, as I am trying to statically link the necessary modules. I am very new with this, so if I am completely misunderstanding, please feel free to let me know.

Thanks!
Carrie

----- Original Message -----
From: Mark Dickinson <[email protected]>
Date: Friday, August 21, 2009 12:50 pm
Subject: Re: Python on Crays
To: (e-mail address removed)

I am trying to build a statically-linked Python based on directions at:

http://yt.enzotools.org/wiki/CrayXT5Installation

I have tried this on multiple systems.  The first time I attempt to

build python, 'make' runs fine but 'make install' fails with the
following error:

Sorry: UnicodeError: ("\\N escapes not supported (can't load unicodedata module)",)

Any help regarding the source of this error and possible fixes would

be appreciated.

Hmm. There's not a lot of information to go on here.
What version of Python is this? Python 2.6.2?
Have you tried Googling for that exact error message?

The following issue looks as though it might be relevant:

http://bugs.python.org/issue1594809

especially since it looks as though the directions you linked
to involve messing with the PYTHONPATH environment variable.

If you could post a log somewhere[*] showing the exact commands
that you executed, along with all the output (and especially
all the output from 'make' and 'make install'), that might help
someone diagnose the problem further.

Mark

[*] I'm not sure where, though. Posting all that output directly
in a newsgroup message might not be considered very friendly.

 

[Mark Dickinson]

Ok, here are links to word documents outlining the commands I executed as well as the make.log file and the make_install.log file
[links snipped]

So from the output of make, it looks as though none of the
modules specified in the Modules/Setup file is being built
at all on your system. So not just unicodedata, but the
math, cmath, array, itertools modules and more are
missing from your build.

You can check this by running Python: after the make step
finishes, you should have a working Python executable called
'python' in the current directory; if you start it up and
then type 'import math' at the '>>>' prompt, I'm guessing
you'll get an error message that looks something like:

ImportError: No module named math

I don't have much idea why those modules aren't being built;
I tried imitating the relevant parts of your instructions
(to the degree that they make sense on my non-Cray system)
without any problems.

Anyway, I agree that issue1594809 doesn't look so relevant;
the only common factor is that in both cases Python is
failing to find the unicodedata module; but in that issue
the unicodedata module is present but doesn't get found
because the paths are messed up, while in your case the
unicodedata module isn't being built at all.

Suggestions:

(1) double check that you've uncommented the appropriate lines
in the Modules/Setup file. E.g., after the configure step, there's
a line in Modules/Setup that looks like:

#unicodedata unicodedata.c # static Unicode character database

that leading '#' should be removed so that it looks like:

unicodedata unicodedata.c # static Unicode character database

and similarly for the other modules in that section.
Make sure that you're editing the Modules/Setup file
*after* the configure step and *before* the make step.

(2) Find a local Unix/Python guru and ask him/her to
help out. These sorts of problems are generally much
easier to figure out when you've got direct access to
the machine.

Sorry I can't be more help than this.

 

[Carrie Farberow]

I am from Wisconsin -- is there a python group here? Do you have any contact info.?

The compute node operating system is Compute Node Linux (CNL).

Carrie

----- Original Message -----
From: Craig <[email protected]>
Date: Thursday, August 27, 2009 2:15 pm
Subject: Re: Python on Crays

Who the one from wisconsin and did you try the python group in madison
maybe they can help.

Well i from madison are and i just a newbie with python.What OS you useing?

From: Mark Dickinson <[email protected]>
Subject: Re: Python on Crays
To: (e-mail address removed)
Date: Thursday, August 27, 2009, 1:48 PM

Ok, here are links to word documents outlining the

commands I executed as well as the make.log file and the
make_install.log file

[links snipped]

So from the output of make, it looks as though none of the
modules specified in the Modules/Setup file is being built
at all on your system.  So not just unicodedata, but
the
math, cmath, array, itertools modules and more are
missing from your build.

You can check this by running Python:  after the make
step
finishes, you should have a working Python executable
called
'python' in the current directory;  if you start it up
and
then type 'import math' at the '>>>' prompt, I'm
guessing
you'll get an error message that looks something like:

ImportError: No module named math

I don't have much idea why those modules aren't being
built;
I tried imitating the relevant parts of your instructions
(to the degree that they make sense on my non-Cray system)
without any problems.

Anyway, I agree that issue1594809 doesn't look so
relevant;
the only common factor is that in both cases Python is
failing to find the unicodedata module;  but in that
issue
the unicodedata module is present but doesn't get found
because the paths are messed up, while in your case the
unicodedata module isn't being built at all.

Suggestions:

(1) double check that you've uncommented the appropriate
lines
in the Modules/Setup file.  E.g., after the configure
step, there's
a line in Modules/Setup that looks like:

#unicodedata unicodedata.c    # static Unicode
character database

that leading '#' should be removed so that it looks like:

unicodedata unicodedata.c    # static Unicode
character database

and similarly for the other modules in that section.
Make sure that you're editing the Modules/Setup file
*after* the configure step and *before* the make step.

(2) Find a local Unix/Python guru and ask him/her to
help out.  These sorts of problems are generally much
easier to figure out when you've got direct access to
the machine.

Sorry I can't be more help than this.