Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider splitting Python package #287

Open
LourensVeen opened this issue Jan 24, 2024 · 0 comments
Open

Consider splitting Python package #287

LourensVeen opened this issue Jan 24, 2024 · 0 comments

Comments

@LourensVeen
Copy link
Contributor

The muscle3 PyPI package currently installs both the libmuscle and muscle3 modules, with muscle3 having additional dependencies. muscle3 isn't needed by models, and to minimise the potential for version conflicts it would be nice if we had a separate libmuscle package that had a minimum of dependencies. Apparently there are EasyBuild issues too (although EasyBuild does have recent matplotlib packages).

I do remember putting the manager into libmuscle because it was easier that way, but we should have a look at this again and see if we can extract it back out. Or leave it in and just have a dependency of the muscle3 package on the libmuscle package.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant