Re: cannot import kudu.client

[veto]

I named the directory kudu or kudu.py not kudo!


> On 1 Sep BE 2561, at 07:02, veto  wrote:
> 
> yes,
> for testing I just named the working directory kudo or the test file kudo.py 
> in another project.
> the print(dir(kudo)) showed  a never ending loading.
> after rename the folder or file the import works.
> thanks a lot
> 
> 
> [GCC 4.9.2] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
> >>> import kudu
> >>> import kudu.client
> >>>
> 
> 
> 
>> On 1 Sep BE 2561, at 05:30, Todd Lipcon > > wrote:
>> 
>> Do you happen to have a directory called 'kudu' in your working directory? 
>> Sometimes python gets confused and imports something you didn't expect. The 
>> output of 'kudu.__file__' might give you a clue.
>> 
>> -Todd
>> 
>> On Fri, Aug 31, 2018 at 3:27 PM, veto > > wrote:
>> i installed and compiled successfully kudo on jessie, stretch and used 
>> dockers on centos and ubutu.
>> 
>> on all i installed python2.7 and pip in kudu-pyton==1.7.1 and 1.2.0 
>> successfully.
>> 
>> i could successfully import kudo but it fails to import kudo.client
>> 
>> here is the log:
>> 
>>  
>> (env) root@boot2docker:~/kudu# python
>> Python 2.7.12 (default, Dec  4 2017, 14:50:18) 
>> [GCC 5.4.0 20160609] on linux2
>> Type "help", "copyright", "credits" or "license" for more information.
>> >>> import kudu
>> >>> import kudu.client
>> Traceback (most recent call last):
>>   File "", line 1, in 
>> ImportError: No module named client
>> 
>> 
>> 
>> 
>> -- 
>> Todd Lipcon
>> Software Engineer, Cloudera
> 

Re: cannot import kudu.client

[veto]

yes,
for testing I just named the working directory kudo or the test file kudo.py in 
another project.
the print(dir(kudo)) showed  a never ending loading.
after rename the folder or file the import works.
thanks a lot


[GCC 4.9.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import kudu
>>> import kudu.client
>>>



> On 1 Sep BE 2561, at 05:30, Todd Lipcon  wrote:
> 
> Do you happen to have a directory called 'kudu' in your working directory? 
> Sometimes python gets confused and imports something you didn't expect. The 
> output of 'kudu.__file__' might give you a clue.
> 
> -Todd
> 
> On Fri, Aug 31, 2018 at 3:27 PM, veto  > wrote:
> i installed and compiled successfully kudo on jessie, stretch and used 
> dockers on centos and ubutu.
> 
> on all i installed python2.7 and pip in kudu-pyton==1.7.1 and 1.2.0 
> successfully.
> 
> i could successfully import kudo but it fails to import kudo.client
> 
> here is the log:
> 
>  
> (env) root@boot2docker:~/kudu# python
> Python 2.7.12 (default, Dec  4 2017, 14:50:18) 
> [GCC 5.4.0 20160609] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
> >>> import kudu
> >>> import kudu.client
> Traceback (most recent call last):
>   File "", line 1, in 
> ImportError: No module named client
> 
> 
> 
> 
> -- 
> Todd Lipcon
> Software Engineer, Cloudera

Re: cannot import kudu.client

[Todd Lipcon]

Do you happen to have a directory called 'kudu' in your working directory?
Sometimes python gets confused and imports something you didn't expect. The
output of 'kudu.__file__' might give you a clue.

-Todd

On Fri, Aug 31, 2018 at 3:27 PM, veto  wrote:

> i installed and compiled successfully kudo on jessie, stretch and used
> dockers on centos and ubutu.
>
> on all i installed python2.7 and pip in kudu-pyton==1.7.1 and 1.2.0
> successfully.
>
> i could successfully import kudo but it fails to import kudo.client
>
> here is the log:
>
>
> (env) root@boot2docker:~/kudu# python
> Python 2.7.12 (default, Dec  4 2017, 14:50:18)
> [GCC 5.4.0 20160609] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
> >>> import kudu
> >>> import kudu.client
> Traceback (most recent call last):
>   File "", line 1, in 
> ImportError: No module named client
>



-- 
Todd Lipcon
Software Engineer, Cloudera