CING fails to test ok on AMD64 with python2.6

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Using Charles' setup, see his text. This might depend on CING working on 
python 2.6, 64 bit, Linux

What is the expected output? What do you see instead?
cing --test -v 0

I get the output below.

best regards--
Charles

testRun (cing.PluginCode.test.test_validate.AllChecks) ... ERROR

======================================================================
ERROR: testRun (cing.PluginCode.test.test_validate.AllChecks)
- ----------------------------------------------------------------------
Traceback (most recent call last):
 File "/home/schwitrs/install/cing-read-only/cing/python/cing/PluginCode/test/test_validate.py", line 113, in testRun
   doProcheck = doProcheck, doWhatif = doWhatif, doWattos = doWattos))
 File "/home/schwitrs/install/cing-read-only/cing/python/cing/PluginCode/validate.py", line 127, in validate
   project.runCingChecks(ranges=ranges)
 File "/home/schwitrs/install/cing-read-only/cing/python/cing/PluginCode/validate.py", line 100, in runCingChecks
   project.criticize(toFile=True)
 File "/home/schwitrs/install/cing-read-only/cing/python/cing/PluginCode/validate.py", line 413, in criticize
   s = project.getCingSummaryDict()
 File "/home/schwitrs/install/cing-read-only/cing/python/cing/Libs/NTutils.py", line 1144, in __getattr__
   raise AttributeError
AttributeError

- ----------------------------------------------------------------------
Ran 1 test in 3.252s

FAILED (errors=1)
Traceback (most recent call last):
 File "/home/schwitrs/install/cing-read-only/cing/python/cing/main.py", line 761, in <module>
   main()
 File "/home/schwitrs/install/cing-read-only/cing/python/cing/main.py", line 514, in main
   testOverall(namepattern="test_*.py")
 File "/home/schwitrs/install/cing-read-only/cing/python/cing/main.py", line 303, in testOverall
   exec("import %s" % (mod_name))
 File "<string>", line 1, in <module>
 File "/home/schwitrs/install/cing-read-only/cing/python/cing/PluginCode/test/test_x3dna.py", line 16, in <module>
   from cing.PluginCode.x3dna import createHtmlX3dna
 File "/home/schwitrs/install/cing-read-only/cing/python/cing/PluginCode/x3dna.py", line 50, in <module>
   if not os.path.exists(cingPaths.x3dna):
 File "/home/schwitrs/opt/python-amd64/lib/python2.6/genericpath.py", line 18, in exists
   st = os.stat(path)
TypeError: coercing to Unicode: need string or buffer, NoneType found
Exception TypeError: "'NoneType' object is not callable" in  ignored
Exception TypeError: "'NoneType' object is not callable" in  ignored
Exception TypeError: "'NoneType' object is not callable" in  ignored

Original issue reported on code.google.com by jurge...@gmail.com on 30 Oct 2009 at 9:42

[GoogleCodeExporter]

Tim, is CCPN ok with 2.6 then? No problems what so ever?

Original comment by jurge...@gmail.com on 30 Oct 2009 at 9:53

[GoogleCodeExporter]

Cool, we're checking it out now.
The plan will be to be backwards compatible to 2.5 so no new 2.6 features used.

Original comment by jurge...@gmail.com on 30 Oct 2009 at 12:03

[GoogleCodeExporter]

Switched to python2.6 for development by me and Geerten, now need to debug the 
errors:
Exception TypeError: "'NoneType' object is not callable" in  ignored
Exception TypeError: "'NoneType' object is not callable" in  ignored
Exception TypeError: "'NoneType' object is not callable" in  ignored

I know what it is.

Original comment by jurge...@gmail.com on 3 Nov 2009 at 9:49

[GoogleCodeExporter]

It's http://bugs.python.org/issue6294

Fixed the verbose Error messages in r658 which had to do with the above bug. 
Solved by work around shelve. 
Used cPickle instead.

The x3dna problem should be disabled in the cing.csh settings file.

Charles, could you try updating to r658 I think it should have solved the: 
AttributeError too.

If so, please mark this issue as having a Status of Fixed.

Original comment by jurge...@gmail.com on 3 Nov 2009 at 3:13

[GoogleCodeExporter]

Furthermore:

> How does one disable it? I updated svn to r658 and reran make install
> and I still get errors related to x3dna (see below).
Removing a plugin like x3dna.py will certainly do it.
In revision 663 I have debugged the code in x3dna.py to check for non-Mac users 
so you don't need to remove it.

In that revision also the other traceback should not occur.

If you like the fix, please mark this issue as having a Status of Verified.

Original comment by jurge...@gmail.com on 5 Nov 2009 at 1:06

• Changed state: Fixed

[GoogleCodeExporter]

verified

Original comment by char...@schwieters.org on 6 Nov 2009 at 9:52

[GoogleCodeExporter]

Thanks Charles, I updated the Status to Verified.

Original comment by jurge...@gmail.com on 7 Nov 2009 at 9:25

• Changed state: Verified