GitHub user davebshow opened a pull request:

    https://github.com/apache/tinkerpop/pull/554

    TINKERPOP-1599 implement real gremlin-python driver

    https://issues.apache.org/jira/browse/TINKERPOP-1599
    
    This PR adds a better driver implementation for gremlin-python:
    
    - Uses a multi-threaded solution to provide asynchronous I/O
    - Decouples the underlying websocket client implementation from driver 
code, making it easy to plug in a different client
    - Makes it easy to plug in different protocols, like the Gremlin Server 
HTTP protocol.
    - Adds simple connection pooling used in concurrent requests, which 
increases driver performance with slow traversals
    - Improves driver tests by adding `pytest` fixtures and removing unneeded 
`unittest` code.
    
    This driver still isn't full featured compared to the Java driver, for 
example, it doesn't implement `Cluster` to use multiple hosts. But, it is 
considerably better than the old implementation, and as this was becoming a big 
PR, I figure we can add more features with subsequent PRs. 
    
    Also note, I know we are in code freeze right now, so I don't expect this 
to be reviewed/merged for 3.2.4, but I'm busy and I wanted to get this done so 
I can move on. 

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/apache/tinkerpop TINKERPOP-1599

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/tinkerpop/pull/554.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #554
    
----
commit b10d6048ced6de08c307b8b9382d67e97e2cb0ef
Author: davebshow <[email protected]>
Date:   2017-01-30T22:22:36Z

    added code for new driver, updated driver tests

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to