DIST: Improve method of distributing packages to users

[asoplata]

There are at least 2 different package distribution methods we should consider changing to:

• binary-compiled “wheels”
• Anaconda packages

!!! Please note that this is a task about what form we use for distributing our code/assets to users (the “user side”). This is distinct from improvements to how do we build our packages using development tools (the “dev side”)., such as here #951 .

Notes

• George specifically provided very useful information to Dylan and Austin about this in this meeting: https://www.notion.so/jonescompneurolab/HNN-Core-Improvements-Meeting-with-George-Dang-abc4a36e4c844b38ba81da39122ab35a
• MPI compatibility will be a major component of this (such as including possible distribution of an MPI executable and an mpi4py install built against it):
  • George has specifically recommended wheels, and this has potential to greatly reduce the complexity of using compiled NEURON mechanisms. I don’t know, but it could be possible this may even enable easier distribution of MPI-compatible installs.
  • Another option related to MPI-compatible installs specifically is to build an Anaconda package for HNN-Core, such that we can be sure we are distributing a copy of mpi4py built against a known MPI executable.

[jasmainak]

I thought the issue with mpi4py is that you need to have either OpenMPI or another MPI binary installed on your computer ... hence the need to go through anaconda. The anaconda install gets you both the MPI binary and mpi4py. Can this be done through wheels?