Skip to content
This repository has been archived by the owner on Apr 3, 2019. It is now read-only.

Status of this project #96

Open
arnuschky opened this issue Aug 18, 2015 · 8 comments
Open

Status of this project #96

arnuschky opened this issue Aug 18, 2015 · 8 comments

Comments

@arnuschky
Copy link

Has this project been abandoned? There are many open issues and unmerged pull-requests. The last activity of the owner @leporo was a year ago. Anyone has news of him?

@leporo
Copy link
Owner

leporo commented Aug 18, 2015

Yes, it seems I've abandoned tornado-redis.

About an year ago I started a big refactoring to support simplified Future-style syntax but never managed to complete it. I've lost the code then (after never touching it in 6 or 7 months) so can't even share it with others.

I'd love to continue with this project but it seems it dropped too far in my list. I don't think I'll be able to take care of it in next few months.

Does somebody want to take the ownership of project?

@arnuschky
Copy link
Author

Thanks for replying so quickly. A pity that you can't continue to work on it - it seems to me that your project is the best choice for using Redis on Tornado. Kudos - no matter how things continue.

Lack of time aside, I know almost nothing about Tornado, so I fear that I won't be a good choice for a maintainer. I'd be happy to chip in in terms of testing or rebasing existing PRs.

I hope someone suitable is willing to step up.

@zguangyu
Copy link

zguangyu commented Sep 4, 2015

I like this project. Although I'm not expert enough to be a maintainer, I'm trying to understand it and make some small changes.

@AeroNotix
Copy link

@leporo I'm about to start a project which will use redis/tornado somewhat heavily so perhaps I (and my colleagues) can help out maintaining.

Gathering a list of issues which are not outlined in the current set of issues would be useful, e.g. something you know which needs to be addressed would be useful.

@leporo
Copy link
Owner

leporo commented Jan 12, 2016

@AeroNotix: Thank you for your interest in maintaining this project. I think you've already reviewed the current list of issues and highlighted most important ones. Looking forward for pull requests. Please let me know if you're interested in gaining the ownership on this repository or being added as maintainer to PyPI.

Before moving forward with tornado-redis, have you considered alternatives like toredis (https://github.com/mrjoes/toredis and https://pypi.python.org/pypi/toredis-fork/0.1.3) for your project?
I haven't tested it but at least it utilises hiredis which tornado-redis is still missing.

@AeroNotix
Copy link

@leporo my only concern is that these haven't been touched in yonks. Do you think that would be an issue?

@leporo
Copy link
Owner

leporo commented Jan 12, 2016

I feel really sorry about it, but tornado-redis haven't been touched for about two years. I think this also can be classified as yonks. It definitely misses wrappers for commands added in most recent versions.
And I doubt I'll be able to update it this year.

I would suggest to check both the toredis and tornado-redis and see if it works for you. It seems toredis has much simpler structure so it has to be much faster and easier to patch.

If you end up with tornado-redis I'd be happy to accept your contribution or even transfer the repository ownership.

@leporo
Copy link
Owner

leporo commented Jul 12, 2016

Guys, as the project is not maintained anymore, it would be nice to have links to alternatives placed in readme.

Can you please share links to clients you've ended with if decided against tornado-redis?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants