Re: [cgkit-user] [cgkit-commits] CGkitinfo Error

[Matthias B. <mat...@gm...>]

Hi David,

first of all, you posted your mail into the commits mailing list which 
is rather meant to receive the automatic svn commit messages. People can 
subscribe to that list if they want to know exactly what modifications 
are done to the code. The list is not meant to be used for discussions, 
this is done in the cgkit-user list instead (I have actually cc'ed to 
the user list instead of the commits list).

david vandergucht wrote:
> Hi there ! i used CGkit a while ago, on windows. Now i'm back in 
> business, but on OSX with the 2 alpha 8.
> 
> I've experienced several problem trying to install it on an "out of the 
> box Léopard with Apple's Python" but finally got it. (i will talk about 
> this in another post, just to have your opinion).

I would be interested in hearing about those problems. I'm still running 
Tiger, so unfortunately, I couldn't test cgkit on Leopard yet.

> Anyway, when executing viewer.py, i've noticed some error about cgkitinfo:
> 
>     import os.path, cgkitinfo
> 
> raise an error, cgkitinfo not beeing found as a module. I've made a 
> workaround editing the __init and replacing
>  
>     import cgkitinfo
> 
> by
> 
>     import cgkit.cgkitinfo as cgkitinfo
> 
> and that way, i had the viewer launch properly, and be able to see my 
> wonderful bi-color Sphere in Opengl
> 
> Is this the normal ? and is this the correct way ?

This is odd. The file cgkitinfo.py is part of the cgkit package and as 
it is in the same directory as __init__.py it should be found without 
prepending "cgkit." to it.

 From where did you run viewer.py? Could it be that you have still been 
in the root directory of the source archive? In that case, Python would 
pick up the local cgkit directory instead of the installed one and the 
local one might not have had the cgkitinfo module (as this is an 
automatically generated module). If that was the problem, then you 
should just change into another directory and try again.

If that was not the problem, can you please post the entire traceback?

- Matthias -