Good question - I'm not sure we can. What happens right now is you get syntax errors during the compile. I'll have to play and see if we can generate an error message before we hit that point.
On Mon, May 9, 2016 at 9:38 AM, Jeff Squyres (jsquyres) <jsquy...@cisco.com> wrote: > Is it possible to give a friendly error message at run time if you > accidentally run with Python 3.x? > > > > On May 9, 2016, at 12:37 PM, Ralph Castain <r...@open-mpi.org> wrote: > > > > Hi folks > > > > As we look at the Python client, there is an issue with the supported > Python version. There was a significant break in the user-level API between > Python 2.x and Python 3. Some of the issues are described here: > > > > https://docs.python.org/2/glossary.html#term-2to3 > > > > Noah and I have chatted about this, and we feel it may be best to just > lock-in on Python 2.x until an overwhelming reason arises for us to > transition to Python 3. At that time, we would have to do a backward-break > to update. > > > > The virtualenv content file (pyenv.txt) already reflects this > requirement, so folks who use virtual environments are set. > > > > Make sense? > > Ralph > > > > _______________________________________________ > > mtt-users mailing list > > mtt-us...@open-mpi.org > > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users > > Searchable archives: > http://www.open-mpi.org/community/lists/mtt-users/2016/05/0846.php > > > -- > Jeff Squyres > jsquy...@cisco.com > For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/ > > _______________________________________________ > mtt-users mailing list > mtt-us...@open-mpi.org > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users > Link to this post: > http://www.open-mpi.org/community/lists/mtt-users/2016/05/0847.php >