Adding a Python version check #2
Conversation
Now checks the Python version is greater than 2.7
|
Can you put the pull-from-cbflib directly (instead of the horrible local tarball) into this pull request too? I'll merge it all into master and then squash-cherrypick-patch it into the 4.2 branch as a bug fix. |
|
A note on Python in MolProbity: A correct version of Python (2.7.8) for use with MolProbity is supplied with cctbx. This Python is made available when the cctbx environment is sourced, and should be used for all cctbx and MolProbity operations. If a machine's local Python (rather than the cctbx-supplied Python) is being used by MolProbity, that is probably a bug and we'd appreciate knowing where this occurs. By my understanding, if everything is set up correctly, version-checking Python should not be necessary. |
|
I believe it is the configure script itself that requires Python 2.7. I'll check tomorrow to see if Apache is successfully using the cctbx-supplied Python... Merlin Hartley
|
|
The downside to this is that I'm using wget because of SourceForge redirections not working under curl... perhaps svn would be better? Merlin Merlin Hartley
|
Due to MolProbity's use of "list comprehension" (which could alternatively be replaced with 'for' loops) it therefore requires Python 2.7 or newer.
This fork merely adds a python version check to the configure script which exits before going any further.