termio | buffering terminal UI library | Command Line Interface library

Instead of this:

#include

This:

#include

I have read a lot about hidden import and I tried the code

Replace printf("some text"); with write(1,"some text", 9); and you'll get the expected cursor position.

You make a wrong assertion about cursor position moved with clib printf, POSIX/ANSI C doesn't specify that this one should move the cursor.

interact() is for manual interaction with the spawned process and it requires to be running on a tty but nohup provides no tty. You can just replace child.interact() with child.expect(pexpect.EOF, timeout=None).

On my terminal disabling ECHO and disable canonical mode, but setting terminal to RAW is probably just better. Following code misses a lot of error handling:

pyinstaller Options: I can't find any information about the option -x, maybe this is the issue.

Also: pyinstaller -d option

It seems that the -d option requires arguments. Maybe try to remove the option or put one of the required values:

-d , --debug

Provide assistance with debugging a frozen application. This argument may be provided multiple times to select several of the following options.

all: All three of the following options.

imports: specify the -v option to the underlying Python interpreter, causing it to print a message each time a module is initialized, showing the place (filename or built-in module) from which it is loaded. See https://docs.python.org/3/using/cmdline.html#id4.

bootloader: tell the bootloader to issue progress messages while initializing and starting the bundled app. Used to diagnose problems with missing imports.

noarchive: instead of storing all frozen Python source files as an archive inside the resulting executable, store them as files in the resulting output directory.

The pts was created when a virtual terminal was attached to the system (usually ssh). The pts was connected as stdin/stdout for a shell which was started for the connection, therefore you already have a process attached to the pts and reading from it.

Once you attach your application, you effectively start a race between both processes (your application and the shell), so whoever is faster will receive the content of the buffer. The character had not remained in the buffer of the pts, rather it was read by the shell attached to the pts.

To be able to read without interruption from the attached process, you need to intercept the buffer of the pts by informing the master multiplexer ptmx, see more in ptmx(4). You can study how it's done in the interceptty

This happens because your computer registers the key strokes and on the console, those are made available on the stdin input stream.

If you save your script as test.py and run python test.py and start entering some keystrokes, like abc, those letters will be on standard input.

Your script doesn't read them, because it doesn't touch that stream, as you're not using input() or any other calls that would read that stream. So your script finishes, the characters are still on standard input, the prompt comes back and it reads those characters, with the given result:

In order to receive broadcast packets, you need to set the SO_BROADCAST socket option.