numpy: asan - #50

I think the proper way to do this is with a multi-output recipe, then we can depend on e.g. either python or python-asan

Not so sure about that. I think multi-output recipes are when you want multiple separate packages, rather than different build variants of the same package. Building multiple outputs would also be much slower, because they'd be full rebuilds of the whole package with different compiler flags.

Unless you meant building an extra output like a mutex? A la this:

https://github.com/conda-forge/python-feedstock/blob/97b95f1bad4d0c0b01e458bf7e0442635c9d7b6f/recipe/meta.yaml#L329-L337

That might make sense, in a way it's similar to python-freethreading: the Python build has some property (say asan-build, it's not specific to python) that multiple packages should share, and can be installed in a synchronized fashion.

You may want to get some expert input on this one, I don't know if this is possible today with Pixi and if so what the best solution is.

It's also similar to the "build profiles" with debug/release variants.

Agreed with everything you have said, and expert opinion has already been sought :). Indeed python-freethreading was what I was looking at when I wrote that.

I didn't jump to variants because it is currently not possible to select a variant of a local path dependency (e.g. via build_string) with pixi-build (we have an internal issue but should make a public one).

Once we have Wolf's flags CEP the real "proper" way to do this would probably look something like prefix-dev/pixi#2813 (comment).

Sounds great then!