| 19 Jan 2022 |
 K900 | It comes from your Python/pip | 14:19:21 |
| K900 | Easiest way is probably to use a newer Python than 3.7 | 14:19:30 |
|  jake :: Stateless -> Farm joined the room. | 14:44:17 |
 mou | Redacted or Malformed Event | 16:23:13 |
 tcelferact | Unfortunately that's not easier as the build is for a django monolith and upgrading would be a huge time investment. This must be specific to nix in some way as our docker image still builds fine on M1? | 16:28:10 |
| tcelferact | I tried upgrading to the 21.11 channel, but I now run into the following for uwsgi:
pip._internal.exceptions.InstallationError: Directory '.' is not installable. Neither 'setup.py' nor 'pyproject.toml' found.
The dir that's supposedly missing the file (it's a tmp dir and I can't check) is /private/tmp/nix-build-python3.7-uwsgi-2.0.18.drv-0.
| 16:30:15 |
| tcelferact | this is probably just a distraction, apologies | 16:52:10 |
| tcelferact | if setuptools is the problem, is there some way to patch the version used by nix's python 3.7 build? | 16:52:36 |
| K900 | You can probably add a newer version to buildInputs | 17:14:40 |
|  zupo joined the room. | 21:14:15 |
| zupo | gheesh hunting this bug down almost killed me: https://github.com/nix-community/poetry2nix/issues/523 | 21:14:31 |
| zupo | but I stand victorious! ⚔️ 🐛 | 21:15:19 |
 adisbladis | In reply to @zupo:matrix.org
gheesh hunting this bug down almost killed me: https://github.com/nix-community/poetry2nix/issues/523 I don't think this is a bug in poetry2nix, but an unfortunate side effect of how nixpkgs python infra propagates it's dependencies.
What does which python say?
| 22:18:21 |
| zupo | [nix-shell:~/work/big-sur-poetry-test]$ which python
/nix/store/avn3nqyfphpaakj2xijazsfry0g93f10-python3-3.9.6/bin/python | 23:24:59 |
| zupo | Redacted or Malformed Event | 23:26:44 |
| zupo | adisbladis: Ah I see, yes, makes sense that it's leaky docker-compose in nixpkgs. Should I move the bug report there? | 23:29:52 |
| adisbladis | In reply to @zupo:matrix.org
adisbladis: Ah I see, yes, makes sense that it's leaky docker-compose in nixpkgs. Should I move the bug report there? I think so.
A quick fixup on your end could be to override docker-compose something along these lines:
docker-compose.overridePythonAttrs(old: {
postFixup = ''
rm $out/nix-support/propagated-build-inputs
'';
})
| 23:38:26 |
| adisbladis | This is a pretty pervasive problem in nixpkgs | 23:39:27 |
| adisbladis | And I think that the correct solution would be to change buildPythonApplication to not propagate python deps | 23:39:57 |
| adisbladis | zupo: I do the same thing for the Poetry derivation: https://github.com/nix-community/poetry2nix/blob/master/pkgs/poetry/default.nix#L41-L45 | 23:40:54 |
| 20 Jan 2022 |
| zupo | 👍👍 thanks | 07:24:29 |
|  cchalc joined the room. | 08:41:34 |
|  sephi joined the room. | 09:35:41 |
|  Martin Ertsås joined the room. | 14:36:36 |
| Martin Ertsås | Hi. I'm struggling in making a development shell for my project. It fails when trying to fetch pytest. I have made a minimal example: https://github.com/martiert/poetry2nix-pytest-error
Not sure if this is a bug, or I'm doing something wrong? My ideal result of this is me being able to run python -m pytest in the shell and have it run my tests
| 14:42:00 |
| mou | Just tried to build your flake and got this error
last 10 log lines:
> Sourcing pip-install-hook
> Using pipInstallPhase
> Sourcing python-imports-check-hook.sh
> Using pythonImportsCheckPhase
> Sourcing python-namespaces-hook
> unpacking sources
> Executing wheelUnpackPhase
> Finished executing wheelUnpackPhase
> patching sources
> sed: can't read setup.cfg: No such file or directory
Just to save some time for whom who will look into issue
| 14:45:59 |
| mou | * Just tried to build your flake and got this error
last 10 log lines:
> Sourcing pip-install-hook
> Using pipInstallPhase
> Sourcing python-imports-check-hook.sh
> Using pythonImportsCheckPhase
> Sourcing python-namespaces-hook
> unpacking sources
> Executing wheelUnpackPhase
> Finished executing wheelUnpackPhase
> patching sources
> sed: can't read setup.cfg: No such file or directory
Just to save some time for whom who will look into the issue
| 14:46:59 |
| Martin Ertsås | aaah, yeah. I forgot to add that. Thank you. | 14:47:25 |
| Martin Ertsås | and that's when trying to build the pytest wheel. | 14:47:44 |
| mou | My bet: issue lies inside nixpkgs buildPythonPackage, but it's only guess | 14:53:18 |
