Github user spmallette commented on the issue:
https://github.com/apache/tinkerpop/pull/682
I've dug into supporting `BigDecimal` directly and it's turning into a mess
a bit. Python does have `Decimal` class which is like `BigDecimal` but it
doesn't serialize through the standard JSON processor:
https://stackoverflow.com/questions/1960516/python-json-serialize-a-decimal-object
so I coerced to float to match our extended module format:
http://tinkerpop.apache.org/docs/current/dev/io/#_bigdecimal
for a number in the `@value`. That sorta worked, but it then causes a loss
in precision anyway. I think it's just better to go with what I said before.
Just coerce the `BigDecimal` groovy pushes on us to double internally and then
it all just works. The test should not explicitly test `BigDecimal`. It should
test:
```groovy
g.withSack(2).V().sack(Operator.div).by(constant(3.0)).sack()
```
which in Java will just test double stuff, but in Groovy it will produce a
`BigDecimal` and our code gets tested. Does that make sense?
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
