Closed wholtz closed 4 months ago
Do you have a MWE environment.yaml
you could share?
Seems to give the error on any environment I throw at it. But here is a specific one:
environment.yaml:
name: base
platforms:
- linux-64
channels:
- conda-forge
dependencies:
- jq
I'm unable to reproduce this. Any ideas?
$ docker run --rm -it mambaorg/micromamba
$ cat >> environment.yml
name: base
platforms:
- linux-64
channels:
- conda-forge
dependencies:
- jq
$ micromamba install -y -c conda-forge conda-lock && conda-lock
...
Locking dependencies for ['linux-64']...
INFO:conda_lock.conda_solver:linux-64 using specs ['jq']
- Install lock using: conda-lock install --name YOURENV conda-lock.yml
It's weird. The test suite has lots of holes which I'm slowly trying to get patched, but a bunch of stuff is tested, and it passes under Python 3.12.
I also do not get the error while running within a mambaorg/micromamba
container. When I get the error, I'm using python v3.12.1 installed via pyenv
(so built locally). And for completeness, this is with an Apple M2 CPU.
Interesting. Would you be able to make a Dockerfile for it?
I have not yet ventured into the world of macos native containers. I'll look into it.
Are you aware of this? https://docs.python.org/dev/whatsnew/3.12.html#:~:text=PEP%20632%3A%20Remove,activated%20virtual%20environment.
Maybe python3.12 from conda-forge is automatically pulling in Setuptools?
How convinced are you that it's a mac thing?
Setuptools is a really great hypothesis. Does it work if you install setuptools in your env? Maybe we just need an explicit setuptools dependency? That would be a very easy fix.
I'm not convinced it is a mac thing. I'll try adding Setuptools in a few hours. Need to head out right now.
Thanks! 2.5.5 did fix it for me.
Checklist
What happened?
This is similar to #542 but the stack trace is different, so I believe it will require a different fix.
Conda Info
Conda Config
Conda list
Additional Context
When I using python 3.11 the error does not occur.