Error at canister deployment using kybra

Hey, I am extremely new to development using IC and I was trying to run the basic hello world program that the developers docs of IC ask you to run to teach you how to deploy into a local test server. But I am running into an error in the deployment phase and I can’t figure out what’s causing this. The error says “Kybra” isn’t installed and so I made sure Python was set up properly and Kybra was in fact installed, I double and triple-checked, I’ve been trying to find a solution to this on various sites for a few hours now and I can’t seem to find someone who has the same issue maybe because rust is majorly preferred over python for this. My friend who was following the same docs ran into the exact same problem, and we weren’t particularly communicating while doing this, am running it on windows WSL while he is running it on native Linux, so I don’t think it’s some problem with the basic setup, we are messing something up and it would be extremely helpful if someone could help find and fix this problem so that we could start to actually try making something. Thank you.

(already tried dfx start --clean)

Error message at “dfx deploy”:

Error: Failed while trying to deploy canisters.

Caused by: Failed while trying to install all canisters.

Caused by: Failed to install wasm module to canister ‘hello_backend’.

Caused by: Failed during wasm installation call

Caused by: The replica returned a rejection error: reject code CanisterError, reject message Error from Canister bkyz2-fmaaa-aaaaa-qaaaq-cai: Canister called ic0.trap with message: ModuleNotFoundError: No module named ‘kybra’.

Consider gracefully handling failures from this canister or altering the canister to handle exceptions. See documentation: Execution errors | Internet Computer, error code None

Can you please confirm that you have done all of these steps?

I think I replied to you in the Discord channel, let me know if you are still stuck, it seems like you are not running dfx deploy from the virtual environment. If that’s not the case this could be a deeper bug.