search

rsgalloway / pyseq

Compressed sequence string module for Python
https://pyseq.rsgalloway.com/
Other
123 stars 36 forks source link

Version 0.5.1 not released in Github nor PyPI #50

Closed darkvertex closed 5 years ago

darkvertex commented 5 years ago

Hi there,

I noticed that there is a 0.5.1 version with a few tiny fixes: https://github.com/rsgalloway/pyseq/compare/0.5.0...master

I recently stumbled upon one of the fixed bugs, the one where it wasn't using basestring for some isinstance() calls so Unicode strings would break pyseq. It's fixed though, but the thing is that it's not released as of writing this sentence: https://github.com/rsgalloway/pyseq/releases https://pypi.org/project/pyseq/#history

The last edit was a year ago. Is there a reason why 0.5.1 is not released? and if not, can you please release it? :)

rsgalloway commented 5 years ago

Hi, thanks for using pyseq. Yeah, I need to push the latest release to PyPI, but I think the process has changed and I haven't had time to bother to learn the new steps yet. Anyway, that's why it's not up yet. Sorry about that.

That said, issue #51 was just reported that may be a performance regression in 0.5.1 that might be worth looking into first.

KengoSawa2 commented 5 years ago

I appreciate the reaction. Take your time. No need to rush:)

darkvertex commented 5 years ago

I appreciate the response. Indeed there is no rush, I was just pointing out the inconsistency.

By the way, when you have a few minutes you may be interested in reading up on Travis CI, which is free for public Github repos and features a PyPI deployment feature: https://docs.travis-ci.com/user/deployment/pypi/

You can see an example here of what a .travis.yml config file looks like with deployment to pypi from git tags, and here are some clear steps on setting up the pypi encrypted password (kindly left in a comment from the repo owner as he was recalling the procedure.)

rsgalloway commented 5 years ago

I think 0.5.1 was never finished, which is why it's not released on github or pypi. Since issue #51 was closed, I can tag and release 0.5.1. All new open issues will go into a 1.0 release.

rsgalloway commented 5 years ago

Oh, also, I'll look into Travis CI, but it looks like it wants access to repos in all my orgs, some of which I don't own. If there's a way to just give it access to this repo, that might work.

rsgalloway commented 5 years ago

OK tagged and released

https://github.com/rsgalloway/pyseq/releases https://pypi.org/project/pyseq/#history