[Twisted-Python] txmongo vs. pymongo + callInThread

[Clayton Daley]

I'm still in "proof of concept" mode so take my comments with a grain of
salt... but my question was motivated by datetime issues:

   - After switching to txmongo, timedelta seemed to break. Turns out it
   breaks autobahn as well so I may need to solve the problem sooner... but
   it's a material difference.
   - I also wanted to take advantage of some timezone stuff purportedly
   included in newer versions of pymongo (but I haven't fully implemented
   anything yet to verify).

When it comes to interest in txmongo:

   - Insofar as it would address the question of lazy calls (and possible
   hassles like not-lazy iterators), it would be a welcome simplification to
   deferToThread.
   - At the same time, I don't see any intrinsic benefit to rebuild the
   client all-the-way-down.  If it were possible to wrap PyMongo in a
   lazy-aware (and deferred returning) wrapper... that would be enough for me.
   - If a wrapper reduces the work to maintain the project at parity, I'd
   redouble my support for the approach. No need to commit volunteer
   supporters (current and/or future) to more work than absolutely necessary.

Clayton Daley

On Tue, Dec 30, 2014 at 4:50 AM, bret curtis <psi29a at gmail.com> wrote:

> On Tue, Dec 23, 2014 at 7:51 AM, Gelin Yan <dynamicgl at gmail.com> wrote:
>
>>
>>
>> On Mon, Dec 22, 2014 at 5:05 AM, Clayton Daley <clayton.daley at gmail.com>
>> wrote:
>>
>>> Are there any major disadvantages of using pymongo with callInThread
>>> instead of txmongo?  I'd like to take advantage of some newer features in
>>> pymongo (unfortunately not available in txmongo) and it's certainly easier
>>> to maintain feature parity using callInThread.
>>>
>>> Clayton Daley
>>>
>>>
>>>
>> Hi Clayton
>>
>>     Txmongo has been inactive for a while so I suggest using pymongo &
>> twisted thread pool. I have been using them for a couple of years and they
>> work quite well.
>>
>> Regards
>>
>> gelin yan
>>
>
> Hey guys,
>
> just wanted to drop in and say that txmongo isn't dead. We (Amplidata)
> just recently sent a merge request to add SSL (authentication/encryption)
> support[1] that Alexandre will review after the holidays. While Alexandre
> isn't currently developing txmongo, he does review and accept pull
> requests. So while the community is small, it is still alive.
>
> Amplidata (the company I work for) has also expressed an interest in
> getting txmongo up to speed with PyMongo, similar in how we got Ldaptor and
> its myriad forks to converge and development happening again.[2][3]
>
> Is there any interest in seeing txmongo be developed further? What are
> some of the pain points that people would rather defer to thread PyMongo
> instead of using async txmongo?
>
> Cheers,
> Bret
>
> [1] https://github.com/fiorix/mongo-async-python-driver/pull/67
> [2]
> https://twistedmatrix.com/pipermail/twisted-python/2014-July/028489.html
> [3] https://github.com/twisted/ldaptor
>
> _______________________________________________
> Twisted-Python mailing list
> Twisted-Python at twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/twisted-python/attachments/20141230/5650faf5/attachment-0002.html>