Skip to content

Conversation

marcoesters
Copy link

Description

Activating build and test environments may fail on Windows if the path contains spaces, which is the case for example if the user name is <first name> <last name>.

The cause of this error is some unwrapped paths in the activation files. The build environment only fails when a bld.bat is present in the recipe directory. In my observation, the test environment calls never appear to be fatal, i.e., the build succeeds even though there is an error in stderr.

Closes #5737

Checklist - did you ...

  • Add a file to the news directory (using the template) for the next release's release notes?
  • Add / update necessary tests?
  • Add / update outdated documentation?

@github-project-automation github-project-automation bot moved this to 🆕 New in 🔎 Review Jun 9, 2025
@conda-bot conda-bot added the cla-signed [bot] added once the contributor has signed the CLA label Jun 9, 2025
Copy link

codspeed-hq bot commented Jun 9, 2025

CodSpeed Performance Report

Merging #5739 will not alter performance

Comparing marcoesters:win-paths-spaces (80adb39) with main (bf2bec3)

Summary

✅ 5 untouched benchmarks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla-signed [bot] added once the contributor has signed the CLA

Projects

Status: 🆕 New

Development

Successfully merging this pull request may close these issues.

Windows: activating environments fail with paths containing spaces

2 participants