[
https://issues.apache.org/jira/browse/HBASE-18020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16007267#comment-16007267
]
Sean Busbey commented on HBASE-18020:
-------------------------------------
Thanks for putting this up [~awleblang].
{quote}
2. Yay for using code from other projects, but are we sure we don't want to use
Python 3 for this? Lots of lines of code in this patch could be removed/the
whole thing made significantly more readable with some of the constructs
introduced in Python 3 and, seeing as how we control our test environment with
Docker and the like, there's no compelling reason not to use it. (Also, Python
3 has been out for ten years. It's time to use it.)
{quote}
A downside to switching to python 3 is that we'd have a hard time sharing stuff
back across other users of the tool. That's probably a minimal downside since
historically we haven't really done so.
Another would be that if we find a way to make this a general purpose tool
others can rely on, the likely home for it (Apache Yetus) purposefully sticks
to earlier pythons to give broader access (i.e. for use on OSes that still ship
Python 2 by default). Maybe this is also minimal since presumably we could
translate to python 2 if such a transfer of responsibility happened?
I'm not really a python person, so I'm happy to defer to others here.
> Update API Compliance Checker to Incorporate Improvements Done in Hadoop
> ------------------------------------------------------------------------
>
> Key: HBASE-18020
> URL: https://issues.apache.org/jira/browse/HBASE-18020
> Project: HBase
> Issue Type: Improvement
> Components: API, community
> Reporter: Alex Leblang
> Assignee: Alex Leblang
> Fix For: 2.0.0
>
> Attachments: HBASE-18020.0.patch
>
>
> Recently the Hadoop community has made a number of improvements in their api
> compliance checker based on feedback from the hbase and kudu community. We
> should adopt these changes ourselves.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
