Github user davebshow commented on the issue:
https://github.com/apache/tinkerpop/pull/415
Maintaining compatibility should be pretty simple, but as you can see from
the PR, there are little things that can go wrong. I think the main issue we
will run into with this library is numeric typing, and I think we are well on
our way to dealing with it.
Regarding the mvn build, I think we can just have it run against the
default Python installation for now, which is a bit more risky, but we can
mitigate the risk by running CI builds for multiple versions of Python. I also
like to test locally, I just spin up a server manually and run `python setup.py
test` against multiple versions of Python. This kind of multiple environment
testing is made easier using the tool `tox`, maybe we could look at adding this
as a requirement.
This shouldn't affect the deployment process at all. The only difference is
now we can add Python 3 to the package metadata.
---
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.
---
