[
https://issues.apache.org/jira/browse/IMPALA-13858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gowthami Bisati resolved IMPALA-13858.
--------------------------------------
Resolution: Resolved
The issue was fixed in the context of IMPALA-14501
> Change shebang of inline_pom.py to python
> -----------------------------------------
>
> Key: IMPALA-13858
> URL: https://issues.apache.org/jira/browse/IMPALA-13858
> Project: IMPALA
> Issue Type: Improvement
> Components: Infrastructure
> Reporter: Riza Suminto
> Assignee: Gowthami Bisati
> Priority: Trivial
> Labels: newbie, ramp-up
>
> I used inline_pom.py often when coding through remote VSCode. The script
> interpret using impala-python, requiring it to rebuild python2 virtualenv
> when switching between fairly different branch.
> {noformat}
> INFO:bootstrap_virtualenv:Creating python2 virtualenv
> INFO:bootstrap_virtualenv:Installing setuptools into the python2 virtualenv
> INFO:bootstrap_virtualenv:Installing packages into the python2 virtualenv
> INFO:bootstrap_virtualenv:Installing Kudu into the python2 virtualenv
> INFO:bootstrap_virtualenv:Installing python2 packages into the
> virtualenv{noformat}
> The script is simple. So , we should be able to avoid this by changing the
> shebang to plain python.
> {code:java}
> #!/usr/bin/env python {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
