Re: Integrating Pytave and Nnet

[enricobertino]

Mike Miller-4 wrote
> However, I took a wild guess that the error about `argv` was referring 
> to `sys.argv`. Sure enough, if I insert a new property into the `sys` 
> module, I can access tensorflow without the error: 
> 
>     >> py.sys.__dict__.__setitem__ ("argv", {""}); 
>     >> py.tensorflow.VERSION 
>     ans = [Python object of type str] 
>     
>       1.0.1 
> 
> I have a few questions
> 
>   * why does `sys.argv` exist when python the interpreter is run, but
>     not when it is embedded in another program?
>   * are we not doing some important initialization step?
>   * should tensorflow not be accessing sys.argv, is this a bug?

Yes, argv can be the cause of the issues! Setting manually the argv
attribute in sys, I can import tensorflow. I guess that when I import
Pandas, that attribute is in a certain way initialized. As you say, probably
some initialization steps are missing because tensorflow should access to
sys.arg like all other packages. 
In next days I will try to analyze both Pytave and Tensorflow module
importing and I will write here again!

Thank you for your help!

Cheers,
Enrico




--
View this message in context: 
http://octave.1599824.n4.nabble.com/Integrating-Pytave-and-Nnet-tp4682478p4682757.html
Sent from the Octave - Maintainers mailing list archive at Nabble.com.