The server won't reject `g:Int32` if it's a byte size value but it won't interpret it as a java `Byte`. This change just allows python to interpret/send the type. I'm not sure what is a breaking change here though. Right now, if Gremlin Server sends a `gx;Byte` python can't deserialize it and gremlin-python has no way to send a single `gx:Byte`. isn't this an additive feature?
I suppose that maybe BigInteger might produce different behavior that could be considered breaking. Currently, `gx:BigInteger` coming from Gremlin Server won't be deserialized and I imagine results in error and if python has a number outside of 64bit size and sends it as `g:Long` it will fail to deserialize on Gremlin Server. So, behavior of numbers is a little different because they remove error conditions, but isn't that ok? or am i not thinking about something correctly? (entirely possibly that i am actually as i might be misunderstanding how python is handling some of this stuff given my middling knowledge of the language) [ Full content available at: https://github.com/apache/tinkerpop/pull/1060 ] This message was relayed via gitbox.apache.org for [email protected]
