James Brock

Oh yeah I see you've been contributing to https://github.com/thomashoneyman/purescript-overlay @toastal

Anyway **purifix** is PureScript build system that works without invoking `spago` at all. Useful if it's important to avoid import-from-derivation.

Just to be clear, are you talking about **easy-purescript-nix**, or **purifix**?

I messaged you on Discourse @toastal

That's a really good question! Because the same guy, @cdepillabout , did both [purenix](https://github.com/purenix-org/purenix) and purifix. I would like to know the answer to that question. Why didn't you use...

I'm also troubled by this issue. I have ``` [tool.poetry.dependencies] pytelicam = [ { platform = "linux", path = "pytelicam-1.1.1-cp310-cp310-linux_x86_64.whl" }, { platform = "win32", path = "pytelicam-1.1.1-cp310-cp310-win_amd64.whl" }, ]...

[Poetry 2.0](https://python-poetry.org/history/#200---2025-01-05) writes the [`markers`](https://packaging.python.org/en/latest/specifications/dependency-specifiers/#environment-markers) to the `poetry.lock` and I wonder if that might help. Because it looks like *poetry2nix* can read environment markers https://github.com/nix-community/poetry2nix/blob/98293f0b368f24c48e05aaa2359dcc0de15e976f/vendor/pyproject.nix/lib/pep508.nix

I suspect that there is a bug here and this line https://github.com/nix-community/poetry2nix/blob/ac847558db725d865d44bbd77f894076c4b03ee3/default.nix#L186 should be instead ```python marker = pyproject-nix.lib.pep508.parseMarkers pkgMeta.markers; ```

Workaround in one command: ```console poetry config virtualenvs.use-poetry-python true ```

I'm puzzled about why the checks are failing and I'd like advice please.