30 Oct
2018
30 Oct
'18
12:37 p.m.
Hi,
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?
Thanks,
-Rick
30 Oct
30 Oct
1:04 p.m.
Hi Rick,
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
I'm sorry.
Best,
Daniel
On 10/30/18 12:37 PM, Rick van Rein wrote:
Hi,
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?
Thanks,
-Rick
7:22 p.m.
[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
31 Oct
31 Oct
9:23 a.m.
Hi Daniel,
On 2018-10-30 19:22, Daniel Kahn Gillmor wrote:
[reordering attributed text for chronological sanity]
On Tue 2018-10-30 13:04:10 +0100, Daniel Salzman wrote:
Yes, if it became a python3-libknot package, it would definitely be
welcome!
Anyway I will try to update the pip package...
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".
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 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.
No, I don't know any reason for that. Your suggestion sound good.
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.
Of course, python2 is dead ;-) Please consider python3 only.
Thank you,
Daniel
--dkg
2176
days inactive
2177
days old
3 comments
4 participants
participants (4)
-
Daniel Kahn Gillmor -
Daniel Salzman -
daniel.salzman＠nic.cz
-
Rick van Rein