CodSpeed Performance Report

Merging #14725 will not alter performance

_{Comparing soapy1:dont-allow-input-file-type-mixing (8589a79) with main (eb3b481)}

Summary

✅ 21 untouched benchmarks

pre-commit.ci autofix

@soapy1 I took the liberty to fill in the TODO, so we can continue with conda/conda-planning#15. Do these changes work for you?

Looks great @jezdez !

Following the bug reproduction steps from the original issue, I get the result:

$ conda create -n testenv-mixed --file env1.txt --file env2.txt

EnvironmentFileTypeMismatchError: Cannot mix environment file formats.

'env1.txt' is a requirements.txt format file
'env2.txt' is a unknown (AttributeError) format file

Where the input files are:

env1.txt (explicit file)

@EXPLICIT
https://repo.anaconda.com/pkgs/main/linux-64/_libgcc_mutex-0.1-main.conda
https://repo.anaconda.com/pkgs/main/linux-64/ca-certificates-2025.2.25-h06a4308_0.conda

env2.txt (regular text file)

numpy

I think this is not exactly right. env1.txt is an explicit file and env2.txt is a requiremets file. This error is caused by some issues in the plugin implementations. I'll open a seperate issue for that. I don't think it should hold up merging this.

Related issues:

• Make environment.yaml environent_spec plugin more conservative in files it tries to handle conda-planning#46
• Add environment spec plugin for explicit input file types conda-planning#47

This just needs a news file!

Calling out that this PR does not fully fix the issue described in #14684. I can confirm that this PR together with conda/conda-planning#47 does fully resolve the issue. Using the env1.txt and env2.txt files specified in the issue:

$ conda create -n testenv-mixed --file env1.txt --file env2.txt

EnvironmentFileTypeMismatchError: Cannot mix environment file formats.

'env1.txt' is a explicit format file
'env2.txt' is a requirements.txt format file

@soapy1 Makes sense, I think we can merge this separately, and then close the ticket once they landed.

Ok, I see the concern of @soapy1 and @jjhelmus in #14820 about not merging that, so I have the sense that we'll end up stalling everything to get the environment class refactor in first. This is a traditional "perfect is the enemy of the good" moment, we need to start somewhere and most of the PRs around the environment changes are just snapshots in time until the next release anyways. Remember that we have the 25.5.x release branch in case we need to do patch release in between.