371 replies to this topic

[littlesat]

Using list as variable is in fact not done….

[Huevos]

Using list as variable is in fact not done….

Of course it is not done, that is why PLi is full of it. LOL.

 

One piece of code I changed in PLi recently was using "False" as a variable name. Unbelievable!

https://github.com/O...bdcaaed1543e4a7

 

The problem is those "list" are keyword arguments to functions that are used by code that you are not in control of.

 

Anyway list comprehension works around the problem

Edited by Huevos, 16 October 2021 - 11:15.

[littlesat]

There is more not done in enigma2…. Just caused by the history…

[Huevos]

@Liitlesat,

 

https://github.com/O...ssageBox.py#L17

https://github.com/O...hoiceBox.py#L16

 

Messagebox and Choicebox are 2 modules that every developer has used for the last 15 years and both have "list" as a keyword argument. If you change that now you are going to break things. So you need to work around it.

 

I am not sure why you are focusing on this now when PLi has been like this for the last 15 years. It is nothing to do with the Py3 discussion.

Edited by Huevos, 16 October 2021 - 21:26.

[Persian Prince]

Just to let you guys know recent OE upgrade brought Python 3.10.x and OpenSSL 3.0.0, after Python 3.10.x so many things are different and this is not just the end of py2 but even some py3 versions.

 

There may not be possible to have both py compatible code anymore, only time will tell and future versions of python-six

 

For now it's better not to go after Python 3.9.x for e2 teams.

[littlesat]

It was wrong from the beginnen…. And indeed when you solve it, it breaks things and that is also why it was never fixt…. More she to (3rd party) plugins… and much much work….
And indeed py >3.10 is another border…. And also extra work..:

Edited by littlesat, 17 October 2021 - 07:25.

[WanWizard]

As an old chinese proverb says: the more work you postpone, the more work you have catching up...

[Huevos]

And here we are 3 months further down the road.

[WanWizard]

Ask the guys that are in favour of anarchie...

[Huevos]

Well we have abandoned our Py2 image. Only Py3 available now.

 

No real problems from users.

 

We have helped a lot of plugin developers to upgrade.

 

Craziest thing is some plugin developers have moaned that their plugins no longer run on our image but refuse to accept tested suggested changes to get them working.

 

------------------------------------------------

 

Pli have it easy. So many examples for them to look at, at other distros when they run into problems with the conversion.

Edited by Huevos, 11 December 2021 - 07:16.

[littlesat]

Nice you did the job…. Here it is simple due to the situation I’m in I do not have the energy and time to do it proven by the commits I made in the last two years. If I could do it it it was done…. But ot also sounds a bit like saying who good you are instead of really helping….

[Huevos]

Nice you did the job…. Here it is simple due to the situation I’m in I do not have the energy and time to do it proven by the commits I made in the last two years. If I could do it it it was done…. But ot also sounds a bit like saying who good you are instead of really helping….

I think have helped PLi a lot over the years.

 

But a project like this is for the team, and as always it doesn't even seem to be able to get through the discussion stage, so no one has any idea what to do.

[Beeker]

I want to help OpenPli to port Enigma2 to python 3 and plugins which are not ported to python 3 already in January, 2022 (when I have more time).

 

Only, I need full support of OpenPli team.

Well that could be a problem.Anyway I've offered it.

 

I've already startied with enigma2-plugins(which are not ported to python3 already AFAIK).

https://github.com/H...commits/python3

 

Python 2 is dead. More and more python plugins like Cryptography, Twisted, Mutagan etc.. has dropped python 2.

So updating OE core will be more useless when time goes by.

 

Only third-party3  PY2 plugins, yes that could be a problem..

Edited by Beeker, 13 December 2021 - 02:35.

[WanWizard]

I want to help OpenPli to port Enigma2 to python 3 and plugins which are not ported to python 3 already in January, 2022 (when I have more time).

 

Only, I need full support of OpenPli team.

Well that could be a problem.Anyway I've offered it..

 

You're more than welcome, the more hands, the quicker its done .

 

What do you want or need from us in terms of "full support" ?
 

[littlesat]

At least that they can commit to our py3 develop github. Please all help is welcome here! Please also commit in a structured way so eg type change by type so it is easy to give suggestions etc.

Edited by littlesat, 13 December 2021 - 17:50.

[WanWizard]

I think that Beeker is senior enough to know how to deal with it...

[Huevos]

https://github.com/H...5cf20855d5837d2

 

And now the PLi complaint about not having .py files on the receiver should get resolved.

Edited by Huevos, 13 December 2021 - 18:07.

[WanWizard]

For Python 3 those are pyc files, not pyo files, that need to be checked for.

[Huevos]

We've been here before. Everyone else is using *.py files so having something different in plugins is going to cause problems.

[Beeker]

 

I want to help OpenPli to port Enigma2 to python 3 and plugins which are not ported to python 3 already in January, 2022 (when I have more time).

 

Only, I need full support of OpenPli team.

Well that could be a problem.Anyway I've offered it..

 

You're more than welcome, the more hands, the quicker its done .

 

What do you want or need from us in terms of "full support" ?
 

 

 

Oh I just meant that OpenPLi is interested in PY3.

 

Regarding py, pyc and pyo files.

With PY3 you need the py files anyway.

That will increase the image size.

When you don't ship the pyc files to the image, the image size should be the same as with python 2.

Not tried by myself.

Edited by Beeker, 13 December 2021 - 18:48.