#conda & PyPI

1 messages · Page 1 of 1 (latest)

raven fiber
#

IMO there’s absolutely no reason to add any kind of mixing the worlds “support” without actually resolving things together. Otherwise you have your conda constraints, resolve them, and then you tell pip or so “OK, here’s a completely standalone set of constraints, feel free to go ham on this venv, there’s no rules, just fuck shit up”

#

Why even bother with constraints if that can happen at any moment? In CI, maybe you could call conda again after to make it verify that pip/uv/whatever didn’t violate the conda constraints, but I’ve never seen anyone do even that.

waxen turret
#

Is anyone even validating that the conda installation metadata matches the Python package installation metadata?

#

Seems like a prerequisite before you check that the Python package tool didn't break your conda packages, you can't expect the Python package tool to act correctly with metadata that doesn't match what you think it should be

raven fiber
#

Until a few years ago, a bunch of conda packages didn’t have PyPI metadata. Since importlib.metadata became a thing, that quickly changed, and I don’t think a lot of packages are still missing it.