kliment/Printrun

Pip will not install dependencies

Closed this issue · 3 comments

Printrun/README.md

Lines 169 to 175 in d4080ef

#### 4. Install Printrun
Once activated your virtual environment, install Printrun' source code with:
```
(venv) $ python -m pip install .
```

According to the readme instructions the command python -m pip install . would install Printrun and its dependencies. However the dependencies are not being installed.

See fresh run using Python 3.12.7 and pip 24.2. Only Printrun gets installed now:

$ python3 -m venv venv
$ source venv/bin/activate
$ python -m pip install --dry-run .
Processing /home/rock/Projects/printrun/rockintrun
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Would install Printrun-2.1.0

I would have sworn that the above command used to install everything. I've got the fix already prepared but I wondered if someone else stumbled across this before.

Same thing if I install from PyPI:

$ python3 -m venv venv
$ source venv/bin/activate
$ python -m pip install --dry-run --no-cache-dir Printrun
Collecting Printrun
  Downloading Printrun-2.1.0-cp312-cp312-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (25 kB)
Downloading Printrun-2.1.0-cp312-cp312-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl (602 kB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 602.3/602.3 kB 13.8 MB/s eta 0:00:00
Would install Printrun-2.1.0

My last "experiment" with Debian on a VM ends in a disaster. I thought I'm not compatible with Debian and deleted the VM for not getting more frustrated.

My last "experiment" with Debian on a VM ends in a disaster. I thought I'm not compatible with Debian and deleted the VM for not getting more frustrated.

Hahaha, no worries. Sad to hear the experience wasn't good but I'm not surprised either :P