install_script | YunoHost installation scripts

According to the documentation in Module::AutoInstall :

Starting from version 0.43, Module::AutoInstall supports modules that require a MY::postamble subroutine in their Makefile.PL. The user-defined MY::postamble, if present, is responsible for calling Module::AutoInstall::postamble and include the output in its return value.

I tested this with this simple Makefile.PL:

Step 1: Download this stable release of uWSGI

Step 2: Extract the tar file inside the site-packages folder of the virtual environment.

For example the extracted path to uwsgi should be:

Try env ARCHFLAGS="-arch x86_64"

(that works for me for other Python-related tools, I don't use pyenv myself).

Rationale: modern macOS supports 2 architectures: intel (x86_64) and m1 (arm-something). Compiling for only one architecture is easier.

You are installing the wrong package. Change dotenv to python-dotenv in your requirements.txt file. See this issue for more information. https://github.com/theskumar/python-dotenv/issues/113

I answer my question myself.

To find the cause of the problem, I created and tested a new virtualenv within the beanstalk instance.

At first, pip install --upgrade setuptools, pip install --upgrade pip works properly. But after upgrading pip to the latest (2020.3.2), pip install --upgrade setuptools make the same problem. And When I downgraded pip to 2020.3.1 using pip install --upgrade pip==2020.3.1, it solved the problem!

So the root cause is pip2020.3.2. It seems that pip 2020.3.2 is yanked release yet (https://pypi.org/project/pip/20.3.2/). I'm not sure why the yanked release is installed.

I tested it in Linux/2.9.16(python 3.6), MacOS11.0.1(python 3.6, 3.9) and got the same results.

Anyway, hope this helps others who are having similar problems.

Below is the troubleshooting process.

The problem solved very easily. Just needed to install python from python.org and not brew.

This django-observer package hasn't been maintained for a long time. The github repository states it works on Python 3 version 3.2 and 3.3 though. So you might have luck setting up a virtualenv with python 3.2 or 3.3 and working from there.

The package appears to have done work similar to that of Django Signals. You can read up on them here. Signals are an implementation of the Observer pattern.

Just FYI, I tried installing the package too and got the same error on my MacOS machine. This is why I suggest switching to Signals.

Change to command to:

this might be the answer to your problem. posting it as an answer allows me to use the space and formatting i need.

The basic problem is that you are not including the stacksearch folder in your dist file.

One way I discovered this was downloading your tar ball from pypi.test . you can see what's in the folder and it only has the scripts. another way is looking at the results of your pip install -e . command. you can see it here: