tools: flash_writer.py fix Python 3.13 compatibility

[Biancaa-R]

Note: Please adhere to Contributing Guidelines.

Summary

• Fixes the issue : [FEATURE] tools/flash_writer.py depends on deprecated telnetlib. #17727
• Making flash_writer.py compatible for Python 3.13
• Changes made without stripping of backward compatibility.

Impact

• Reduced an error of missing module.

Testing

[simbit18]

Hi @Biancaa-R How can we use the telnet protocol with versions higher than Python 3.12?

https://docs.python.org/3/library/telnetlib.html

It is necessary to use the following alternatives:

https://pypi.org/project/telnetlib3/

https://pypi.org/project/Exscript/

[linguini1]

This does not fix the issue. The telnet module cannot just be removed.

[cederom]

Thank you @Biancaa-R :-)

• I am afraid this functionality is required for application operations thus cannot be just removed without alternative as @simbit18 and @linguini1 noticed. We need a working alternative please :-)
• Please take a look at https://github.com/apache/nuttx/blob/master/CONTRIBUTING.md when proposing a fix log before and after change are required in order to provide initial proof the fix is working as expected :-)

[Biancaa-R]

Thank you @Biancaa-R :-)

• I am afraid this functionality is required for application operations thus cannot be just removed without alternative as @simbit18 and @linguini1 noticed. We need a working alternative please :-)
• Please take a look at https://github.com/apache/nuttx/blob/master/CONTRIBUTING.md when proposing a fix log before and after change are required in order to provide initial proof the fix is working as expected :-)

Sure @cederom Ill fix it and get back.

[Biancaa-R]

Thank you @Biancaa-R :-)

• I am afraid this functionality is required for application operations thus cannot be just removed without alternative as @simbit18 and @linguini1 noticed. We need a working alternative please :-)
• Please take a look at https://github.com/apache/nuttx/blob/master/CONTRIBUTING.md when proposing a fix log before and after change are required in order to provide initial proof the fix is working as expected :-)

@cederom I need a small help , so the older version is fully synchronous , the newest version is predominantly asynchronous with the async library , but it can be made sync also ,so which one do I do ? asynchronous implementation is fine?

[cederom]

@Biancaa-R: @cederom I need a small help , so the older version is fully synchronous , the newest version is predominantly asynchronous with the async library , but it can be made sync also ,so which one do I do ? asynchronous implementation is fine?

The old implementation is synchronous, so we need to stick to synchronous. As you know in Python using async in one place will taint all other calls with async thus flips the whole solution upside down. So let's stick to the old design :-)

ps/2: I really liked Python some time ago until it became self-incompatible nightmare changing language syntax, standard library components and API, changing ecosystem syntax and functionalities (i.e. pip). This makes Python not much trustworthy solution when you think in long term maintenance terms. There could be completely alternative solution here just to avoid Python and rewrite this tool in C that will not change in time. Maybe tool like this already exist? Or maybe Python developers provided a quick-fix information when introducing this breaking change of telnet module removal what alternatives / solutions do they offer instead?

[fdcavalcanti]

@Biancaa-R: @cederom I need a small help , so the older version is fully synchronous , the newest version is predominantly asynchronous with the async library , but it can be made sync also ,so which one do I do ? asynchronous implementation is fine?

The old implementation is synchronous, so we need to stick to synchronous. As you know in Python using async in one place will taint all other calls with async thus flips the whole solution upside down. So let's stick to the old design :-)

ps/2: I really liked Python some time ago until it became self-incompatible nightmare changing language syntax, standard library components and API, changing ecosystem syntax and functionalities (i.e. pip). This makes Python not much trustworthy solution when you think in long term maintenance terms. There could be completely alternative solution here just to avoid Python and rewrite this tool in C that will not change in time. Maybe tool like this already exist? Or maybe Python developers provided a quick-fix information when introducing this breaking change of telnet module removal what alternatives / solutions do they offer instead?

The deprecation was announced some time ago (2019!). The current telnetlib page gives us alternatives:
https://docs.python.org/3.13/library/telnetlib.html