Thank you, Eric.
I still have my "libj..argtypes = ( … )" in there after I refreshed from
your latest j.py (for double checking the types). The one for JSetM is causing
ctypes.ArgumentError with byref(ss).
It looks working after I removed all argtypes.
thank you.
Maurice
> On Feb 18, 201
j.test() with the latest files from the api/python3 works for me on 3.6.4
anaconda on linux.
Please verify that you are using the j.py from the latest addon version.
If there is still a problem, let me know your environment.
On Sun, Feb 18, 2018 at 10:24 PM, More Rice wrote:
> Thanks Eric. Yes
Thanks Eric. Yes, though, not everything is working yet.
For example, j.test() isn’t working because j.set() still has bugs - I
didn’t have time to dig deeper on that one this weekend.
Thanks.
On Sun, Feb 18, 2018 at 8:15 PM Eric Iverson
wrote:
> Thanks. Being able to easily use J from python
Thanks. Being able to easily use J from python will be nice!
I take your point about c_longlong instead of c_ulonglong where
appropriate. I will make that change.
Sounds like you made your own fixes. Congrats.
Please verify that the latest in the addon also works and suggest any
further changes.
Problem solved! (I think.)
In j.py, after the ctypes.CDLL() call, for each API in libj, you need set
libj..restype and libj..argtypes accordingly (I pulled down the
jsource code and matched them). Once you do that, it runs.
~/experiment/python3> python3
Python 3.6.4 |Anaconda custom (64-bit)| (
re python:
I didn't expect so much early use.
First, let's move this discussion to general so as to not clutter up
programming.
I'll dig into this a bit and report back in general.
On Sun, Feb 18, 2018 at 9:23 AM, Vijay Lulla wrote:
> I am on a mac and I too get a segmentation fault when I ru
I am on a mac and I too get a segmentation fault when I run the j.init()
line. Since it is a mac I had to change the pathdll in j_config.py like
pathdll = pathbin+'/libj.dylib'
Is there any way to check what caused the segmentation fault?
On Sun, Feb 18, 2018 at 3:51 AM, bill lam wrote:
> I t
I think for j806 deb installm the j_config.py
can be something like
# following is typical for j806 debian install
pathbin= '/usr/bin'
pathdll= 'libj.so.8.06'
pathpro= '/etc/j/8.06/profile.ijs'
Сб, 17 фев 2018, Eric Iverson написал(а):
> I have just added a python3 folder to the addons api fami
It is faulting on the do() method call after JInit() on j.py:39 for me as well.
Segmentation fault: 11
My J version is
Engine: j806/j64/darwin
Release: commercial/2017-11-06T10:20:33
Library: 8.06.09
Qt IDE: 1.6.2s/5.6.3
Platform: Darwin 64
Installer: J806 install
thanks.
Maurice
> On Feb 17, 2
Eric,
I'm interested in this. Python is the fastest growing language
with astronomers -- the astropy package has really useful routines.
I don't really understand much about this, but I put j.py and j_config.py
into my python3 directory & edited the paths in j_config.py.
Starting python3,
I have just added a python3 folder to the addons api family.
The python scripts in the addon make it easy to use J from python3.
The popularity of python, combined with easy use of J, might open some
doors.
--
For information abo
In case anybody wants know how to call j.dll from Python, I have made a repo
with a demonstration app to show how to do it.
https://github.com/jonghough/PytoJ_Demo
The actual logic of the connection is from source code somebody wrote in the
mailing list (thanks!) :
http://www.jsoftware.com/pip
12 matches
Mail list logo
