Initialization

[gswifort]

I think that when loading the ARX module, pyrx should be imported (similar to import pyrx). This will be needed to perform additional initialization tasks such as loading commands (e.g. REPL)

[CEXT-Dan]

If I understand correctly, the ARX module should call PyImport_ImportModule("PYRX")?

[gswifort]

yes, but probably "pyrx"

[CEXT-Dan]

It’s not very happy about this, it caused my pyrx_onload.py to fail, but it seems to work if I load it after pyrx_onload

[CEXT-Dan]

I uploaded a fresh build, PyImport_ImportModule("pyrx") is called after pyrx_onload.

[CEXT-Dan]

Would it not be better to have something similar to pyrx_onload, maybe pyrx_init.py?
This way you would not have to add conditionals to the pyrx module and it could have the reload event and stuff

[gswifort]

I think you're right. I think the module should be private (not useful for library users) and it could be more precise to say that it is used to initialize the host and not the package. Maybe _host_init.py (pyrx/_host_init.py)

[CEXT-Dan]

If _host_init.py imports

from pyrx import Rx, Ap, Ed

I can’t load it while working uninstalled

from pyrx_imp import Rx, Ap, Ed

works. I need to spend some time thinking about how to build a better build environment for me. maybe using the embedded

use pyrx if there's nothing I need to test , otherwise pyrx_imp for now

[gswifort]

I don't know what your environment looks like, but assuming you have a virtual python environment, after activating it, with the working directory set to the git repository (the directory where pyproject.toml is), call pip install -e ., this will install pyrx in editable mode, i.e. it will use the files in the repository as if they were installed.

[CEXT-Dan]

pip install -e . worked!

I have debug builds in another folder that’s not checked in, it never worked 100% because its outside the folder structure

[gswifort]

Related: #288