No harm.  I was just pointing out that it's in good shape if you do
want to use it for a project.  As for touch, Erich is working on it.
He actually pointed out the protocol change to me (it's also something
I needed, worked around it for now), so it's on its way.

Feel free to add the functionality yourself.  The way pybeanstalk
implements the protocol is pretty straight forward and easy to
understand.   In addition, Erich's good about accepting patches from
others.

Next time I talk to him, I'll make poke him to have a look at the
list, and post any updates (I'm not sure when he'll be back from
vacation).


On Dec 1, 10:35 am, "Jeremy Dunck" <[EMAIL PROTECTED]> wrote:
> On Mon, Dec 1, 2008 at 10:15 AM, jmj <[EMAIL PROTECTED]> wrote:
>
> > Actually pybeanstalk is fairly well maintained.  The maintainer,
> > Erich, updates it fairly quickly, and the code base is well designed
> > and easy to use.
>
> > I know he's been out of town for the holiday.
>
> > As a side note, I'm actually using pybeanstalk for an enterprise job
> > queue.  It performs well, and I've seen no problems.  Testing has
> > shown about 2000 put/reserve cycles per minute.  Since we haven't
> > testing beyond 10k jobs yet, I don't have any further data.
>
> Thanks for the feedback-- I didn't mean to cast any aspersions on
> pybeanstalk-- I haven't used it enough to have any opinion on it, and
> really was just asking out of ignorance.  :-)
>
> I do have a couple nits, and in particular have need of the touch
> functionality, so that's what I meant about whacking on it.
>
> __getattr__ for the protocol stuff is one of my nits-- it ruins tab
> completion, which I use a lot.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"beanstalk-talk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/beanstalk-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to