Github user spmallette commented on the issue:
https://github.com/apache/tinkerpop/pull/415
@davebshow what are the risks of building python 2 and not 3 or the other
way around? will we easily break compatibility such that not building against
both on a constant basis will cause problems? or can building both be saved for
"integration tests" which run less frequently?
put in more context, is it worth extending the build time of `mvn clean
install` to cover both python 2 and 3?
I'm sorta hoping the answer is "no" and that we can make running "both"
part of integration tests only.
Also, what does python 2/3 compatibility mean for deployment? does anything
change in how this stuff goes up to pypi?
On the whole, this is most excellent btw. We really needed this. I do think
that we should try to figure out how all the test/deploy stuff gets settled
before merging though. I suggest we further wait for #416 to merge to master so
that you can rebase this branch. Then I can work with you to tweak the pom.xml
from there based on whatever is settled on for test/deploy issues.
---
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.
---
