python-daemon | The official Python daemon of Cryptic | SMS library

I am on MacOS 10.15.7 Python version 3.8.2

I'm guessing you used the Python 3 bundled/pre-installed with macOS Catalina.

The documentation gives what you want : pip download

pip download does the same resolution and downloading as pip install, but instead of installing the dependencies, it collects the downloaded distributions into the directory provided

source

So you may try these option with pip download :

I was able to figure out a work around that utilizes Threading instead of a daemon. See below for the code.

Launch Daemons (and cron jobs and ...) don't run under your usual Terminal/shell environment, so they don't get whatever customization, add-ons, etc are set up in your Terminal/shell environment. In particular, they don't run the various shell initialization scripts (~/.bash_profile, ~/.bashrc, etc) that normally have the commands to set up your environment.

In the specific case of anaconda, its installer adds a section to your ~/.bashrc file to add the anaconda binaries directory to PATH, and probably a bunch of other changes. This affects your environment your bash sessions in Terminal, but doesn't take effect for Launch Agents, or even Terminal sessions in other shells (zsh is now the default, and it's causing some trouble with this).

For a Launch Daemon, I'd recommend against making it run your shell setup scripts -- those are your personal config, and don't have any real business being run by a system process. Instead, I'd create a short shell script that includes the relevant setup (copied from your ~/.bashrc), and then runs your python script. Then change the Launch Daemon so it runs that script, rather than running the python script directly.

P.S. Since the script doesn't have to do anything after starting the python script, this is a case where the script could use the exec command to exit itself, and run the python script instead in the same process. That means that python would be a direct subprocess of launchd, and launchd can monitor, control, etc it in the way that it likes to. (That's as opposed to having the script run python normally, in which case you'd have a now-pointless shell process hanging out waiting for the python script to finish so that it can finish.)

So I'd end the script with:

Your issue is typically related to Xcode toolkit.

Type this command in your terminal

The error "Failed to install PyPI packages" means Cloud Build was unable to build Docker images for your Cloud Composer environment. This is usually because there was a PyPI package installation failure, or there were incompatible dependencies. In your case, it is the latter:

Have you tried Thread.Sleep (Timeout.Infinite) ?

If you don't want to create zombie processes you should wait for them to finish i.e. execute wait system call instead of sleep:

So with the details as provide in the question, we have the scenario where a Python script and the environment it will be executed at has:

1. Dependency on some packages;
2. No virtualenv is used, but the Python user install directory (as the ec2-user user) is used instead for simplicity for the installation of the script's dependencies;
3. The script however requires root privileges to run (due to the usage of low ports, with the elevated permission achieved via sudo (as the root user).

Naturally, running a script as root while the dependencies were installed local to a user other than root will mean that none of the dependencies will actually be accessible by that script. As the dependencies are installed under the site.USER_BASE for the ec2-user, in order for the script to be able to import its dependency while being executed under the root user, the location may be defined using the PYTHONUSERBASE environment variable.

To achieve that while using sudo, try: