[
https://issues.apache.org/jira/browse/LUCENE-9230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17039574#comment-17039574
]
ASF subversion and git services commented on LUCENE-9230:
---------------------------------------------------------
Commit b01d7cb79a00aae89c108cdf3185971ee68ecda6 in lucene-solr's branch
refs/heads/branch_8x from Robert Muir
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=b01d7cb ]
LUCENE-9230: explicitly call python version we want from builds
On newer linux distros, at least, 'python' now means python3. So
we can't rely on what version of python it will invoke (at least for a
few years).
For example in Fedora Linux:
https://fedoraproject.org/wiki/Changes/Python_means_Python3
For python2.x code, explicitly call 'python2.7' and for python3.x code,
explicitly call 'python3'.
Ant variable names are cleaned up, e.g. 'python.exe' is renamed to
'python2.exe' and 'python32.exe' is renamed to 'python3.exe'. This also
makes it easy to identify remaining python 2.x code that should be
migrated to python 3.x
> gradle moman fails on my machine, assumes python -> python2
> -----------------------------------------------------------
>
> Key: LUCENE-9230
> URL: https://issues.apache.org/jira/browse/LUCENE-9230
> Project: Lucene - Core
> Issue Type: Task
> Reporter: Robert Muir
> Priority: Major
> Attachments: LUCENE-9230.patch, LUCENE-9230.patch, LUCENE-9230.patch
>
>
> python2 is EOL and many distros are transitioning {{python}} to really invoke
> python3. So the scripts fail on wrong syntax in such cases. This happens for
> me if i try {{gradle moman}}.
> I think as a first step, we should explicitly call {{python2}} for any
> python2 scripts, and {{python3}} for python3 scripts?
> cc [~mikemccand]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
