Hm, strange, the Cheetah package on my PC is definitely written with
capital C and can't be imported with small c.
How did you install your Cheetah?

Best regards,
Marcus

On 03/22/2016 01:05 PM, Rohit Jatana wrote:
>  import Cheetah;print Cheetah.version
>
> Traceback (most recent call last):
>   File "<pyshell#31>", line 1, in <module>
>     import Cheetah;print Cheetah.version
> ImportError: No module named Cheetah
>
> when i am importing with small c ,it's working.
>
> On Tue, Mar 22, 2016 at 5:07 PM, Marcus Müller
> <marcus.muel...@ettus.com <mailto:marcus.muel...@ettus.com>> wrote:
>
>     Hey Rohit,
>
>     "import Cheetah"
>
>     ^ the capital C is important, which is why I expliticly asked you
>     to copy and paste the command.
>
>     Marcus
>
>
>     On 03/22/2016 12:31 PM, Rohit Jatana wrote:
>>     hey!
>>     i have appended the python path 
>>
>>     >>> import sys
>>     >>> print sys.path
>>     ['C:\\Python26\\Lib\\idlelib',
>>     'C:\\Windows\\system32\\python26.zip', 'C:\\Python26\\DLLs',
>>     'C:\\Python26\\lib', 'C:\\Python26\\lib\\plat-win',
>>     'C:\\Python26\\lib\\lib-tk', 'C:\\Python26',
>>     'C:\\Python26\\lib\\site-packages',
>>     'C:\\Python26\\lib\\site-packages\\wx-2.8-msw-ansi']
>>     >>> sys.path.append('c:\cheetah-2.4.4')
>>     >>> print sys.path
>>     ['C:\\Python26\\Lib\\idlelib',
>>     'C:\\Windows\\system32\\python26.zip', 'C:\\Python26\\DLLs',
>>     'C:\\Python26\\lib', 'C:\\Python26\\lib\\plat-win',
>>     'C:\\Python26\\lib\\lib-tk', 'C:\\Python26',
>>     'C:\\Python26\\lib\\site-packages',
>>     'C:\\Python26\\lib\\site-packages\\wx-2.8-msw-ansi',
>>     'c:\\cheetah-2.4.4']
>>     >>> import cheetah
>>     >>> import cheetah;print cheetah.version
>>
>>     Traceback (most recent call last):
>>       File "<pyshell#14>", line 1, in <module>
>>         import cheetah;print cheetah.version
>>     AttributeError: 'module' object has no attribute 'version'
>>
>>     and after doing this still same error.
>>
>>     i want to enhance the filter design tools and adding some support
>>     to it. I am interested in this bcoz i have got some strong dsp ,
>>     asp and signals and systems background. Also i can work on python.
>>     I am participating in gsoc16. since i am rookie to gnuradio so
>>     facing the problem. 
>>     but to be honest gnuradio support for windows is poor. 
>>
>>
>>     On Tue, Mar 22, 2016 at 3:07 PM, Marcus Müller
>>     <marcus.muel...@ettus.com <mailto:marcus.muel...@ettus.com>> wrote:
>>
>>         Hi Rohit,
>>
>>         can you make sure to use the "reply" button in your mail
>>         client to
>>         directly reply to my mails? That way, the context is
>>         preserved, and mail
>>         clients can show your discussion on the mailing list as one
>>         thread,
>>         making it far more probable you'll get a good answer!
>>
>>         On 22.03.2016 10:21, Rohit Jatana wrote:
>>         > yes cheetah is already installed.
>>         Point is that your output [1] shows:
>>         > -- Python checking for Cheetah >= 2.0.0
>>         > -- Python checking for Cheetah >= 2.0.0 - not found
>>         > CMake Error at volk/CMakeLists.txt:62 (message):
>>         >   Cheetah templates required to build VOLK
>>         >
>>         Which means that even if it was installed, it can't be found.
>>         Can you open a shell in the build directory, and run
>>
>>         python -c "import Cheetah;print Cheetah.Version"
>>
>>         there (please make sure to copy and paste the ".." string
>>         correctly)?
>>
>>         If python tells you the module could not be found, you didn't
>>         install
>>         Cheetah to a directory that python automatically searches for
>>         modules.
>>         In that case, you might need to amend the PYTHONPATH
>>         environment variable.
>>
>>         Just a note: I'm absolutely no expert on building GNU Radio
>>         on Windows.
>>         As a matter of fact, I don't even know whether or not GNU
>>         Radio on
>>         Cygwin works at alll!
>>
>>         So, my usual approach here is to take a step back and ask:
>>         Why are you
>>         doing this?
>>
>>         Best regards,
>>         Marcus
>>
>>         [1]
>>         
>> http://lists.gnu.org/archive/html/discuss-gnuradio/2016-03/msg00571.html
>>
>>
>
>
>
>
> _______________________________________________
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Reply via email to