py-bluepyemodel: opensourcing with dependencies

[heerener]

No description provided.

[spackbot-app]

Hi @heerener! I noticed that the following package(s) don't yet have maintainers:

• py-bluepyefe
• py-bluepyemodel
• py-bluepyopt
• py-currentscape
• py-efel
• py-morph-tool
• py-morphio
• py-neurom

Are you interested in adopting any of these package(s)? If so, simply add the following to the package class:

    maintainers("heerener")

If not, could you contact the developers of this package and see if they are interested? You can quickly see who has worked on a package with spack blame:

$ spack blame py-bluepyefe

Thank you for your help! Please don't add maintainers without their consent.

You don't have to be a Spack expert or package developer in order to be a "maintainer," it just gives us a list of users willing to review PRs or debug issues relating to this package. A package can have multiple maintainers; just add a list of GitHub handles of anyone who wants to volunteer.

[tldahlgren]

Confirmed all homepages, version sha256, and main branches. I could not confirm the unifurcation branch for py-morphio.

I have a question about version and branch naming.

Adding @adamjstewart since these are all python packages.

[heerener]

Confirmed all homepages, version sha256, and main branches. I could not confirm the unifurcation branch for py-morphio.

I have a question about version and branch naming.

The unifurcation branch is probably an internal remnant that was overlooked; since it doesn't exist any more, I'll remove it from the recipe.
Similarly, for develop / master mismatches, I would guess it's a leftover from when these recipes were originally written for internal use without much thought put into these kinds of things. I'll try to verify that changing the version won't break anything and update.

As for the neuron-related questions: I'll check with the people who are actually familiar with the software.