Skip to content

Tracking issue: PyPI dependencies pixi can't manage yet. #771

Open

Description

@ruben-arts

There are a few PyPI packages pixi can't install yet, where pip can.

Please paste your examples in this issue so we have a list of known packages we can track, test and benchmark with along the way.

Information we would like:

  1. What did you run and what was the outcome?
    e.g. pixi add --pypi packagex
    If it doesn't recreate in an empty environment please share your pixi.toml that recreates the issue.

  2. What error did pixi return?
    e.g.

    × RECORD file doesn't match wheel contents: missing hash for mediapipe/version.txt (expected sha256=-fE2KU)
    
  3. Can pip install the package?
    Does pip install packagex work?

  4. What platform are you on?
    e.g. linux-64

  5. Did you find a workaround, if so please explain.
    e.g. build it into a conda package, using a custom fork, etc.

Your input would greatly help us improve the pixi's experience!
Thanks in advance! ❤️

Activity

  1. pablovela5620 commented on Feb 2, 2024

    @pablovela5620
    Contributor

    Mediapipe

    1. pixi add --pypi mediapipe
    2. × RECORD file doesn't match wheel contents: missing hash for mediapipe/version.txt (expected sha256=-fE2KU)
    3. python -m pip install mediapipe does work
    4. platform osx-arm64
    5. work around was just to use pip to install using pixi tasks
    [project]
    name = "ipdscan"
    version = "0.1.0"
    description = "Add a short description here"
    authors = ["pablovela5620 <[email protected]>"]
    channels = ["conda-forge"]
    platforms = ["osx-arm64"]
    
    [tasks]
    mp-install = "python -m pip install mediapipe"
    
    [dependencies]
    python = "3.11.*"
    pip = ">=23.3.2,<23.4"
    rerun-sdk = ">=0.12.0,<0.13"
    requests = ">=2.31.0,<2.32"
    tqdm = ">=4.66.1,<4.67"
    
    [pypi-dependencies]
    imutils = "*"
    
  2. tylerjw commented on Feb 4, 2024

    @tylerjw

    I wanted to use this library that is packaged in pypi: https://github.com/spirali/elsie

    Here is the error I was seeing when trying to use pixi add:

     WARN rattler_installs_packages::index::package_database: errors while processing source distributions:
      × failed to resolve `pypi-dependencies`, due to underlying error
      ╰─▶ No metadata could be extracted for the following available artifacts:
          	- lxml-4.6.5.tar.gz
    
    Error:   × error while processing source distribution 'lxml-4.6.5.tar.gz':
      │  could not build wheel: <string>:67: DeprecationWarning: pkg_resources is deprecated as an API. See https://
      │ setuptools.pypa.io/en/latest/pkg_resources.html
      │ 
      help: Probably an error during processing of source distributions. Please check the error message above.
    

    Posting in the discord channel got it working with this fix:

    pixi add python lxml
    pixi add --pypi elsie
    

    The reason for this is:

    there seems to be an issue with one of the lxml source distributions. Meaning you have to locally build the package but that is not working because of the error it is giving you. pixi reports back on errorous packages where pip probably continues trying other versions.

  3. liquidcarbon commented on Feb 12, 2024

    @liquidcarbon
    Contributor

    pixi add duckdb ❌ pixi add --pypi duckdb ❌ vs pixi run pip install duckdb ✅ on Windows

    PS C:\code> pixi init duckdb-pip
    ✔ Initialized project in C:\code\duckdb-pip
    PS C:\code> cd .\duckdb-pip\
    PS C:\code\duckdb-pip> pixi add python=3.11
    ✔ Added python=3.11
    PS C:\code\duckdb-pip> pixi add duckdb     
      × could not determine any available versions for duckdb on win-64. Either the package could not be found or version constraints on other
      │ dependencies result in a conflict.
      ╰─▶ Cannot solve the request because of: No candidates were found for duckdb *.
    
    
    PS C:\code\duckdb-pip> pixi add --pypi duckdb
      × could not build wheel: warning: no files found matching '*.h' under directory 'duckdb'
      │ warning: no files found matching '*.hpp' under directory 'duckdb'
      │ warning: no files found matching '*.cpp' under directory 'duckdb'
      │ warning: no files found matching '*.h' under directory 'src'
      │ warning: manifest_maker: MANIFEST.in, line 6: 'recursive-include' expects <dir> <pattern1> <pattern2> ...
      │
      │ C:\Users\AKISLU~1\AppData\Local\Temp\.tmpkvrxrc\venv\Lib\site-packages\setuptools\command\build_py.py:207: _Warning: Package 'duckdb-      
      │ stubs.value' is absent from the `packages` configuration.
      │ !!
      │
      │         ********************************************************************************
      │         ############################
      │         # Package would be ignored #
      │         ############################
      │         Python recognizes 'duckdb-stubs.value' as an importable package[^1],
      │         but it is absent from setuptools' `packages` configuration.
      │
      │         This leads to an ambiguous overall configuration. If you want to distribute this
      │         package, please make sure that 'duckdb-stubs.value' is explicitly added
      │         to the `packages` configuration field.
      │
      │         Alternatively, you can also rely on setuptools' discovery methods
      │         (for example by using `find_namespace_packages(...)`/`find_namespace:`
      │         instead of `find_packages(...)`/`find:`).
      │
      │         You can read more about "package discovery" on setuptools documentation page:
      │
      │         - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
      │
      │         If you don't want 'duckdb-stubs.value' to be distributed and are
      │         already explicitly excluding 'duckdb-stubs.value' via
      │         `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
      │         you can try to use `exclude_package_data`, or `include-package-data=False` in
      │         combination with a more fine grained `package-data` configuration.
      │
      │         You can read more about "package data files" on setuptools documentation page:
      │
      │         - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
      │
      │
      │         [^1]: For Python, any directory (with suitable naming) can be imported,
      │               even if it does not contain any `.py` files.
      │               On the other hand, currently there is no concept of package data
      │               directory, all directories are treated like packages.
      │         ********************************************************************************
      │
      │ !!
      │   check.warn(importable)
      │ C:\Users\AKISLU~1\AppData\Local\Temp\.tmpkvrxrc\venv\Lib\site-packages\setuptools\command\build_py.py:207: _Warning: Package 'duckdb-      
      │ stubs.value.constant' is absent from the `packages` configuration.
      │ !!
      │
      │         ********************************************************************************
      │         ############################
      │         # Package would be ignored #
      │         ############################
      │         Python recognizes 'duckdb-stubs.value.constant' as an importable package[^1],
      │         but it is absent from setuptools' `packages` configuration.
      │
      │         This leads to an ambiguous overall configuration. If you want to distribute this
      │         package, please make sure that 'duckdb-stubs.value.constant' is explicitly added
      │         to the `packages` configuration field.
      │
      │         Alternatively, you can also rely on setuptools' discovery methods
      │         (for example by using `find_namespace_packages(...)`/`find_namespace:`
      │         instead of `find_packages(...)`/`find:`).
      │
      │         You can read more about "package discovery" on setuptools documentation page:
      │
      │         - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
      │
      │         If you don't want 'duckdb-stubs.value.constant' to be distributed and are
      │         already explicitly excluding 'duckdb-stubs.value.constant' via
      │         `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
      │         you can try to use `exclude_package_data`, or `include-package-data=False` in
      │         combination with a more fine grained `package-data` configuration.
      │
      │         You can read more about "package data files" on setuptools documentation page:
      │
      │         - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
      │
      │
      │         [^1]: For Python, any directory (with suitable naming) can be imported,
      │               even if it does not contain any `.py` files.
      │               On the other hand, currently there is no concept of package data
      │               directory, all directories are treated like packages.
      │         ********************************************************************************
      │
      │ !!
      │   check.warn(importable)
      │ C:\Users\AKISLU~1\AppData\Local\Temp\.tmpkvrxrc\venv\Lib\site-packages\setuptools\command\build_py.py:207: _Warning: Package
      │ 'duckdb.experimental' is absent from the `packages` configuration.
      │ !!
      │
      │         ********************************************************************************
      │         ############################
      │         # Package would be ignored #
      │         ############################
      │         Python recognizes 'duckdb.experimental' as an importable package[^1],
      │         but it is absent from setuptools' `packages` configuration.
      │
      │         This leads to an ambiguous overall configuration. If you want to distribute this
      │         package, please make sure that 'duckdb.experimental' is explicitly added
      │         to the `packages` configuration field.
      │
      │         Alternatively, you can also rely on setuptools' discovery methods
      │         (for example by using `find_namespace_packages(...)`/`find_namespace:`
      │         instead of `find_packages(...)`/`find:`).
      │
      │         You can read more about "package discovery" on setuptools documentation page:
      │
      │         - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
      │
      │         If you don't want 'duckdb.experimental' to be distributed and are
      │         already explicitly excluding 'duckdb.experimental' via
      │         `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
      │         you can try to use `exclude_package_data`, or `include-package-data=False` in
      │         combination with a more fine grained `package-data` configuration.
      │
      │         You can read more about "package data files" on setuptools documentation page:
      │
      │         - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
      │
      │
      │         [^1]: For Python, any directory (with suitable naming) can be imported,
      │               even if it does not contain any `.py` files.
      │               On the other hand, currently there is no concept of package data
      │               directory, all directories are treated like packages.
      │         ********************************************************************************
      │
      │ !!
      │   check.warn(importable)
      │ error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/      
      │ visual-cpp-build-tools/
      │
    
    PS C:\code\duckdb-pip> pixi add pip          
    ✔ Added pip
    PS C:\code\duckdb-pip> pixi run pip install duckdb
    Collecting duckdb
      Downloading duckdb-0.9.2-cp311-cp311-win_amd64.whl.metadata (798 bytes)
    Downloading duckdb-0.9.2-cp311-cp311-win_amd64.whl (10.3 MB)
       ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 10.3/10.3 MB 21.8 MB/s eta 0:00:00
    Installing collected packages: duckdb
    Successfully installed duckdb-0.9.2
    
    
  4. liquidcarbon commented on Feb 12, 2024

    @liquidcarbon
    Contributor
    1. work around was just to use pip to install using pixi tasks

    @pablovela5620 I am also finding this necessary quite often, probably more often than @ruben-arts would like :)

    In this pattern the environment definition is fragmented between pixi.toml tasks and pixi.lock. It could work, esp with pinned pip installs in tasks, but is it the intention?

  5. ruben-arts commented on Feb 12, 2024

    @ruben-arts
    ContributorAuthor

    In this pattern the environment definition is fragmented between pixi.toml tasks and pixi.lock. It could work, esp with pinned pip installs in tasks, but is it the intention?

    @liquidcarbon This is indeed not what we want as UX but we simply need to develop more to support all PyPI packages. Its a weird bunch of requirements we have to support to be equivalent to pip. So please keep posting non working packages!

  6. ruben-arts commented on Feb 12, 2024

    @ruben-arts
    ContributorAuthor

    @liquidcarbon the duckdb on conda-forge has been continued on python-duckdb which should be available on windows. We'll keep the example for pypi to test more!

  7. tdejager commented on Feb 15, 2024

    @tdejager
    Contributor

    @liquidcarbon I cannot reproduce this, neither on OSX or on windows. It's strange it does not select the .whl for some reason.

  8. tdejager commented on Feb 15, 2024

    @tdejager
    Contributor

    @tylerjw actually it also fails for the same version in pip on apple silicon, like pip we error out when we cannot build the first source distribution.

  9. tdejager commented on Feb 15, 2024

    @tdejager
    Contributor

    @pablovela5620 so it seems mediapipe 10.9 is a package with an invalid RECORD file, I manually checked it and it's incorrect.

    This is mentioned in the PyPa

    During extraction, wheel installers verify all the hashes in RECORD against the file contents. Apart from RECORD and its signatures, installation will fail if any file in the archive is not both mentioned and correctly hashed in RECORD.

    Mediapipe has a version.txt that is not mentioned in the RECORD for the 10.9 release.

    Which in this case triggers the error, I'm unsure why pip does no do this. But I feel its good to adhere to the standard here.

    In any case, mediapipe 10.8 does seem to work, you could use that instead.

    Also see: google-ai-edge/mediapipe#5025

  10. liquidcarbon commented on Feb 15, 2024

    @liquidcarbon
    Contributor

    @liquidcarbon I cannot reproduce this, neither on OSX or on windows. It's strange it does not select the .whl for some reason.

    @tdejager Just tried on Win10, original comment was on Win11
    same thing:

    PS C:\Users\a\Desktop\code\duckdb-pip> pixi add python=3.11
    ✔ Added python 3.11.*
    PS C:\Users\a\Desktop\code\duckdb-pip> pixi add duckdb
    × could not determine any available versions for duckdb on win-64. Either the package could not be found or version
    │ constraints on other dependencies result in a conflict.
    ╰─▶ Cannot solve the request because of: No candidates were found for duckdb *.

    I was on Pixi 0.9.1, upped to 0.13.0 - same thing

    But pixi add --pypi duckdb works. 🤷‍♂️

  11. ruben-arts commented on Feb 15, 2024

    @ruben-arts
    ContributorAuthor
  12. liquidcarbon commented on Feb 15, 2024

    @liquidcarbon
    Contributor

    @ruben-arts noted -- I just wasn't sure which part @tdejager was trying to reproduce

  13. awray3 commented on Feb 25, 2024

    @awray3

    Tensorflow metal on Apple silicon MacOS 14.2.1:

    pixi init tf-metal && cd tf-metal
    pixi add "python>=3.11" "tensorflow>=2.13" pip
    pixi add --pypi tensorflow-metal
    > × failed to resolve `pypi-dependencies`, due to underlying error
      ╰─▶ The following packages are incompatible
          └─ tensorflow-metal * cannot be installed because there are no viable options:
             └─ tensorflow-metal 0.1.0 | 0.1.1 | 0.1.2 | 0.2.0 | 0.3.0 | 0.4.0 | 0.5.0 | 0.5.1 | 0.6.0 | 0.7.0 | 0.7.1
          | 0.8.0 | 1.0.0 | 1.0.1 | 1.1.0 is excluded because none of the artifacts are compatible with the Python
          interpreter or glibc version and there are no supported sdists
    
    pixi run pip install tensorflow-metal
    > Successfully installed tensorflow-metal-1.1.0
  14. baszalmstra commented on Feb 25, 2024

    @baszalmstra
    Contributor
  15. 58 remaining items

  16. ruben-arts commented on Feb 18, 2025

    @ruben-arts
    ContributorAuthor

    @Goooyi pixi global doesn't support pypi dependencies: #2261

  17. pablovela5620 commented on Feb 25, 2025

    @pablovela5620
    Contributor

    having some weirdness with rerun-sdk, feedstock isnt yet merged for latest 0.22.1 update. If I try to add via cli

    (pi0-lerobot) ⚡ hocap-dataset ~/pi0-lerobot pixi add rerun-sdk==0.22.1 --pypi
    Error: 
      × failed to solve the pypi requirements of 'default' 'linux-64'
      ├─▶ failed to resolve pypi dependencies
      ╰─▶ Because rerun-sdk==0.22.1 has no wheels with a matching platform tag (e.g., `manylinux_2_28_x86_64`) and you require rerun-sdk==0.22.1, we
          can conclude that your requirements are unsatisfiable.
          
          hint: Wheels are available for `rerun-sdk` (v0.22.1) on the following platforms: `manylinux_2_31_aarch64`, `manylinux_2_31_x86_64`,
          `macosx_10_12_x86_64`, `macosx_11_0_arm64`, `win_amd64`
    
    Error: 
      × failed to solve the pypi requirements of 'default' 'linux-64'
      ├─▶ failed to resolve pypi dependencies
      ╰─▶ Because only the following versions of rerun-sdk are available:
              rerun-sdk<=0.21.0
              rerun-sdk==0.22.0
              rerun-sdk==0.22.1
          and rerun-sdk>=0.21.0 has no wheels with a matching platform tag (e.g., `manylinux_2_28_x86_64`), we can conclude that rerun-sdk>=0.21.0
          cannot be used.
          And because lerobot==0.1.0 depends on rerun-sdk>=0.21.0, we can conclude that lerobot==0.1.0 cannot be used.
          And because only lerobot[pusht]==0.1.0 is available and you require lerobot[pusht], we can conclude that your requirements are unsatisfiable.
          
          hint: Pre-releases are available for `rerun-sdk` in the requested range (e.g., 0.22.1rc1), but pre-releases weren't enabled (try:
          `--prerelease=allow`)
          
          hint: Wheels are available for `rerun-sdk` (v0.22.1) on the following platforms: `manylinux_2_31_aarch64`, `manylinux_2_31_x86_64`,
          `macosx_10_12_x86_64`, `macosx_11_0_arm64`, `win_amd64`
    

    but if I directly link to the url

    rerun-sdk = { url = "https://files.pythonhosted.org/packages/1e/db/3ce2be017d7d4ac0948fb064bf7417b36c96bc07d1b8a922017606ba03c6/rerun_sdk-0.22.1-cp38-abi3-manylinux_2_31_x86_64.whl" }
    

    it works just fine

  18. traversaro commented on Feb 25, 2025

    @traversaro
    Contributor

    feedstock isnt yet merged for latest 0.22.1 update

    Kind OT, but anyhow: I pinged in conda-forge/rerun-sdk-feedstock#61, feel free to ping yourself in the future if something like this happens, thanks!

  19. pablovela5620 commented on Feb 25, 2025

    @pablovela5620
    Contributor

    Yes, I should have started with that!

    feedstock isnt yet merged for latest 0.22.1 update

    Kind OT, but anyhow: I pinged in conda-forge/rerun-sdk-feedstock#61, feel free to ping yourself in the future if something like this happens, thanks!

  20. dlyz commented on Apr 3, 2025

    @dlyz
    1. What did you run and what was the outcome?

      Command:
      pixi add --pypi flash-attn

      pixi.toml

      [workspace]
      channels = ["conda-forge"]
      name = "pixi-example"
      platforms = ["win-64"]
      version = "0.1.0"
      
      [tasks]
      
      [dependencies]
      python = ">=3.11,<3.13"
      pip = ">=25.0.1,<26"
      setuptools = ">=75.8.2,<76"
      
      [pypi-dependencies]
      torch = { version = "<2.6", index = "https://download.pytorch.org/whl/cu124" }
      torchvision = { version = "<0.21", index = "https://download.pytorch.org/whl/cu124" }
      torchaudio = { version = "<2.6", index = "https://download.pytorch.org/whl/cu124" }
      packaging = ">=24.2, <25"
      einops = ">=0.8.1, <0.9"
    2. What error did pixi return?

      Error:   × Failed to update PyPI packages for environment 'default'
        ├─▶ Failed to prepare distributions
        ├─▶ Failed to build `flash-attn==2.7.4.post1`
        ├─▶ The build backend returned an error
        ╰─▶ Call to `setuptools.build_meta:__legacy__.build_wheel` failed (exit code: 1)
            
            [stderr]
            Traceback (most recent call last):
              File "<string>", line 14, in <module>
              File "C:\Users\***\AppData\Local\rattler\cache\uv-cache\builds-v0\.tmp36pAkT\Lib\site-packages\setuptools\build_meta.py", line 334, in get_requires_for_build_wheel
                return self._get_build_requires(config_settings, requirements=[])
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
              File "C:\Users\***\AppData\Local\rattler\cache\uv-cache\builds-v0\.tmp36pAkT\Lib\site-packages\setuptools\build_meta.py", line 304, in _get_build_requires
                self.run_setup()
              File "C:\Users\***\AppData\Local\rattler\cache\uv-cache\builds-v0\.tmp36pAkT\Lib\site-packages\setuptools\build_meta.py", line 522, in run_setup
                super().run_setup(setup_script=setup_script)
              File "C:\Users\***\AppData\Local\rattler\cache\uv-cache\builds-v0\.tmp36pAkT\Lib\site-packages\setuptools\build_meta.py", line 320, in run_setup
                exec(code, locals())
              File "<string>", line 22, in <module>
            ModuleNotFoundError: No module named 'torch'
      
            hint: This error likely indicates that `[email protected]` depends on `torch`, but doesn't declare it as a build dependency. If `flash-attn` is a first-party package, consider adding `torch` to its `build-system.requires`. Otherwise, `uv     
            pip install torch` into the environment and re-run with `--no-build-isolation`.

      import torch works of course using pixi run python

    3. Can pip install the package?
      It works in pure conda env, but does not work with pip inside the pixi (pixi run pip install ...) resulting with ImportError: cannot import name 'setup' from 'setuptools' (unknown location).

    4. What platform are you on?
      win-64

    5. Did you find a workaround, if so please explain.
      I guess one could install torch using conda packages (pytorch-gpu, etc) but there is no torchaudio for win-64 and I couldn't manage to install torchaudio separately using --pypi either. So no workaround so far.

  21. traversaro commented on Apr 3, 2025

    @traversaro
    Contributor

    The hint is relevant:

          hint: This error likely indicates that `[email protected]` depends on `torch`, but doesn't declare it as a build dependency. If `flash-attn` is a first-party package, consider adding `torch` to its `build-system.requires`. Otherwise, `uv     
          pip install torch` into the environment and re-run with `--no-build-isolation`.
    

    Probably you can disable build-isolation for flash-attn, see https://pixi.sh/latest/reference/pixi_manifest/#no-build-isolation ? Note that in that case probably you also nee to install other build dependencies to the environment explicitly.

  22. dlyz commented on Apr 3, 2025

    @dlyz

    Probably you can disable build-isolation for flash-attn

    Thank you, it helped. I overlooked the thing about build isolation, got confused after seeing uv mentioned, sorry. It would be great though if there would be a message from pixi with the link you provided, but not sure it worth investing.

  23. dhirschfeld commented on Apr 9, 2025

    @dhirschfeld
    Contributor

    When trying to install a pyproject.toml project where a dependency depends on pywin32, pixi will throw a failed to resolve pypi dependencies error, even if the dependency was marked with sys_platform == 'win32'

    Example pyproject.toml

    [project]
    authors = [{name = "Dave Hirschfeld", email = "[email protected]"}]
    name = "deleteme"
    requires-python = ">= 3.11"
    version = "0.1.0"
    dependencies = [
      "httpx>=0.27.0",
      "httpx-negotiate-sspi>=0.28.1; sys_platform == 'win32'",
    ]
    
    [build-system]
    build-backend = "hatchling.build"
    requires = ["hatchling"]
    
    
    
    [tool.pixi.workspace]
    channels = ["conda-forge"]
    platforms = [
        "linux-64",
        "win-64"
    ]
    
    
    [tool.pixi.pypi-dependencies]
    deleteme = { path = ".", editable = true }
    ❯ pixi install --all
    Error:   × failed to solve the pypi requirements of 'default' 'linux-64'
      ├─▶ failed to resolve pypi dependencies
      ╰─▶ Because only the following versions of pywin32 are available:
              pywin32<=223
              pywin32==224
              pywin32==225
              pywin32==226
              pywin32==227
              pywin32==228
              pywin32==300
              pywin32==301
              pywin32==302
              pywin32==303
              pywin32==304
              pywin32==305
              pywin32==306
              pywin32==307
              pywin32==308
              pywin32==309
              pywin32==310
          and pywin32>=223,<=305 has no wheels with a matching Python ABI tag (e.g., `cp312`), we can conclude that pywin32>=223,<=305 cannot
          be used.
          And because pywin32>=306 has no wheels with a matching platform tag (e.g., `manylinux_2_28_x86_64`) and httpx-negotiate-sspi==0.28.1
          depends on pywin32>=223, we can conclude that httpx-negotiate-sspi==0.28.1 cannot be used.
          And because only httpx-negotiate-sspi<=0.28.1 is available and you require httpx-negotiate-sspi>=0.28.1, we can conclude that your
          requirements are unsatisfiable.
          
          hint: You require CPython 3.12 (`cp312`), but we only found wheels for `pywin32` (v305) with the following Python ABI tags: `cp36m`,
          `cp37m`, `cp38`, `cp39`, `cp310`, `cp311`
          
          hint: Wheels are available for `pywin32` (v310) on the following platforms: `win32`, `win_amd64`, `win_arm64`

    Note

    This is when trying to install the project from a linux box.

  24. tdejager commented on Apr 10, 2025

    @tdejager
    Contributor

    Yes, you are right this is kind of a big issue we should pass the environment markers correctly to uv. Which we currently do not seem to do.

  25. dhirschfeld commented on Apr 10, 2025

    @dhirschfeld
    Contributor

    I have to have things working on both Windows and Linux so this one is definitely biting me.

    It's not a show-stopper though - I just make those deps [tool.pixi.target.win-64.dependencies] which works fine for pixi envs. Things are a little broken for pip users, but I'm trying to discourage the use of pip anyway! 🤣

  26. tdejager commented on Apr 10, 2025

    @tdejager
    Contributor

    Aha okay! Good to know 😄

  27. atonderski commented on Apr 26, 2025

    @atonderski

    Also ran into this issue, and the proposed workaround breaks compatibility with for example direct uv pip install.

    Any estimate on if/when this will be fixed?

  28. kkraus14 commented on Jul 25, 2025

    @kkraus14
    Contributor

    I have run into the same issue related to a "pywin32; sys_platform == 'win32'" dependency, but I need to continue supporting pip users and producing pip packages. There isn't really a workaround as far as I can tell other than potentially moving away from using the pyproject.toml support and having a separate pixi.toml with relevant information duplicated across them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions