Maintenance note #245
Description
Hi, current maintainer here, as of December 2025.
The last time I've solved a Comsol model for the purpose of my actual work was more than four years ago. Since then, I have no longer been using MPh, nor have I been using Comsol for anything other than testing this very library here.
So if you are an active user, and you're reading this, please ask yourself how MPh will be maintained going forward.
Most open-source projects out there don't depend on a software product that costs five-digit dollar amounts every year to renew the license for. The project here is different. If I didn't happen to have access to Comsol via my current employer, I would have abandoned maintenance of MPh a long time ago. Worst case, I might do just that – because who knows. Best case, the project will never need any update ever – if you believe that.
If you want to count on this project being maintained in the future – get involved. I don't mind adding people as (co-)maintainers, as long as there's some kind of track record to reassure all of us that you know what you're doing. Maintenance should come from the active user base. If you can't find the time to implement new features (very understandable), maybe run the test suite on your particular platform whenever a new Comsol version is released. Fix things as needed. Add new tests. Update the documentation. Etc.
Also, keep pressuring Comsol to release a "LiveLink for Python", or whatever they would call it. That's the only way to get first-class Python support. It's what Ansys does, and for good reason. This right here was never meant to be more than a temporary solution until Comsol does right by Python users.