Skip to content

Problems with Python 3 venv on the windows-latest VM #25043

Answered by bek0s
bek0s asked this question in Actions
Discussion options

You must be logged in to vote

False alarm! :slight_smile: Turns out this is the expected behaviour of cmd. To fix my “issue” I need to call the activate script using “call”:

call venv\Scripts\activate.bat

Thaks! :slight_smile:

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
1 participant