Re: [Twisted-Python] Using ldapbindingchecker (part of ldaptor) with Twisted.

[bret curtis]

On Wed, Feb 4, 2015 at 2:46 PM, David Shepherd  wrote:

> I am looking for any examples of using the ldapbindingchecker to
> authenticate a custom SSH Server written with Twisted and Python 2.7. At
> the moment I am trying to hack an existing SSHD example in the Twisted
> O'Reilly book.  The docs refer to a "cfg" but I cannot find where it
> discusses what CFG actually is ?
>
>
I've yet to really dig into the code in that area of Ldaptor yet, but I
believe this might be what you want:

ldapChecker = LDAPBindingChecker(ldaptor.config.LDAPConfig())
p.registerChecker(ldapChecker)

or

cfg = LDAPConfig()
checker = LDAPBindingChecker(cfg)
realm = TODOGetRidOfMeRealm(config=cfg)
porta = portal.Portal(realm)
porta.registerChecker(checkers.AllowAnonymousAccess(),
credentials.IAnonymous)
porta.registerChecker(checker)

> I seem to need a service account to authenticate with the
> ldapbindingchecker so I can decide my user accound and password are valid
> over ldap. Where is this defined and what is the format ? I have found the
> global.cfg file and that gets me part of the way there but effectively I
> still cannot set a password. Can anyone help ?
>
>  Looking here:
http://ldaptor.readthedocs.org/en/latest/_modules/ldaptor/checkers.html
seems to indicate that you need to pass in your credentials. There are a
few TODO items in here as well.

I hope this gets you started into a better direction! I hope there are
others that can chime in as well

Cheers,
Bret

references:
https://twistedmatrix.com/pipermail/twisted-python/2005-November/011928.html
https://searchcode.com/codesearch/view/15584430/
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] twisted and twisted-infra organizations on GitHub

[bret curtis]

On Fri, Apr 24, 2015 at 10:54 AM, Gelin Yan  wrote:
>
> Hi Glyph
>
>  off-topic a bit. I care about txmongo. I actually plan to use it in
> production soon.
>
> Regards
>
> gelin yan
>
>
Glad you do! :D  We use it in production as well!  Just landed MongoDB 3.x
support, but we've still have a way to go to make it 1:1 with PyMongo.

As for an apart ecosystem organization, I don't see any problems with
moving yet again. ;)  I just question the necessity of it right now, it
isn't like we are endlessly scrolling through pypi packages.

Cheers,
Bret
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] twisted ldaptor

[bret curtis]

Hello there,

if you wish to make a pull request, file a bug report or ask Ldaptor
specific questions, you can contact the developer directly here:
https://github.com/twisted/ldaptor/issues

Not everyone who works on Ldaptor is a member of this mailing list.

I'll try to answer inline:

On Sat, May 2, 2015 at 12:37 PM,  wrote:

>
> i'm currently investigating how to add ldap server support to OTPme (
> https://www.otpme.org) as i want to extend it to be a complete
> authentication/authorization system including some kind of directory
> service. so i started working on integration with ldaptor. my first
> problem, adding search support, is partly solved now. i've checked
> ldifftree.py and after some debugging i got a search() method that is able
> to do an indexed search of OTPme's directory (which is not in svn yet)
> which allows fast search results for a directory with more than 2048 users.
>
>
Congratulations! :) How are you going about this? Are these additions
backwards compatible with OpenLDAP? Are you also writing test-cases to
cover these?


> but as this is just a start there will be more problems to solve i guess.
>

There always are, when I first started using Ldaptor, startTLS was broken
which was a requirement for me to do any work with it.


> one issue i have is that an ldapsearch against ldaptor which requests just
> some attributes instead of all always returns all object attributes.
> for example the ldapsearch below returns the complete ldif of each found
> user in ldaptor (tested also with ldiftree.py):
> ldapsearch -H ldap://localhost:8080 -b "ou=users,dc=domain,dc=intern" -w
> abcd -x '(uid=*)' givenName
> Running the same search against my openldap server it returns just the dn
> and givenName attributes of each found user.
> Is this a missing feature or do i just miss something in my db class?
>

Please file an issue on github with an example (ldif entries in a txt file
would work) that can be used to test with a real OpenLDAP server. Then the
ldapsearch like you provided above and a snippit of your ldaptor code so we
can try to reproduce it.


> another important part i haven't looked at yet is how to implement
> authentication. as OTPme focus on OTPs i dont want to add any user
> passwords to the ldap tree. the smoothest solution would be to get
> username+OTP from ldaptor to do authentication. maybe you can give me some
> hints in the right direction? :)


Another issue/question for github, there are others that have spent more
time in this area of the codebase.


> and the last question for now is related the licensing. OTPme is licensed
> under GPLv2. do i run into any licensing issues when using ldaptor with
> OTPme?
>
>
Ldaptor is MIT/Expat license, if you would like to commit code then that
too must be MIT/Expat otherwise it won't be accepted. As for using Ldaptor
to talk with OTPme, there shouldn't be a license problem as they are two
separate applications/services. What exactly is your concern there?



> regards
> the2nd
>
>
Cheers,
Bret
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] Twisted 15.2 Release Announcement

[bret curtis]

Great job! :)

Cheers,
Bret

On Tue, May 19, 2015 at 8:14 AM, HawkOwl  wrote:

> On behalf of Twisted Matrix Labs, I'm honoured to announce the release of
> Twisted 15.2.
>
> Bringing not only headlining features but also a lot of incremental
> improvements, this release has got plenty to like:
>
> - twisted.logger has landed! This is a brand-new, feature-rich logging
> framework.
> - Python 3.4 is now a supported platform for all the Py3 ported modules.
> - twisted.trial.unittest.TestCase's assertEqual, assertTrue, and
> assertFalse methods now pass through the standard library's more
> informative failure messages.
> - twisted.python.filepath.FilePath now supports Unicode (text) paths
> properly, and includes as{Bytes,Text}Mode methods for interacting with APIs
> that require a text/bytes-only FilePath.
> - twisted.mail.smtp.sendmail now supports ESMTP and provides a high-level
> interface for sending mail.
> - The following parts of Twisted are now ported to Python 3:
>- twisted.internet.process
>- twisted.cred.credentials
>- twisted.python.modules
>- twisted.internet.kqreactor
>- twisted.internet.endpoints.ProcessEndpoint
>- twisted.web.static
> - Over 50 tickets closed since 15.1.
>
> You can find the downloads at https://pypi.python.org/pypi/Twisted (or
> alternatively http://twistedmatrix.com/trac/wiki/Downloads).
>
> Many thanks to everyone who had a part in this release - the supporters of
> the Twisted Software Foundation, the developers who contributed code as
> well as documentation, and all the people building great things with
> Twisted!
>
> Twisted Regards,
> HawkOwl
>
> ___
> Twisted-Python mailing list
> Twisted-Python@twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
>
>
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] Call for volunteers: fundraising

[bret curtis]

For me as well please. :)

Cheers,
Bret

On Mon, Oct 5, 2015 at 9:52 PM, Glyph Lefkowitz 
wrote:

>
> > On Oct 4, 2015, at 8:04 AM, John Aherne  wrote:
> >
> > OK.
> >
> > That makes sense.
> >
> > Do we have a list of current sponsors and what they have contributed
> stored anywhere.
> >
> > Do we have a list of email addresses of people using twisted in a
> serious application that might be contacted.
> >
> > Then a list of people that have contributed to twisted so are making a
> contribution that is not strictly financial.
> >
> > If not, then we have to try and find out who are using twisted for a
> business application.
> >
> > Any pointers to where I can find this information will be helpful.
>
> We do have all of those things; I can put you in touch with our contact at
> the SFC if you want to get started :-).  Shall I do so?
>
> -glyph
>
>
>
> ___
> Twisted-Python mailing list
> Twisted-Python@twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
>
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] txmongo vs. pymongo + callInThread

[bret curtis]

We're not sure about what OP has done, but if there is ever anything
lacking in TxMongo... please open an issue/ticket with us over at:
https://github.com/twisted/txmongo

Cheers,
Bret

On Wed, Oct 7, 2015 at 8:18 PM, Jonathan Vanasco 
wrote:

>
> On Dec 21, 2014, at 4:05 PM, Clayton Daley 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.
>
> I know thread is a bit old, but I'm wondering if the OP ended up using
> callInThread or not , and if there were any issues.
>
> I started working on a txmongo solution to offload some storage, but then
> realized I was already in a deferred thread (to handle blocking operations)
> and i probably should be using pymongo.
>
>
> ___
> Twisted-Python mailing list
> Twisted-Python@twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
>
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] txmongo vs. pymongo + callInThread

[bret curtis]

There is one thing that TxMongo does that PyMongo, Motor and the rest don't
do: handle deadlines and timeouts.

We're (HGST/WesternDigital) using MongoDB (with WiredTiger) in real-time
applications and one of our requirements was to honour application set
deadlines (or timeouts) on a per-call basis.

So if you are interested in that, we have it. :)

For those just tuning in...
Timeout: how many seconds the call is allowed run before raising an error.
Deadline: a time (unix timestamp) in the future that the call is allowed to
run before raising an error.

We take advantage of Twisted's native deferred cancellation mechanism in
addition to validation checks that no modifications happen to MongoDB when
a TimeExceeded is raised.

We've been very satisfied with how MongoDB has performed (post 3.0/WT)
along with TxMongo and Twisted.

Cheers,
Bret


On Fri, Oct 9, 2015 at 7:52 PM, Jonathan Vanasco 
wrote:

>
> On Oct 9, 2015, at 1:06 PM, Clayton Daley wrote:
>
> I (OP) was looking into these libraries/options as part of a side project
> that's been delayed by real work.  I'm also relegating Mongo to a caching
> layer after stumbling upon Sarah Mei's "Why You Should Never Use MongoDB"
> and realizing I was going to have the exact same problems
>
> Thanks for the update!
>
> FWIW, (sorry, non-twisted!)  if you want to avoid mongodb:
>
> 1. We use redis for KV caching, and its really, really, really fast.
> 2. Riak can use LevelDB as a backing store -- leveldb supports snappy
> compression on documents
> 3. If you need the document search, i really like Elastic
>
> I don't really like/trust mongodb from past experience myself.  I would
> normally not use it for anything other than a read-through cache... except
> for my current need.  We have a web spider and need to archive the
> snapshots.  WireTiger, which was bought by mongodb and integrated into the
> 3.x branch, is the only storage backend I've found that will do "bucket
> level compression".  I forget if it's applied on pages or blocks, but it
> will basically apply zlib or snappy compression onto sets of documents.  I
> looked for weeks on something that could do that, it was the only option.
> We did a lot of storage tests on our typical data, and bucketed compression
> saves way more space than document compression or document compression
> using a seed.
>
> ___
> Twisted-Python mailing list
> Twisted-Python@twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
>
>
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] memory leaks

[bret curtis]

Isn't this a duplicate of my "memory leak" bug report from about 11 months ago?
https://twistedmatrix.com/trac/ticket/8164

Glype's last comment on the ticket was:
Now, again, I want to be clear that the buffer size here is still a
bug, and we vastly mis-estimated a reasonable size.

The end result was that Hawkie indicated that there was a 64K buffer
of variable length logs. Because they are variable in length means
they use either almost no memory to potentially causing the OOM to
come along. What wasn't clear was if you reached the 64K limit, does
Twisted then just drop the rest of the logs are is the buffer a
circular one and drops the first entry to accommodate the last entry
or something else entirely?

Cheers,
Bret


On Tue, Dec 6, 2016 at 7:58 AM, Glyph Lefkowitz  wrote:
>
> On Dec 5, 2016, at 10:18 PM, Amber Hawkie Brown 
> wrote:
>
>
> On 6 Dec. 2016, at 17:09, Glyph Lefkowitz  wrote:
>
>
> twisted.logger._initialBuffer can consume a surprisingly large amount of
> memory if logging is not initialized
>
>
> The way that `twisted.logger` is supposed to work is that at process startup
> time, the global log observer has a ring buffer for any messages emitted
> before logging is initialized, and emit those messages to the initial set of
> log observers passed to `globalLogBeginner.beginLoggingTo`.
>
> The size of this buffer (in `twisted.logger._buffer._DEFAULT_BUFFER_MAXIMUM`
> is 65535.  This value was selected arbitrarily, probably because somebody
> (me or wsanchez) thought "huh, yeah, 64k, that's probably a fine number);
> but of course, that's 64k ''bytes''.
>
> If this were a buffer of actual formatted log messages, of say 200 bytes
> each, that would be about 13 megabytes, which is maybe an acceptable amount
> of RAM to spend on a log buffer.
>
> However, it isn't that.  It's a buffer of 64k log ''events'', each of which
> probably has a `log_logger` and `log_source` set, each of which is an object
> attached to potentially arbitrary data.  For example, every `Factory` that
> starts up logs something, which means you're holding on to an instance, and
> an instance dictionary, and the protocol instance, and the protocol instance
> dictionary.  Worse yet, any logged ''failures'' might hold on to all the
> stuff on their stack.
>
> Add it all up and you end up with a log buffer totaling in the hundreds of
> megabytes, or even gigabytes, once it's full.  In an application that
> naively uses Twisted without ever initializing logging, this hangs around
> forever.
>
> This buffer should probably be a ''lot'' smaller, and we might want to emit
> a warning when it fills up, reminding people that it is ''only polite'' to
> start up the logging subsystem, even just to explicitly throw logs away.
>
>
> I fixed trac: https://twistedmatrix.com/trac/ticket/8936#ticket
>
>
> Thanks!
>
> By "Fixed" I take it you mean rolled back, via:
>
> trac@dornkirk:~$ ./virtualenv/bin/pip freeze | grep Trac==
> Trac==1.0.13
>
>
> and
>
> https://github.com/twisted-infra/braid/commit/c2d393fd501c6464b1b475eff214cab64f13ee2a
>
>
> Don't get me wrong, I'm not complaining :). This is certainly the right
> thing to do for now.  But I'm wondering if you know what's wrong with 1.2 so
> we can upgrade soonish?
>
> -glyph
>
>
> ___
> Twisted-Python mailing list
> Twisted-Python@twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
>

___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] bringing LDAP back

[Bret Curtis]

Hello Twistrons,

I admit to being "that guy" who pushed this project forward and see
Ldaptor find a new home (and focus) in Twisted and I'm glad that Tommi
and Glyph are on board. I'm also glad that AntonG has also re-licensed
his changes as MIT and has written consent from another developer as
well.

With that said, lets get this ball rolling.

Firstly, we'll need a repo to get started with. My company (Amplidata)
has it's own fork, but I think it is best we start with a clone, not a
direct fork as github would have us do, of tv42s repo. I've had
experience with a popular fork was 2 years further along than the
original, yet this fork would only be on the second page of search
results.

We can either:
1) Move (donate) tv42's repo to Twisted, this means that all links to
tv42/Ldaptor would automatically be forwarded to Twisted/Ldaptor.
2) Twisted creates it's own Ldaptor repo, I or someone else clones
this and then merge TV42's repo in, commit/push and file a merge
request with Twisted/Ldaptor.

We're, of course, open to other suggestions, but those two above seem
the best options. From there, we can start dealing with other issues
such as:

A) What to do with the UI part of Ldaptor. Who, if anyone, still uses
it? Do we trim it out or just mark it as deprecated since it relies on
old versions of twisted and nevow.
B) Pull in downstream patches from Redhat, SuSE and Debian.
C) Replace remaining bits of non-MIT code.
D) Get back to tv42's Todo list. :)

Cheers,
Bret

On 28 June 2014 00:27, Glyph  wrote:
> Hello fellow Twistrons,
>
> A long time ago, for reasons we need not discuss here, the pure-python LDAP
> implementation within Twisted was pulled out into a separate package under a
> different license.
>
> Recently however, the authors of this LDAP code have generously re-licensed
> the code under a Twisted-compatible MIT license, both the original code at
> 
> and the more recent fork (which I believe has more users) at
> .  It seems as though there's
> even a solution for the problematic MD4 implementation here
> .
>
> Since there's no active, central hub for ldaptor development, I think we
> should pull it into the Twisted org on Github, and some of the folks on the
> Cc: line have volunteered to help with that.
>
> Does that sound good to everybody?  (Are you excited!!!?)
>
> It's also a possibility that we could distribute a for-real SSO back-end
> with Cred using this, which I'm pretty excited about.
>
> -glyph

___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] bringing LDAP back

[Bret Curtis]

On 1 July 2014 21:06, Glyph Lefkowitz  wrote:
>
> On Jul 1, 2014, at 11:57 AM, Tommi Virtanen  wrote:
>
>> On Tue, Jul 1, 2014 at 11:49 AM, Glyph Lefkowitz
>>  wrote:
>>> (Also, please be careful, and don't push to the main Twisted repo if you
>>> work on Twisted.  Github is super obnoxious about mirroring; we can't turn
>>> off pull requests and we can't turn off pushes even though it's really
>>> supposed to be a read-only mirror right now, and pushes to that repository
>>> break our SVN integration.)
>>
>> I'm no Github expert, but you should be able to just make people be in
>> a non-"Owners" team, and then selectively give that team push access
>> to only the repos you want.
>>

Not only this, I still like the idea of forking from Twisted/ldaptor
in my own repo and working on my own branch. When finished, I usually
send a merge request upstream, in this case to Twisted/ldaptor. I
assume that it would either be accepted or rejected with comments.  If
this is too much overhead for you, then the below is a good idea and
give make us contributors.

>> The "Owners" team probably gives non-admin contributors too much power
>> in the first place.
>

This works by creating a team with 'write access' to twisted/ldaptor.
This would make you (Glyph) the gatekeeper (admin access by default)
in adding and kicking members out of the group. The rest of the world
is technically in the 'read access'  team as is the nature of open
organizations on github.

> This is indeed a better idea.
>
> I'll still need the list of names for that team though ;)

psi29a
https://github.com/psi29a

>
> -g

Cheers! :)

___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] bringing LDAP back

[Bret Curtis]

On 2 July 2014 00:45, Glyph Lefkowitz  wrote:
>
> I've made you a contributor to that repository, but I recommend that you do
> this anyway, and (for now) just merge your own PRs after a little while if
> nobody steps forward to review them.  Hopefully some more interested parties
> will arrive and allow for a nice review-driven process early though :-).
>

I've initialized the new repo with tv42's repo. It isn't a github
fork, but a mirror. I also tagged it with the 0.43 release since that
is the last known official release build.

>
>
>
> Let me know if I did this right:
>
> https://github.com/twisted/ldaptor
>
> -glyph

You've done is right and I've already github forked it (after I did
the above) and started to get down to business.

Whenever someone gets the chance, please check this out:
https://github.com/twisted/ldaptor/pull/1

The summary/comment pretty much sums up what we've talked about in the
list so far. I think once it is merged, it is a pretty good starting
place.

This has been tested against our project at Amplidata and with only 3
failing tests out of 337, we're doing really so far.

Going forward, here are some things I want to tackle:
1) Get those remaining 3 tests (or code it tests) fixed.
2) Follow up with Pypi about the semi-dead Ldaptor 0.53 release
3) Start the PEP8 process on the codebase
4) Help existing debian maintainer to transition to twisted's ldaptor
5) ?
... additional input from you guys would be awesome. :)

Cheers,
Bret

___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] bringing LDAP back

[Bret Curtis]

Hello again,

I sent another pull request, this takes care of the last 3 failing
tests and opens up an additional 50 tests that also pass now. We're
now at 387 tests!

https://github.com/twisted/ldaptor/pull/3

It is my recommendation that after this is reviewed and hopfully
commited that we make a branch and tag the release as 0.54.0. The
reason for the large jump is that antong's last semi-offical release
was 0.53 on PyPI. At this point we (myself and anyone else that wants
to help) should reach out to downstream projects (PyPI, Debian, and
etc.) to make them aware that Ldaptor development is again active.

I would also like to (ab)use github's issue tracker and milestones to
sort issues into queues. For example, the next milestone would be 0.55
with: https://github.com/twisted/ldaptor/issues/2  as the first real
issue to be tracked there. Another issue I'll file shortly will be
that we go through the code and start refactoring deprecated code like
I did for test_ldiftree.py.

Would you mind if I did this or would you rather someone else handle this?

Another question is that of documentation.  We could use sphinx to
handle this to autodoc our API and also include howtos and examples.
This can readily be used for html, pdf and man page generation which
would be handy for downstream.

What does everyone think?

Cheers,
Bret

___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] standard practices, was (bringing LDAP back)

[Bret Curtis]

On 8 July 2014 14:06,   wrote:
>
>
>
> On 11:30 am, hawk...@atleastfornow.net wrote:
>>
>> On 8 Jul 2014, at 5:26, Glyph Lefkowitz  wrote:
>>>
>>> On Jul 7, 2014, at 2:21 PM, exar...@twistedmatrix.com wrote:

 It might not be.  Now that so many new projects are being added to the
 github Twisted repository (and particularly, projects that have new
 contributors), perhaps it is (slightly past) time to set down some of these
 things officially?
>>>
>>>
>>> I think we should make a list of some suggestions before we try to make
>>> that list into an official policy.  Date-based version numbers is a good
>>> suggestion to start that list with :).
>>
>>
>> Maybe we need a Request For Comment/PEP-style way of formalising/proposing
>> policy? Django’s doing it as well, and it seems like a nice way of doing it.
>
>
> I don't see this as the necessary conclusion.  We're not arguing about what
> the policy should be yet.  I'm just saying it should be written down in one
> place - not smeared out across 10 years of mailing list archives.
>

Thankfully we're just just discussing it and not arguing about it,
hopefully in another thread. :)

Cheers,
Bret


>
> Jean-Paul
>
> ___
> Twisted-Python mailing list
> Twisted-Python@twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] bringing LDAP back

[Bret Curtis]

Right, so from what I read here then our official release to the world
will be 14.0, provided that Travis is green before 2015. ;)

Sound good?

Cheers,
Bret

On 7 July 2014 23:26, Glyph Lefkowitz  wrote:
> On Jul 7, 2014, at 2:21 PM, exar...@twistedmatrix.com wrote:
>
> It might not be.  Now that so many new projects are being added to the
> github Twisted repository (and particularly, projects that have new
> contributors), perhaps it is (slightly past) time to set down some of these
> things officially?
>
>
> I think we should make a list of some suggestions before we try to make that
> list into an official policy.  Date-based version numbers is a good
> suggestion to start that list with :).
>
> -g
>
> ___
> Twisted-Python mailing list
> Twisted-Python@twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
>

___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] txmongo vs. pymongo + callInThread

[bret curtis]

On Tue, Dec 23, 2014 at 7:51 AM, Gelin Yan  wrote:

>
>
> On Mon, Dec 22, 2014 at 5:05 AM, Clayton Daley 
> 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@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

[Twisted-Python] bringing TxMongo back from the brink!

[bret curtis]

Hello fellow Twistrons,

let me introduce TxMongo, an asynchronous MongoDB client that has come up a
few times in discussion on this list. The project isn't dead, it has been
contributed to over the years though while the original author, Alexandre
Fiori, reviews and accepts the pull requests.

After helping make a new 0.6 release, with SSL support, we talked about the
possibility of Amplidata taking on the future development of TxMongo and
breathing new life into the project. We just need a new place to host the
'official' repository and reign in all the various forks. What better place
to do that than Twisted's github organization, similar in nature to what
was done with Ldaptor.

Amplidata will be the primary driver in development, but new feature
requests and patches are of course, always welcome. :)

So what does everyone think of this?
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] bringing TxMongo back from the brink!

[bret curtis]

On Fri, Jan 30, 2015 at 4:19 AM, Glyph  wrote:

>
>
> On Jan 29, 2015, at 12:05 PM, Clayton Daley 
> wrote:
>
> Unless Twisted loves the idea of hosting this, it might make more sense to
> start a TxCommons (like https://github.com/ZF-Commons). This shifts the
> emphasis away from the Twisted and onto the Commons, including:
>
>- The lower (or lack of) "core support" commitment.  The Commons can
>still highlight "supported" projects (by the commons or outside
>organizations), but it's more transparent about the status relative to 
> core.
>- A significantly lower participation/contribution barrier that isn't
>interrelated with the politics (and justifiably high standards) of core.
>- A central place to find Tx libraries that actively welcomes new
>additions.
>   - My twisted-pyro and twisted-mandrill are so-so examples of what I
>   mean.  If they were a little more mature, it'd be better for someone to
>   find and improve these libraries than start over from scratch.
>   - More importantly, users would know that the project won't
>   fragment if I'm not proactively maintaining it. They can always become 
> an
>   active participant in the Commons and move business along.  Obviously, I
>   relinquish that control if and when I contribute it (or the commons
>   establishes an official fork).
>
> Clayton Daley
>
>
> So, I don't mind the idea of Twisted hosting it for now, but you make a
> good point.  The Twisted org on Github is presently hosting quite a few
> things, with varying degrees of association with various subsets of the
> core developers.
>
> Since ldaptor already moved to this org, I think we should probably just
> move this as well, and then move things *out* later once we have
> established a Commons org and figured out how we want to administer it.
>
> BTW: any chance of renaming those TxPyro and TxMandrill? :)
>
> -glyph
>
>
> ___
> Twisted-Python mailing list
> Twisted-Python@twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
>
>

If ever the Twisted org on github feels a bit crowded, I think a break out
to something like TxCommons is a good idea.

Cheers,
Bret
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] txmongo vs. pymongo + callInThread

[bret curtis]

On Sat, Jan 31, 2015 at 7:37 PM, Gelin Yan  wrote:

>
>
> On Tue, Dec 30, 2014 at 5:50 PM, bret curtis  wrote:
>
>> On Tue, Dec 23, 2014 at 7:51 AM, Gelin Yan  wrote:
>>
>>>
>>>
>>> On Mon, Dec 22, 2014 at 5:05 AM, Clayton Daley 
>>> 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
>>
>>
>>
>  Hi Bret
>
>I am glad to know txmongo is still here. I used it several times a few
> years ago and was impressed by its speed (twice faster than pymongo &
> thread pool).
>
>  I hope txmongo can support the latest GEO index & replication.
>
> Regards
>
> gelin yan
>
>
Hello Gelin,

You should check out our other thread about getting TxMongo moved into
Twisted's github org.
https://twistedmatrix.com/pipermail/twisted-python/2015-January/029144.html

There is already some support for Geo and replication, but it could always
use more work. What is it specifically you would like to see, aside from
everything. ;)

https://github.com/fiorix/txmongo/blob/master/txmongo/filter.py
^--  Support for GEO2D and GEOHAYSTACK spatial indices were added in 2012.

When you specify your hosts in ConnectionPool, you can give it a full
mongodb URI that includes all your replication servers, even with SSL
support. It is smart enough to cycle through until it finds a master to
continue operations.

I'm still trying to a compile a list of pain points that people have that
can be addressed. The more specific, the better.

Cheers,
Bret
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python