You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi Eric! Glad you find the software useful. It is mostly bandwidth on our end that has prohibited a pypi release. If you'd be willing to contribute in that way, we'd be most grateful!
Happy to help, there are some specific things I could do, such as registering a package name on PyPI first and ensuring that you all have the relevant permissions to push packages to that PyPI package project -- followed by handing over ownership to you all. Releases to PyPI are much lighter weight than doing a peer-reviewed paper 😹. Let me know if you'd like that.
I also know the conda-forge process and bots well enough to have them do auto pulls from PyPI to conda-forge as well, which will ensure that you have distributions on both PyPI and conda-forge. We can proceed with that afterwards.
There are project-specific things that need to be defined, such as what the release process looks like (e.g. who cuts the releases, when), what versioning system you would use (semver vs. date-based), and whether you'd want some form of automation in the repo for releases (like what I do for pyjanitor). I'd defer to you all for answers to these questions though.
Hi! I'm wondering if you all might be considering a release of the package on PyPI and/or conda-forge?
Happy to help guide the process if a lack of knowledge is the main barrier here, have done this for other bioinformatics-oriented tools.
The text was updated successfully, but these errors were encountered: