[jira] [Commented] (TINKERPOP-2071) gremlin-python: the graphson deserializer for g:Set should return a python set

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TINKERPOP-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16654080#comment-16654080 ] 

ASF GitHub Bot commented on TINKERPOP-2071:
-------------------------------------------

aboudreault opened a new pull request #964: TINKERPOP-2071: gremlin-python: g:Set graphson deserializer should return a python set
URL: https://github.com/apache/tinkerpop/pull/964
 
 
   If there is additional documentation you would like somewhere... please, point me where.  

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> gremlin-python: the graphson deserializer for g:Set should return a python set
> ------------------------------------------------------------------------------
>
>                 Key: TINKERPOP-2071
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2071
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: python
>            Reporter: Alan Boudreault
>            Priority: Major
>             Fix For: 3.3.4
>
>
> This is something that has already been discussed. The reason that a g:Set is deserialized to a list is because Java can return some numerical values that are not differentiate by python. See TINKERPOP-1844 for more details.
> However, I think this is is not something very common so I would like to propose another behavior:
> 1. By default, always return a python set as normal for g:Set
> 2. When we detect the case described, log a warning and return a python list.
> 3. Document properly the limitation and the behavior of g:Set.
> Already discussed with Stephen and we think it's an acceptable behavior. I will provide a PR shortly.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)