Dear Robin,
This is really cool! Seeing as NESTML also generates user modules, I am more than a little
interested in this feature.
To address the more technical point: does running with the user module .so path in the
LD_LIBRARY_PATH environment variable allow NEST to find it? Some changes are happening
with the paths—see
https://github.com/nest/nest-simulator/pull/1578—but the use of
LD_LIBRARY_PATH will, as far as I'm aware, be the recommended approach to locate user
modules. This contrasts with having a single "predefined" user module
installation directory (e.g. "/home/charl/.local/lib/nest/user_modules") that is
retrieved by invoking nest-config. Will the first option fit into the workflow of someone
who wants to install a pipnest-generated package? What is the workaround that you came up
with?
Cheers,
Charl
On Thu, May 28, 2020, at 00:37, Robin Gilbert De Schepper wrote:
Hi,
I created a little tool that provides packaging for NEST extension modules into python
packages that can be `pip installed` on the target machine.
https://pip-nest.readthedocs.io/en/latest/
First off, is this interesting to the community? It certainly seems easier to `pip
install some-module` than to provide installation instructions, and I can now specify my
modules as dependencies in code I distribute.
Secondly, there are some shortcomings based on the fact that the pip install only
reliably produces the build artifacts into python's site-packages and nest doesn't
look for them there. This can probably only be elegantly solved by adding an `entry_point`
to the nest python module so that these pip nest modules can announce themselves there?
--
Robin De Schepper, MSc
Department of Brain and Behavioral Sciences
Unit of Neurophysiology
University of Pavia, Italy
Via Forlanini 6, 27100 Pavia - Italy
Tel: (+39) 038298-7607
http://www-5.unipv.it/dangelo/
_______________________________________________
NEST Users mailing list -- users(a)nest-simulator.org
To unsubscribe send an email to users-leave(a)nest-simulator.org