@ahartikainen raised an issue on PyStan’s GitHub suggesting it be archived. There have been no commits in the last two years and here’s what GitHub says:
Here’s what GitHub says:
You can archive a repository to make it read-only for all users and indicate that it’s no longer actively maintained.
Source: Archiving repositories - GitHub Docs
This won’t delete the repository and it won’t make it impossible for people to use the frozen version, but it will let people know it’s not being maintained.
I’d like to hear from @ariddell about what his plans are for PyStan and also from the @SGB as I do not believe we have any policies in place for this kind of move.
1 Like
As one of the SGB members, I think SGB is not needed in this kind of case except if there would be a proposal for voting.
I think archiving makes sense, if it’s not maintained, and I assume it is possible to revert that, so there is no harm done.
httpstan made a release in November 2025. PyStan now builds wheels for ARM64 (so Apple Silicon).
I’ve made some progress on updating httpstan for C++17 and the new boost version. I’m currently on leave from the university so I’ve had less time to work on this.
And python users can of course always just use nutpie ;-)
1 Like
I don’t think there are httpstan wheels for any recent distribution (at least I failed to set them up for CI in ArviZ).
Just for the sake of prior art, I had recently archived some repositories after a similar forum post: https://discourse.mc-stan.org/t/archiving-older-unmaintained-stan-dev-repos/34638?u=wardbrian
None of them were remotely close to the usage level of PyStan, of course
If you visit Client Challenge you’ll note some wheels were uploaded in November 2025.
Yes, but there are no compatible versions of marshmallow which one could install.
marshmallow.warnings.RemovedInMarshmallow4Warning: The 'missing' argument to fields is deprecated. Use 'load_default' instead.
Good point. Would be great to get rid of that dependency or otherwise resolve that
1 Like