Shame on me for not reading your entire mail before replying. You could set your PATH before invoking `make`...?
We could probably also do something like `make PYTHON=/path/to/your/python3 cleandoc`, if that would be helpful. Let me know. On Dec 24, 2019, at 5:20 PM, Jeff Squyres <jsquy...@cisco.com<mailto:jsquy...@cisco.com>> wrote: The key is in the output: raise RuntimeError('This python installation is too old! ' RuntimeError: This python installation is too old! Use Python 3.7 or later You need at least Python 3.7. On Dec 22, 2019, at 4:11 PM, Guillaume Mercier via mpi-forum <mpi-forum@lists.mpi-forum.org<mailto:mpi-forum@lists.mpi-forum.org>> wrote: Hello Jeff, I followed your instructions, but I'm stuck with the make cleandoc command in your Git repo: make rendered-backend BINDING_RENDER_VERSION=3.1 make[1]: Entering directory '/home/mercierg/Developpement/Git/A_RELIRE/mpi-pythonization' Traceback (most recent call last): File "binding-tool/binding_prepass.py", line 109, in <module> main() File "binding-tool/binding_prepass.py", line 96, in main common.check_for_sufficient_version() File "/home/mercierg/Developpement/Git/A_RELIRE/mpi-pythonization/binding-tool/common.py", line 38, in check_for_sufficient_version raise RuntimeError('This python installation is too old! ' RuntimeError: This python installation is too old! Use Python 3.7 or later Makefile:396: recipe for target 'binding-prepass' failed make[1]: *** [binding-prepass] Error 1 make[1]: Leaving directory '/home/mercierg/Developpement/Git/A_RELIRE/mpi-pythonization' Makefile:412: recipe for target 'rendered-31' failed make: *** [rendered-31] Error 2 I have python 3.7 and 3.8 installed but the default version is 2.7.15+ and I don't want to change that. Is there a way to modify your scripts/makefiles so that I can force it to consider python 3.8 instead (and not change my system)? Thanks. Guillaume On 12/18/19 8:47 PM, Jeff Squyres (jsquyres) via mpi-forum wrote: Chapter Committees / Chairs -- We need Chapter Committees to review their chapters in three sets of upcoming document-wide changes that are slated to be merged "soon". 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 <https://docs.google.com/spreadsheets/d/1qPAREYgeuSCMtU-EQniDilrHIYb8W0-f6Qzjp-UtnH8/edit?folder=1_LOwR_QeX_bwIe_eptiy0OxWaOvPQ8W8#gid=0> (including an un-numbered chapter for partitioned communication). This will let us track what has been done / what still needs to be done. *_FIRST SET _* 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: 1a. "Ticket 0 changes for MPI-4.x" https://github.com/mpi-forum/mpi-standard/pull/151 1b. "Uniform style for Fortran code" https://github.com/mpi-forum/mpi-standard/pull/145 Deadline: Jan 7, 2020 (Yes, that's an early deadline, but we need time to merge these PRs and fix conflicts with the second set) *_SECOND SET _* 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. To be clear: this review does not include Embiggening. It is more-or-less the "MPI-3.1" style of function bindings. See this wiki page for instructions <https://github.com/mpiwg-large-count/large-count-issues/wiki/pythonizing-initial-review>. 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. If you just want to compare the rendered PDF: * Here's a PDF from the head of the mpi-4.x branch <https://aws.open-mpi.org/~jsquyres/forum-unofficial/mpi-report-mpi4xhead-d8ad059.pdf> (i.e., old/original LaTeX) * Here's a PDF from the head of the Pythonization branch <https://aws.open-mpi.org/~jsquyres/forum-unofficial/mpi-report-d8ad059-pythonized-NOT-embiggened.pdf> /_with no Embiggening_/ (i.e,. new/Python-rendered LaTeX) Deadline: 21 Jan, 2020 This gives us time to finalize everything before the T-2 week deadline for the Portland Forum meeting. *_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. *_THIRD SET_* After Pythonization comes Embiggening. We need Chapter Committees to review their chapters to ensure that API parameters were embiggened properly. 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. Also check that the existing MPI-3.1 "_x" functions -- and their corresponding non-"_x" versions -- are all rendered correctly. If you just want to compare the rendered PDF: * Here's a PDF from the head of the mpi-4.x branch <https://aws.open-mpi.org/~jsquyres/forum-unofficial/mpi-report-mpi4xhead-d8ad059.pdf> (i.e., old/original LaTeX) * Here's a PDF from the head of the Pythonization branch <https://aws.open-mpi.org/~jsquyres/forum-unofficial/mpi-report-d8ad059-pythonized-and-EMBIGGENED.pdf> /_with Embiggening enabled_/ (i.e,. new/Python-rendered LaTeX) Deadline: 21 Jan, 2020 You can probably review the second and third sets in a single pass through the text. -- Jeff Squyres jsquy...@cisco.com <mailto:jsquy...@cisco.com> _______________________________________________ mpi-forum mailing list mpi-forum@lists.mpi-forum.org https://lists.mpi-forum.org/mailman/listinfo/mpi-forum _______________________________________________ mpi-forum mailing list mpi-forum@lists.mpi-forum.org<mailto:mpi-forum@lists.mpi-forum.org> https://lists.mpi-forum.org/mailman/listinfo/mpi-forum -- Jeff Squyres jsquy...@cisco.com<mailto:jsquy...@cisco.com> -- Jeff Squyres jsquy...@cisco.com<mailto:jsquy...@cisco.com>
_______________________________________________ mpi-forum mailing list mpi-forum@lists.mpi-forum.org https://lists.mpi-forum.org/mailman/listinfo/mpi-forum
