python bindings: CPython order

* Changed the order of python versions the configure/make process
  checks for, placing Python 3.7 ahead of 3.6.
* Updated the HOWTO documentation to reflect this change.

Tested-by: Ben McGinnes <[email protected]>
Signed-off-by: Ben McGinnes <[email protected]>

1 files changed, 26 insertions, 7 deletions

diff --git a/doc/gpgme-python-howto.texi b/doc/gpgme-python-howto.texi
index 5f33f5d1..c88c7460 100644
--- a/doc/gpgme-python-howto.texi
+++ b/doc/gpgme-python-howto.texi
@@ -257,6 +257,9 @@ The release of Python 3.7.0; which appears to be working just fine
 with our bindings, in spite of intermittent reports of problems for
 many other Python projects with that new release.
 @item
+Python 3.7 has been moved to the head of the specified python
+versions list in the build process.
+@item
 In order to fix some other issues, there are certain underlying
 functions which are more exposed through the @ref{Context, , gpg.Context()}, but
 ongoing documentation ought to clarify that or otherwise provide the
@@ -521,9 +524,25 @@ For Python 2 it checks for these executables in this order: @samp{python},
 @samp{python2} and @samp{python2.7}.
 
 For Python 3 it checks for these executables in this order: @samp{python3},
-@samp{python3.6}, @samp{python3.5}, @samp{python3.4} and @samp{python3.7}.@footnote{As Python 3.7 is a very recent release, it is not given
-priority over 3.6 yet, but will probably be prioritised by the release
-of Python 3.7.2.}
+ @samp{python3.7}, @samp{python3.6}, @samp{python3.5} and @samp{python3.4}.@footnote{With no issues reported specific to Python 3.7, the release of
+Python 3.7.1 at around the same time as GPGME 1.12.0 and the testing
+with Python 3.7.1rc1, there is no reason to delay moving 3.7 ahead of
+3.6 now.  Production environments with more conservative requirements
+will always enforce their own policies anyway and installation to each
+supported minor release is quite possible too.}
+
+On systems where @samp{python} is actually @samp{python3} and not @samp{python2} it
+may be possible that @samp{python2} may be overlooked, but there have been
+no reports of that actually occurring as yet.
+
+In the three months or so since the release of Python 3.7.0 there has
+been extensive testing and work with these bindings with no issues
+specifically relating to the new version of Python or any of the new
+features of either the language or the bindings.  This has also been
+the case with Python 3.7.1rc1.  With that in mind and given the
+release of Python 3.7.1 is scheduled for around the same time as GPGME
+1.12.0, the order of preferred Python versions has been changed to
+move Python 3.7 ahead of Python 3.6.
 
 @menu
 * Installing GPGME::
@@ -1636,10 +1655,10 @@ else:
     pass
 @end example
 
-It is important to note that the result will only return @samp{None} when a
-pattern has been entered for @samp{logrus}, but it has not matched any
-keys. When the search pattern itself is set to @samp{None} this triggers
-the exporting of the entire public keybox.
+It should be noted that the result will only return @samp{None} when a
+search pattern has been entered, but has not matched any keys.  When
+the search pattern itself is set to @samp{None} this triggers the exporting
+of the entire public keybox.
 
 @example
 import gpg