15 Feb
2021
15 Feb
'21
7:45 a.m.
Hi,
I am sure you know the answer to my question.
I decided to get ready for bullseye and I see that bullseye is moving to
python3. However tdebindings is still on python2.7.
What is the recommended TDE approach on that?
thank you
15 Feb
15 Feb
9:45 a.m.
Anno domini 2021 Mon, 15 Feb 08:45:21 +0100
deloptes scripsit:
Hi,
I am sure you know the answer to my question.
I decided to get ready for bullseye and I see that bullseye is moving to
python3. However tdebindings is still on python2.7.
What is the recommended TDE approach on that?
This hits devuan chimaera, too, so I'm also interested in advice. But it looks like
python2.7 will be around for at least for chimaera/bullseye.
Nik
--
Please do not email me anything that you are not comfortable also sharing with the NSA,
CIA ...
6:46 p.m.
Dr. Nikolaus Klepp wrote:
This hits devuan chimaera, too, so I'm also
interested in advice. But it
looks like python2.7 will be around for at least for chimaera/bullseye.
I am absolutely not happy when I see that the debian build scripts (or
whatever) are trying to create symlink in /usr/bin for python.
I think it is very odd. The scripts should use python2.7 or create alias
when running or whatever.
Looking at differences in python 2+ and 3 seems the difference is in python3
using UTF-8 and python2.7 is still maintained but not recommended.
I personally do not find any use for python here, but whole tdebindings
fails.
What can we/I do to help? I honestly had some other plans ... but ...
upgrading to bullseye is not high priority for now :)
regards
16 Feb
16 Feb
2:17 a.m.
On 2021/02/16 03:46 AM, deloptes wrote:
Dr. Nikolaus Klepp wrote:
Hi Emanoil, Nik,
the topic of python 2 has come up already in internal discussions. Here is the current
status:
1) we will need to migrate to python3 as some point. Some work has already been done, but
a lot is still required. May
happen for R14.1.0 or in one of the subsequent R14.1.x releases.
2) python bindings (python-trinity and pytdeextensions) works on python 2 but need to be
updated for python 3
3) tdebindings is mostly broken AFAICT. I personally would like to see it fixed, but we
have postponed any work on it
till after R14.1.0 is released.
4) you can perfectly run TDE on bullseye, no problem there.
If you want to help you are welcome, obviusly :-)
Cheers
Michele
This hits devuan chimaera, too, so I'm also
interested in advice. But it
looks like python2.7 will be around for at least for chimaera/bullseye.
I am absolutely not happy when I see that the debian build scripts (or
whatever) are trying to create symlink in /usr/bin for python.
I think it is very odd. The scripts should use python2.7 or create alias
when running or whatever.
Looking at differences in python 2+ and 3 seems the difference is in python3
using UTF-8 and python2.7 is still maintained but not recommended.
I personally do not find any use for python here, but whole tdebindings
fails.
What can we/I do to help? I honestly had some other plans ... but ...
upgrading to bullseye is not high priority for now :)
regards
9:15 a.m.
Michele Calgaro via tde-devels wrote:
Hi Emanoil, Nik,
the topic of python 2 has come up already in internal discussions. Here is
the current status:
1) we will need to migrate to python3 as some point. Some work has already
been done, but a lot is still required. May happen for R14.1.0 or in one
of the subsequent R14.1.x releases.
2) python bindings (python-trinity and pytdeextensions) works on python 2
but need to be updated for python 3
3) tdebindings is mostly broken AFAICT. I personally would like to see it
fixed, but we have postponed any work on it till after R14.1.0 is
released.
4) you can perfectly run TDE on bullseye, no problem there.
If you want to help you are welcome, obviusly :-)
Thank you for the update Michele,
for the python as mentioned to me it is disturbing that it tries to symlink
under /usr/bin, might be I try to fix this one only.
What about other packages like kpilot and qt4-theme? Are they going to be
dropped?
regards
9:45 a.m.
On Tuesday 16 of February 2021 10:15:45 deloptes wrote:
Michele Calgaro via tde-devels wrote:
This symlink was created there during the build, because the standard CDBS
rules "python-distutils" expect the "python" binary available. And
because
it's easier to create a symlink than modify standard CDBS rules, we used
this little hack.
Cheers
--
Slávek
Hi Emanoil, Nik,
the topic of python 2 has come up already in internal discussions.
Here is the current status:
1) we will need to migrate to python3 as some point. Some work has
already been done, but a lot is still required. May happen for R14.1.0
or in one of the subsequent R14.1.x releases.
2) python bindings (python-trinity and pytdeextensions) works on
python 2 but need to be updated for python 3
3) tdebindings is mostly broken AFAICT. I personally would like to see
it fixed, but we have postponed any work on it till after R14.1.0 is
released.
4) you can perfectly run TDE on bullseye, no problem there.
If you want to help you are welcome, obviusly :-)
Thank you for the update Michele,
for the python as mentioned to me it is disturbing that it tries to
symlink under /usr/bin, might be I try to fix this one only.
What about other packages like kpilot and qt4-theme? Are they going to
be dropped?
regards
____________________________________________________
9:54 a.m.
On Tuesday 16 of February 2021 10:15:45 deloptes wrote:
What about other packages like kpilot and qt4-theme?
Are they going to
be dropped?
This is not a significant problem for KPilot. You can see that we have
added pilot-link to our extra-dependencies and we are building it without
python support because there is no need for python support for KPilot.
Qt4-tqt-theme will no longer be built for distributions that no longer
include support for Qt4 => will not contain qt4 applications and therefore
qt4-tqt-theme will not be needed.
Cheers
--
Slávek
6:40 p.m.
Slávek Banko via tde-devels wrote:
This symlink was created there during the build,
because the standard CDBS
rules "python-distutils" expect the "python" binary available. And
because
it's easier to create a symlink than modify standard CDBS rules, we used
this little hack.
Thank you, but is it not possible to do this somewhere in the build
directory?
1169
days inactive
1170
days old
7 comments
4 participants
participants (4)
-
deloptes -
Dr. Nikolaus Klepp -
Michele Calgaro -
Slávek Banko