<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
Shame on me for not reading your entire mail before replying.
<div class=""><br class="">
</div>
<div class="">You could set your PATH before invoking `make`...?</div>
<div class=""><br class="">
</div>
<div class="">We could probably also do something like `make PYTHON=/path/to/your/python3 cleandoc`, if that would be helpful. Let me know.</div>
<div class=""><br class="">
</div>
<div class="">
<div><br class="">
<blockquote type="cite" class="">
<div class="">On Dec 24, 2019, at 5:20 PM, Jeff Squyres <<a href="mailto:jsquyres@cisco.com" class="">jsquyres@cisco.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
The key is in the output:
<div class=""><br class="">
</div>
<div class=""><span style="caret-color: rgb(0, 0, 0); font-family: Menlo-Regular; font-size: 18px;" class="">raise RuntimeError('This python installation is too old! '</span><br style="caret-color: rgb(0, 0, 0); font-family: Menlo-Regular; font-size: 18px;" class="">
<span style="caret-color: rgb(0, 0, 0); font-family: Menlo-Regular; font-size: 18px;" class="">RuntimeError: This python installation is too old! Use Python 3.7 or later</span></div>
<div class=""><font face="Menlo-Regular" size="4" class=""><span style="caret-color: rgb(0, 0, 0);" class=""><br class="">
</span></font></div>
<div class=""><font face="Menlo-Regular" size="4" class=""><span style="caret-color: rgb(0, 0, 0);" class="">You need at least Python 3.7.</span></font></div>
<div class=""><font face="Menlo-Regular" size="4" class=""><span style="caret-color: rgb(0, 0, 0);" class=""><br class="">
</span></font>
<div class=""><br class="">
<blockquote type="cite" class="">
<div class="">On Dec 22, 2019, at 4:11 PM, Guillaume Mercier via mpi-forum <<a href="mailto:mpi-forum@lists.mpi-forum.org" class="">mpi-forum@lists.mpi-forum.org</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class=""><br class="">
Hello Jeff,<br class="">
<br class="">
I followed your instructions, but I'm stuck with the make cleandoc command in your Git repo:<br class="">
<br class="">
<br class="">
make rendered-backend BINDING_RENDER_VERSION=3.1<br class="">
make[1]: Entering directory '/home/mercierg/Developpement/Git/A_RELIRE/mpi-pythonization'<br class="">
Traceback (most recent call last):<br class="">
File "binding-tool/binding_prepass.py", line 109, in <module><br class="">
main()<br class="">
File "binding-tool/binding_prepass.py", line 96, in main<br class="">
common.check_for_sufficient_version()<br class="">
File "/home/mercierg/Developpement/Git/A_RELIRE/mpi-pythonization/binding-tool/common.py", line 38, in check_for_sufficient_version<br class="">
raise RuntimeError('This python installation is too old! '<br class="">
RuntimeError: This python installation is too old! Use Python 3.7 or later<br class="">
Makefile:396: recipe for target 'binding-prepass' failed<br class="">
make[1]: *** [binding-prepass] Error 1<br class="">
make[1]: Leaving directory '/home/mercierg/Developpement/Git/A_RELIRE/mpi-pythonization'<br class="">
Makefile:412: recipe for target 'rendered-31' failed<br class="">
make: *** [rendered-31] Error 2<br class="">
<br class="">
I have python 3.7 and 3.8 installed but the default version is<br class="">
2.7.15+ and I don't want to change that.<br class="">
<br class="">
Is there a way to modify your scripts/makefiles so that I can force<br class="">
it to consider python 3.8 instead (and not change my system)?<br class="">
<br class="">
Thanks.<br class="">
Guillaume<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
On 12/18/19 8:47 PM, Jeff Squyres (jsquyres) via mpi-forum wrote:<br class="">
<blockquote type="cite" class="">Chapter Committees / Chairs --<br class="">
We need Chapter Committees to review their chapters in three sets of upcoming document-wide changes that are slated to be merged "soon".<br class="">
After you complete a review, please put an "X" in the corresponding row/column for your chapter and the specified PR in this Google spreadsheet <<a href="https://docs.google.com/spreadsheets/d/1qPAREYgeuSCMtU-EQniDilrHIYb8W0-f6Qzjp-UtnH8/edit?folder=1_LOwR_QeX_bwIe_eptiy0OxWaOvPQ8W8#gid=0" class="">https://docs.google.com/spreadsheets/d/1qPAREYgeuSCMtU-EQniDilrHIYb8W0-f6Qzjp-UtnH8/edit?folder=1_LOwR_QeX_bwIe_eptiy0OxWaOvPQ8W8#gid=0</a>> (including
an un-numbered chapter for partitioned communication). This will let us track what has been done / what still needs to be done.<br class="">
*_FIRST SET<br class="">
_*<br class="">
Bill Gropp (the MPI Standard document Editor) has two PRs with "ticket 0" changes. However, the changes are pervasive and touch a LOT of the document. We therefore need Chapter Committees to review their chapters in the following two PRs:<br class="">
1a. "Ticket 0 changes for MPI-4.x"<br class="">
<a href="https://github.com/mpi-forum/mpi-standard/pull/151" class="">https://github.com/mpi-forum/mpi-standard/pull/151</a><br class="">
1b. "Uniform style for Fortran code"<br class="">
<a href="https://github.com/mpi-forum/mpi-standard/pull/145" class="">https://github.com/mpi-forum/mpi-standard/pull/145</a><br class="">
Deadline: Jan 7, 2020<br class="">
(Yes, that's an early deadline, but we need time to merge these PRs and fix conflicts with the second set)<br class="">
*_SECOND SET<br class="">
_*<br class="">
The Pythonization group has Pythonized the bindings in the entire document. We've completed a first correctness pass over the work, but we need more eyes to compare the end result of our work to the (non-Pythonized) head of the mpi-4.x branch.<br class="">
To be clear: this review does not include Embiggening. It is more-or-less the "MPI-3.1" style of function bindings.<br class="">
See this wiki page for instructions <https://github.com/mpiwg-large-count/large-count-issues/wiki/pythonizing-initial-review>.<br class="">
For additional information, also see the Pythonization slides presented at the Forum last week <https://docs.google.com/presentation/d/1QZyh6TbjDMu7mEcNqBFfe9fFOltaCtxgZ2ZODzdtDpI/edit#slide=id.g5d01a902fe_0_69>. If you have any questions or problems, let
us know in the Embiggening WG.<br class="">
If you just want to compare the rendered PDF:<br class="">
* Here's a PDF from the head of the mpi-4.x branch<br class="">
<https://aws.open-mpi.org/~jsquyres/forum-unofficial/mpi-report-mpi4xhead-d8ad059.pdf> (i.e.,<br class="">
old/original LaTeX)<br class="">
* Here's a PDF from the head of the Pythonization branch<br class="">
<https://aws.open-mpi.org/~jsquyres/forum-unofficial/mpi-report-d8ad059-pythonized-NOT-embiggened.pdf><br class="">
/_with no Embiggening_/ (i.e,. new/Python-rendered LaTeX)<br class="">
Deadline: 21 Jan, 2020<br class="">
This gives us time to finalize everything before the T-2 week deadline for the Portland Forum meeting.<br class="">
*_NOTE:_* At the ABQ Forum meeting, I asked you to commit/PR your approvals.json file that resulted from running the tool. This is no longer necessary -- please just mark the google spreadsheet as described above.<br class="">
*_THIRD SET_*<br class="">
After Pythonization comes Embiggening. We need Chapter Committees to review their chapters to ensure that API parameters were embiggened properly.<br class="">
You can do this by finding all "POLY" kinds in the Pythonized LaTeX bindings, and you can see 2xC bindings and 2xF08 bindings in the rendered PDF in your chapter. If you have any questions or problems, let us know in the Embiggening WG.<br class="">
Also check that the existing MPI-3.1 "_x" functions -- and their corresponding non-"_x" versions -- are all rendered correctly.<br class="">
If you just want to compare the rendered PDF:<br class="">
* Here's a PDF from the head of the mpi-4.x branch<br class="">
<https://aws.open-mpi.org/~jsquyres/forum-unofficial/mpi-report-mpi4xhead-d8ad059.pdf> (i.e.,<br class="">
old/original LaTeX)<br class="">
* Here's a PDF from the head of the Pythonization branch<br class="">
<https://aws.open-mpi.org/~jsquyres/forum-unofficial/mpi-report-d8ad059-pythonized-and-EMBIGGENED.pdf><br class="">
/_with Embiggening enabled_/ (i.e,. new/Python-rendered LaTeX)<br class="">
Deadline: 21 Jan, 2020<br class="">
You can probably review the second and third sets in a single pass through the text.<br class="">
-- <br class="">
Jeff Squyres<br class="">
jsquyres@cisco.com <mailto:jsquyres@cisco.com><br class="">
_______________________________________________<br class="">
mpi-forum mailing list<br class="">
mpi-forum@lists.mpi-forum.org<br class="">
https://lists.mpi-forum.org/mailman/listinfo/mpi-forum<br class="">
</blockquote>
_______________________________________________<br class="">
mpi-forum mailing list<br class="">
<a href="mailto:mpi-forum@lists.mpi-forum.org" class="">mpi-forum@lists.mpi-forum.org</a><br class="">
<a href="https://lists.mpi-forum.org/mailman/listinfo/mpi-forum" class="">https://lists.mpi-forum.org/mailman/listinfo/mpi-forum</a><br class="">
</div>
</div>
</blockquote>
</div>
<br class="">
<div class=""><span class=""><br class="">
-- <br class="">
</span><span class="">Jeff Squyres<br class="">
</span><span class=""><a href="mailto:jsquyres@cisco.com" class="">jsquyres@cisco.com</a></span>
</div>
<br class="">
</div>
</div>
</div>
</blockquote>
</div>
<br class="">
<div class=""><span class=""><br class="">
-- <br class="">
</span><span class="">Jeff Squyres<br class="">
</span><span class=""><a href="mailto:jsquyres@cisco.com" class="">jsquyres@cisco.com</a></span>
</div>
<br class="">
</div>
</body>
</html>