GpgFrontend/gpgme
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

python: windows c and cython

Browse Source 
* added warning that he Windows C runtime issues will also affect use
  with Cython and that relying on binary installers would remove that
  possible use case.
This commit is contained in:
Ben McGinnes 2018-12-05 10:51:59 +11:00
parent c8a04af676
commit 1dffdcc6e9
3 changed files with 22 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
lang/python/doc/rst/gpgme-python-howto.rst
View File

@ -547,6 +547,14 @@ versions for CPython 2.7 and 3.4, with 64-bit versions for both x86-64
(i.e. Intel and AMD) and ARM architectures for CPython 3.5, 3.6, 3.7 and
later releases. That\'s the bare **minimum**, it\'d probably be higher.
Additionally, with only a binary installation used in conjunction with
the CPython installer from ``python.org`` the advanced options available
which utilise `Cython <#cython>`__ will not be able to be used at all.
Cython depends on being able to compile the C code it generates and that
too would need to utilise a matching runtime to both the installed
version of CPython and these bindings in order to work with the
bindings.
Considering all of that, what do we recommend?
#. Use a recent version of CPython; at least 3.5, but ideally 3.6 or

7
lang/python/doc/src/gpgme-python-howto
View File

@ -569,6 +569,13 @@ x86-64 (i.e. Intel and AMD) and ARM architectures for CPython 3.5,
3.6, 3.7 and later releases. That's the bare *minimum*, it'd probably
be higher.
Additionally, with only a binary installation used in conjunction with
the CPython installer from =python.org= the advanced options available
which utilise [[#cython][Cython]] will not be able to be used at all. Cython
depends on being able to compile the C code it generates and that too
would need to utilise a matching runtime to both the installed version
of CPython and these bindings in order to work with the bindings.
Considering all of that, what do we recommend?
1. Use a recent version of CPython; at least 3.5, but ideally 3.6 or

7
lang/python/doc/texinfo/gpgme-python-howto.texi
View File

@ -747,6 +747,13 @@ x86-64 (i.e. Intel and AMD) and ARM architectures for CPython 3.5,
3.6, 3.7 and later releases. That's the bare @strong{minimum}, it'd probably
be higher.
Additionally, with only a binary installation used in conjunction with
the CPython installer from @samp{python.org} the advanced options available
which utilise @ref{C plus Python plus SWIG plus Cython, , Cython} will not be able to be used at all. Cython
depends on being able to compile the C code it generates and that too
would need to utilise a matching runtime to both the installed version
of CPython and these bindings in order to work with the bindings.
Considering all of that, what do we recommend?
@enumerate