[opensuse] Ultrasol
Running ultrasol.sh yields the following: docscott@AbyssLaptop:~> ultrasol.sh Traceback (most recent call last): File "/usr/lib64/games/ultrasol/ultrasol.py", line 69, in <module> exec "import " + n File "<string>", line 1, in <module> File "/usr/lib64/games/ultrasol/games/dieboesesieben.py", line 42 SyntaxError: Non-ASCII character '\xf6' in file /usr/lib64/games/ultrasol/games/dieboesesieben.py on line 42, but no encoding declared; see http://www.python.org/peps/pep-0263.html for details docscott@AbyssLaptop:~> Any fixes for this? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Dr. Thayer, On Sunday 25 February 2007 13:55, J. Scott Thayer M.D. wrote:
Running ultrasol.sh yields the following:
docscott@AbyssLaptop:~> ultrasol.sh Traceback (most recent call last): File "/usr/lib64/games/ultrasol/ultrasol.py", line 69, in <module> exec "import " + n File "<string>", line 1, in <module> File "/usr/lib64/games/ultrasol/games/dieboesesieben.py", line 42 SyntaxError: Non-ASCII character '\xf6' in file /usr/lib64/games/ultrasol/games/dieboesesieben.py on line 42, but no encoding declared; see http://www.python.org/peps/pep-0263.html for details docscott@AbyssLaptop:~>
Any fixes for this?
It really behooves both you and anyone who would like to help you for you to give more information than a terse dump of the error diagnostics that ensue when you try to run something unsuccessfully. You need to specify details of the software you installed, the operating system on which it's running, platform software (e.g., the Java platform) and possibly the hardware hosting it all. In particular, if you're installing RPMs and getting this kind of problem it suggests some sort of configuration problem in your system or that you're forcing installation in the face of unmet prerequisites. Ordinarily RPM won't allow the installation of a package whose prerequisites are not met, and most problems of incompatibilities or insufficiencies between the new software and your existing system setup are precluded. If you don't give us details of the scenario, it's just an exercise in either guessing what happened or rotely requesting the necessary details behind of the problematic symptoms. Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 25 February 2007 17:09, Randall R Schulz wrote:
Dr. Thayer,
On Sunday 25 February 2007 13:55, J. Scott Thayer M.D. wrote:
Running ultrasol.sh yields the following:
docscott@AbyssLaptop:~> ultrasol.sh Traceback (most recent call last): File "/usr/lib64/games/ultrasol/ultrasol.py", line 69, in <module> exec "import " + n File "<string>", line 1, in <module> File "/usr/lib64/games/ultrasol/games/dieboesesieben.py", line 42 SyntaxError: Non-ASCII character '\xf6' in file /usr/lib64/games/ultrasol/games/dieboesesieben.py on line 42, but no encoding declared; see http://www.python.org/peps/pep-0263.html for details docscott@AbyssLaptop:~>
Any fixes for this?
It really behooves both you and anyone who would like to help you for you to give more information than a terse dump of the error diagnostics that ensue when you try to run something unsuccessfully.
You need to specify details of the software you installed, the operating system on which it's running, platform software (e.g., the Java platform) and possibly the hardware hosting it all.
In particular, if you're installing RPMs and getting this kind of problem it suggests some sort of configuration problem in your system or that you're forcing installation in the face of unmet prerequisites. Ordinarily RPM won't allow the installation of a package whose prerequisites are not met, and most problems of incompatibilities or insufficiencies between the new software and your existing system setup are precluded.
If you don't give us details of the scenario, it's just an exercise in either guessing what happened or rotely requesting the necessary details behind of the problematic symptoms.
Randall Schulz
Thank you for your comments, points taken. I am running Suse 10.2 64bit on an AMD Turion based Acer. I installed via Yast Software Management module and did NOT instruct it to force install in the face of dependency issues. My analysis indicates that this has to do with Python not liking the character encoding of this European authored program, specifically the use of an umlaut. Python.org mentions this issue but I am not clear on the solution. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 25 February 2007 14:54, J. Scott Thayer M.D. wrote:
...
... My analysis indicates that this has to do with Python not liking the character encoding of this European authored program, specifically the use of an umlaut. Python.org mentions this issue but I am not clear on the solution.
This seems consistent with Anders' reply. As a work-around hack, you could just go in an replace the umlaut-bearing vowel(s) with their unadorned ASCII / ISO-8859-1 counterparts. You may need to iterate this modification more than once, but it's worth a try, providing it does not wear down your patience / insistence in getting this software running. Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 25 February 2007 22:55, J. Scott Thayer M.D. wrote:
Running ultrasol.sh yields the following:
docscott@AbyssLaptop:~> ultrasol.sh Traceback (most recent call last): File "/usr/lib64/games/ultrasol/ultrasol.py", line 69, in <module> exec "import " + n File "<string>", line 1, in <module> File "/usr/lib64/games/ultrasol/games/dieboesesieben.py", line 42 SyntaxError: Non-ASCII character '\xf6' in file /usr/lib64/games/ultrasol/games/dieboesesieben.py on line 42, but no encoding declared; see http://www.python.org/peps/pep-0263.html for details docscott@AbyssLaptop:~>
Any fixes for this?
Yes, but in future, please direct such bug reports to the place where you got the package. They will need to fix it and put out a fixed version The solution is to add a coding line to the python source file, to tell python which encoding is used for the text. Edit the file, and add # -*- coding: iso-8859-15 as the first line. You'll have to do that for gypsy.py as well The reason is that python defaults to ASCII encoding starting in python 2.5 (as explained on the web site mentioned in the error message) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Any fixes for this?
Yes, but in future, please direct such bug reports to the place where you got the package. They will need to fix it and put out a fixed version
The solution is to add a coding line to the python source file, to tell python which encoding is used for the text. Edit the file, and add
# -*- coding: iso-8859-15
as the first line. You'll have to do that for gypsy.py as well
The reason is that python defaults to ASCII encoding starting in python 2.5 (as explained on the web site mentioned in the error message)
So, despite the fact that I got this package from an Opensuse repository and the package is likely the same in any OTHER Opensuse repository I should direct my questions elsewhere? Do I have that right? And that would assume I was already certain I was LOOKING at a bug. BTW, the fix worked fine. Thank you. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 26 February 2007 00:15, J. Scott Thayer M.D. wrote:
So, despite the fact that I got this package from an Opensuse repository and the package is likely the same in any OTHER Opensuse repository I should direct my questions elsewhere?
As far as I can see, ultrasol isn't included in 10.2, so I would think you got this from a third party packager. Most likely packman. You should report bugs to the people who put together the package, otherwise there won't be a fixed version. The packagers are extremely unlikely to monitor mailing lists such as this one to find bugs in their packages.
Do I have that right? And that would assume I was already certain I was LOOKING at a bug.
Package didn't work => bug. This is by default, so yes, you can be certain it is a bug -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 26 February 2007 00:24, I wrote:
You should report bugs to the people who put together the package, otherwise there won't be a fixed version. The packagers are extremely unlikely to monitor mailing lists such as this one to find bugs in their packages.
Incidentally, for this exact same reason, even if it had been an opensuse package, you should still not report bugs on this mailing list. Bugs go to bugzilla.novell.com, where the developers can see them -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 25 February 2007 18:25, Anders Johansson wrote:
On Monday 26 February 2007 00:24, I wrote:
You should report bugs to the people who put together the package, otherwise there won't be a fixed version. The packagers are extremely unlikely to monitor mailing lists such as this one to find bugs in their packages.
Incidentally, for this exact same reason, even if it had been an opensuse package, you should still not report bugs on this mailing list. Bugs go to bugzilla.novell.com, where the developers can see them
OK -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (3)
-
Anders Johansson -
J. Scott Thayer M.D. -
Randall R Schulz