lyx2lyx/* small woes

[José Matos]

On Sat, 2023-08-19 at 12:40 -0400, Scott Kostyshak wrote:
> On Sat, Aug 19, 2023 at 05:05:36PM +0100, José Matos wrote:
> 
> The changes look simple so I would say go ahead for master branch.
> There is still no freeze for it anyway.
> 
> Scott

Could you do it, please?

The ssh server from our server is old and I am unable to connect even
by enabling legacy mode. I tried this several times in the last two
years with the help of Riki and I have never succeeded.

More and more other services have been increasing the requirements for
security and so the LyX server is the only where I have problems. :-(


On a related note to this issue:

1) There is another batch of easy fixes that deal with the removal of
variables that are defined but never used. There are several examples
like this on the lyx2lyx directory.


2) FWIW at some point, after the release of 2.4, I would like to
modernize the python code in order to remove the compatibility with
python 2.

That compatibility is not only moot as it is a nuisance. One of the
easiest examples is the need that we have now to prefix all text
strings with u (for unicode).

The same applies to use typing to annotate functions and take advantage
of static analysers to ensure the correctness of code.

The questions is to decide what is the best timing for this operation.
Could it be after 2.4.1 release?

Best regards,
-- 
José Abílio