On Mon, 4 Feb 2013, Petrus Hyvönen wrote:
Hopefully fixed in rev 1442394.
Petrus, please try it out and let me know if it's _really_ fixed.
JCC & my wrapped library rebuilt, old removed, my previously failed example
works now as it should (reports the details of the exception). Many Th
>
>
>>
> Hopefully fixed in rev 1442394.
> Petrus, please try it out and let me know if it's _really_ fixed.
>
>
>
JCC & my wrapped library rebuilt, old removed, my previously failed example
works now as it should (reports the details of the exception). Many Thanks.
I see you also made modificatio
On Mon, 4 Feb 2013, Andi Vajda wrote:
On Mon, 4 Feb 2013, Petrus Hyvönen wrote:
I have some strange error when an java exception occurs in the wrapped
library 'orekit', the exception text is not printed and a python error
"NameError: global name 'StringWriter' is not defined" occurs in
__in
On Mon, 4 Feb 2013, Petrus Hyvönen wrote:
I have some strange error when an java exception occurs in the wrapped
library 'orekit', the exception text is not printed and a python error
"NameError: global name 'StringWriter' is not defined" occurs in __init__.py
I am using the --use_full_names o
Hi,
I have some strange error when an java exception occurs in the wrapped
library 'orekit', the exception text is not printed and a python error
"NameError: global name 'StringWriter' is not defined" occurs in __init__.py
I am using the --use_full_names option, latest JCC from SVN.
It is in the
