MNT: Remove 'pip install' options in recipes

[matthewfeickert]

Resolves #582

Description

• Remove --no-deps --no-build-isolation pip install options in recipes as the build tool (e.g. conda-build, rattler-build) will enforce all required pip install options itself at build time.

c.f.:

• docs: Remove 'pip install' options in recipes conda-build#5541
• docs: Remove 'pip install' options in recipes prefix-dev/rattler-build#1198

[matthewfeickert]

This is ready for review.

[ocefpaf]

@wolfv we can't do this while we use conda-build b/c of the multiple outputs bug. However, if/when we drop conda-build, do you know if rattler-build will behave as expected with multiple outputs?

[matthewfeickert]

we can't do this while we use conda-build b/c of the multiple outputs bug.

Out of curiosity, is there an issue for this?

[ocefpaf]

Out of curiosity, is there an issue for this?

I'm pretty sure there is one, or more, in conda-build. To be fair, are trying to keep conda-build on life support as we move to rattler-build, so I don't think anyone is working on that.

[marcelotrevisani]

@wolfv we can't do this while we use conda-build b/c of the multiple outputs bug. However, if/when we drop conda-build, do you know if rattler-build will behave as expected with multiple outputs?

after we drop conda-build and start to use rattle, we could add this when the --strict-conda-forge flag is enabled

[matthewfeickert]

As I don't know the full history of things, or even the technical problems with conda-build, should I instead change this PR to add in --ignore-installed as that's also a flag set (conda/conda-build#5543) and then once conda-forge has gone full rattler-build removing all the flags can be revisited?

I also don't know if there is a projected timeline for full rattler-build adoption. (2025? 2026?)

[marcelotrevisani]

As I don't know the full history of things, or even the technical problems with conda-build, should I instead change this PR to add in --ignore-installed as that's also a flag set (conda/conda-build#5543) and then once conda-forge has gone full rattler-build removing all the flags can be revisited?

I also don't know if there is a projected timeline for full rattler-build adoption. (2025? 2026?)

yeah, I think that would be nice to add the flag for now :)

[matthewfeickert]

... then once conda-forge has gone full rattler-build removing all the flags can be revisited?

@marcelotrevisani conda-forge has now changed to use the v1 / rattler-build recipe format as the default (c.f. PR #669). @wolfv can correct me if I'm wrong, but I believe that the issue with the flags being needed for recipes with multiple build outputs is now also resolved (c.f. conda-forge/conda-forge.github.io#2913, #582 (comment), and #582 (comment)). So I think this PR is ready for review again.