Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dependency of pip installed package is missing #730

Open
2 tasks done
wholtz opened this issue Oct 8, 2024 · 2 comments
Open
2 tasks done

Dependency of pip installed package is missing #730

wholtz opened this issue Oct 8, 2024 · 2 comments

Comments

@wholtz
Copy link

wholtz commented Oct 8, 2024

Checklist

  • I added a descriptive title
  • I searched open reports and couldn't find a duplicate

What happened?

An environment.yaml:

name: base
platforms:
  - linux-64
channels:
  - conda-forge
dependencies:
  - python=3.12.7
  - pip=24.2
  - pip:
      - jupyter==1.1.1

What I did:

$ conda-lock -f environment.yaml
Locking dependencies for ['linux-64']...
INFO:conda_lock.conda_solver:linux-64 using specs ['python 3.12.7.*', 'pip *']
 - Install lock using: conda-lock install --name YOURENV conda-lock.yml
$ grep 'name: ipython' conda-lock.yml
$ grep ipython conda-lock.yml
    ipython: '>=7.23.1'
    ipython: '>=6.1.0'
    ipython: '*'

I expected the first grep to return a line, indicating that there is a section of the yaml describing a source for ipython.

Additional Context

I'm using the current main branch of conda-lock (commit aa227c33c739768823f095d31164b7c9555beae2).

$ conda-lock --version
conda-lock, version 2.5.8.dev266+gaa227c3
$ pipx list | grep conda.lock
   package conda_lock 2.5.8.dev266+gaa227c3, installed using Python 3.12.0
    - conda-lock
$ uname -a
Darwin example.local 23.6.0 Darwin Kernel Version 23.6.0: Wed Jul 31 20:48:52 PDT 2024; root:xnu-10063.141.1.700.5~1/RELEASE_ARM64_T6020 arm64 arm Darwin
@LL924
Copy link

LL924 commented Oct 28, 2024

We got the same issue recently with other packages installed with pip.

@maresb
Copy link
Contributor

maresb commented Oct 29, 2024

Thanks a lot for the report and sorry about the delayed response.

I ran a git bisect on this, and the first bad commit is 1ac5f7c, so this is indeed a regression in main. 😞 I'll fix this before the v3 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants