Open mwcraig opened 6 days ago
Hi @mwcraig, apologies for not getting back to you sooner!
I've been in touch with Kyle, and we've set up a separate Github organisation for ongoing maintenance at sep-developers/sep -- which should hopefully sidestep any future problems in case I can no longer maintain sep
(although I plan to keep going with this as long as I can!). Over the next few days I'll try to merge all the changes in this repo over there, and figure out how to sunset sep-pjw
in as smooth a way as possible.
With that in mind, if the up-to-date package name reverts to sep
, are there any particular changes that need to be made to keep (or aid) the conda compatibility? I don't use conda myself, so I'm rather unfamiliar with best practices for packaging and maintenance there.
👋 @PJ-Watson thanks for keeping sep up-to-date! There are a couple of projects I'm involved on that use sep and I was getting worried about its future.
I noticed that
sep-pjw
isn't in conda-forge yet. I'm one of the maintainers of the currentsep
feedstock and would be happy to open the pull request to https://github.com/conda-forge/staged-recipes to addsep-pjw
. I'm also part of conda-forge core, so if you would prefer to open the PR please mention me on it and I'll give it a quick review.