DEFAULT_TIMEOUT and same redis connection error about django-rq HOT 8 CLOSED

Yes, this is a bug. There's already an issue open for this at #71 . Mind submitting a Pull request and test for this?

from django-rq.

All right, I added a filter to get only the connection params:
#80

from django-rq.

@selwin Did you have a chance to look at my pull request?
Is there a chance to have it merged and released in a new version soon?
Thanks

from django-rq.

Fixed in #80 . Will try to release a new version soon

from django-rq.

Any idea when you will be able to release a new version?
Thanks

from django-rq.

Hello, I'll try to release one soon, but I'm not sure if there's enough in master that warrants a release. In the meantime, you could use "pip install -e" to install from a specific github commit.

Sent from my phone

On Dec 5, 2014, at 7:18 AM, Michael Palumbo [email protected] wrote:

Any idea when you will be able to release a new version?
Thanks

—
Reply to this email directly or view it on GitHub.

from django-rq.

I honestly prefer to pin versions in my requirements file instead of commits.
The last version was issued about 5 months ago and there are quite some merge requests since then.
You could still release a minor version, it does not have to be a big change I think.
Thanks

from django-rq.

@selwin
Any progress on a new release?
Thanks

from django-rq.