I created a little tool that provides packaging for NEST extension modules into python packages that can be `pip installed` on the target machine.
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