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 @aarongarrett , I was wondering what if you thought of giving a few contributors access to the repository and pypi so that we can help with at least merging PRs and keeping the code working with newer python releases, and then being able to release these on pypi?
I'm happy to help with general maintenance---we use inspyred in our tools so and we'd like to keep using it on newer python versions. I'm also happy to help with pypi releases (we can just set up a github action that automatically releases to pypi when a release is tagged here on github).
That's great to hear. I'm happy to help out to begin with. I'd like to add more CI to cover all current supported Python versions, fix any issues we see, and then make a new release with these fixes so folks can use inspyred off pypi again.
Hi @aarongarrett , I was wondering what if you thought of giving a few contributors access to the repository and pypi so that we can help with at least merging PRs and keeping the code working with newer python releases, and then being able to release these on pypi?
I'm happy to help with general maintenance---we use inspyred in our tools so and we'd like to keep using it on newer python versions. I'm also happy to help with pypi releases (we can just set up a github action that automatically releases to pypi when a release is tagged here on github).
https://packaging.python.org/en/latest/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/
Please do let us know. We'd really like to keep inspyred alive. Cheers,
The text was updated successfully, but these errors were encountered: