PyChess fails on discovering it's own engine

[GoogleCodeExporter]

Just tried a clean run with deleting ~/.config/pychess and 
~/.local/share/pychess, and all engines discovered ok except our own one.
The throbber animates endlessly.

Original issue reported on code.google.com by gbtami on 10 May 2014 at 11:04

Attachments:

• 2014-05-10_12-48-41.log.bz2

[GoogleCodeExporter]

Seems like there's two problems here, the first being this from the log:

12:48:48 ('Python', '12:05:48.107') ERROR: Traceback (most recent call last):
12:48:48 ('Python', '12:05:48.107') ERROR:   File 
"/home/tamas/pychess/lib/pychess/Players/PyChess.py", line 7, in <module>
12:48:48 ('Python', '12:05:48.107') ERROR:     import pychess
12:48:48 ('Python', '12:05:48.107') ERROR: ImportError: No module named pychess

But also, shouldn't the engine discovering code fail better so that the 
throbber doesn't continue when an engine fails discovery?

Original comment by mattgatto on 10 May 2014 at 12:18

• Added labels: Type-Defect

[GoogleCodeExporter]

Maybe it's a regression from revision cb1acf69a133 which removed the need to 
specify PYTHONPATH?

Original comment by mattgatto on 10 May 2014 at 12:21

[GoogleCodeExporter]

I can't reproduce.

Original comment by mattgatto on 10 May 2014 at 12:23

[GoogleCodeExporter]

I think you have an installed pychess (.rpm) and "import pychess" can work from 
there. 

Original comment by gbtami on 10 May 2014 at 4:39

[GoogleCodeExporter]

This issue was closed by revision 7754bb1a43e0.

Original comment by gbtami on 10 May 2014 at 4:40

• Changed state: Fixed