>> Not sure about this rpm you downloaded, but .pyc files are compiled
>> versions of python's source .py files. Unfortunately they are not
>> binary compatable with different versions of python, so your 2.1
>> pyc's probably won't work with a 2.2 python interpreter and
>> vice-versa. The good news is that rarely are .py files not
>> compatable, and .pyc files are easily generated from .py source
>> files. Does the pysol package you have come with the .py files in
>> addition to the .pyc files?
> Don't know. The file was downloaded and installed by apt-get on
> SuSE8.2 Never even got to look at it. Not sure how I would determine
> that. It was not a .src.rpm so I doubt that it built a .spec file.
Well, you should try and find out if apt installed .py files with pysol
too. If so, you will probably be able to regenerate .pyc files from
the .py files and be up and running in no time. In some cases it's as
easy as running "touch *.py" so the source file's timestamp is updated,
and next time python runs that .pyc it will see the source .py file is
newer than the .pyc file and automatically recompile it into a fresh
.pyc file.
I'm not an apt guy yet (rpm), but the apt howto says something like:
apt-file list packagename
should do the trick maybe?
~ Daniel
________________________________________________________________
The best thing to hit the internet in years - Juno SpeedBand!
Surf the web up to FIVE TIMES FASTER!
Only $14.95/ month - visit www.juno.com to sign up today!
-----------------------------------------------------------------------
This list is provided as an unmoderated internet service by Networked
Knowledge Systems (NKS). Views and opinions expressed in messages
posted are those of the author and do not necessarily reflect the
official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 20:14:28 EDT