30 Říj
2018
30 Říj
'18
19:22
[reordering attributed text for chronological sanity]
On Tue 2018-10-30 13:04:10 +0100, Daniel Salzman wrote:
On 10/30/18 12:37 PM, Rick van Rein wrote:
Perhaps we should be shipping this in the knot packages in debian? the
first bullet point in debian/TODO is "package python3-libknot".
Is there a reason that we shouldn't be producing python bindings from
the same source package for debian? Then each new release would
automatically push an updated libknot python package into debian.
Is there any reason to prefer python2 here? I'm assuming that we want
to prefer python3 for any new packages, given that py2 is eol relatively
soon.
--dkg
You/Daniel pointed me to the Python control
library, but I cannot find
it in the 2.7.3 packages -- is that forgotten, or am I missing it?
The control library interface in Python is not a part of regular libknot packages.
It can be found in Python's pip repository (libknot). Unfortunately, it's not
up-to-date :-(
For now you have to download it from the repository
https://gitlab.labs.nic.cz/knot/knot-dns/tree/2.7/python/libknot
or to get from corresponding source package
https://secure.nic.cz/files/knot-dns/knot-2.7.3.tar.xz