pyca / pyca/pynacl

Recipe conflict between pip and conda

Open
#910 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
1.2k
Forks
267
Avg merge
42m
Merged PRs (30d)
2

Description

There is a mismatch on the cffi requirement between the conda and pip recipes. Is this intentional and if not, can they be updated to match? As a result, my rattler packaging fails on a pip check as the dependencies can't resolve. I have other packages I'm using that require cffi < 2. I would prefer having to manually pin pynacl < 1.6.1 and if the current version was marked to require cffi >= 2 that would fix the issue for me..

The pip package requirements are as follows:

[build-system]
# Must be kept in sync with `dependencies` below
requires = [
    "setuptools>=61.0.0,!=74.0.0",
    "wheel",
    "cffi>=1.4.1; platform_python_implementation != 'PyPy' and python_version < '3.9'",
    "cffi>=2.0.0; platform_python_implementation != 'PyPy' and python_version >= '3.9'",
]

Conda requirements are as follows:

host:
    - _libgcc_mutex 0.1 conda_forge
    - _openmp_mutex 4.5 2_gnu
    - bzip2 1.0.8 hda65f42_8
    - ca-certificates 2025.11.12 hbd8a1cb_0
    - cffi 2.0.0 py311h03d9500_1
...
  run:
    - __glibc >=2.17,<3.0.a0
    - cffi >=1.4.1
    - libgcc >=14
    - libsodium >=1.0.20,<1.0.21.0a0
...

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Locate the pip build-system/dependencies metadata and the conda recipe, then compare their cffi constraints across supported Python versions. Confirm the intended lower bound with the package requirements and dependency-resolution behavior; done means the recipes are consistent and the reported pip check conflict is resolved.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
build-system
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.