pexpect | Python module for controlling interactive programs | Command Line Interface library

This looks to be an active issue relating to poetry. See here - Issue #4085. Some suggest a workaround by downgrading poetry-core down to 1.0.4.

There is an active PR to fix the issue.

The error error: [Errno 2] No such file or directory: '/opt/anaconda3/lib/python3.8/site-packages/rtree/lib' was caused by py2app trying to build the program bundle using a non-existent interpreter. This means that even if you try to uninstall a manager like Anaconda, it still has option logs somewhere on your mac.

The fix:

1. Open the terminal and type the command type -a python.

• You will see similar lines

Detect the password prompt: The password prompt appears mainly after makepkg enters in fakeroot. IDK how to detect that and supply the password from the script. There is no pattern actually. Some package evoke 1 y/n prompt while some prompt more than 1.

There is a pattern. An y/n prompt is shown when:

• makepkg invokes pacman to install build dependencies (for the -s option);
• makepkg invokes pacman to install the freshly built package (for the -i option);
• makepkg invokes pacman to remove the build dependencies (for the -r option).
• makepkg invokes pacman to...

In all cases, if makepkg is given the --noconfirm option, it will pass that to pacman as well.

Enter actual password: Actually, I want to enter password through a GUI. So, basically, I want user to input password in a text box that I will create using Tkinter.

The password prompt, if any, is shown by sudo. Sudo supports running external "askpass" tools through the SUDO_ASKPASS environment variable.

Write or install a program that shows the password prompt and outputs the password to stdout (e.g. ssh-askpass or zenity would do), then set the SUDO_ASKPASS environment variable to the program's path:

applaunchservices appears to be Apple-only:

Simple package for registering an app with apple Launch Services to handle UTI and URL. See Apple documentations for details.

I suspect you don't need that, either. Did you create your requirements.txt from a pip freeze? There's likely a bunch of stuff in there you don't need.

I suggest you review that file and remove anything you aren't directly depending on. pip will find transitive dependencies (dependencies your dependencies depend on) and install them automatically.

Prune that file, commit, and redeploy.

Did you try pexpect.run("[COMMAND]", events={"[y/n]: " : "y\n"}) ? According to the documentation and depending on your program the newline may be necessary.

Or, to be more generic and save, use

When I check the dump, session matches b'First_line:\r\n', but p.stdin.write doesn't move the pexpect cursor forward to look for "Second_line:", as what happens with send() or sendline().

May I suggest a simpler way, using PopenSpawn? The docs state that it "provides an interface like pexpect.spawn interface (sic) using subprocess.Popen":

NOTE - Tested in Windows 11, using Python 3.9.

After trying for a few days and just found out that pip and python in the project are not pointing to .venv but to anaconda due to an update. when error

no module stdnum

actually there is a problem with pip so make sure your pip path with which pip or which python

1. to solve .venv that doesn't work by deleting the .venv folder, create venv in python, and install all requirements again

By using this way you can see your output

I fixed it by writing matplotlib and pandas on top of the RUN command. Here is the fixed dockerfile: