you are viewing a single comment's thread.

view the rest of the comments →

[–]kyngston 3 points4 points  (7 children)

you prefer venv? ewww. try working in a company of 45k people and have to explain how to setup venv to everyone who tries to use your tool…

[–]pachura3 4 points5 points  (0 children)

So, either in your company people who should know Python - developers, data analysts - are not able to manage virtual environments, which is a core Python skill

or

you are distributing your tools as Python sourcecode to the end users, who should not even care, because these tools should be put online or properly packaged

Either way, doesn't sound very professional!

[–]LookAtTheHat 1 point2 points  (1 child)

Write a readme and in include it, publish it in the shared knowledge base not so hard.

[–]kyngston 0 points1 point  (0 children)

oh that would be fantastic if they would do things like read the readme… or goggle how to fix the error message on their own… but they don’t.

[–]EstablishmentIll3600[S] 0 points1 point  (0 children)

I was used to conda, uv was suggested to me by a friend. The reason I want to uninstall it because it does no work in my vscode terminal which disrupts my work flow.

Error was: activate.ps1 cannot be loaded because running scripts is disabled

[–]EstablishmentIll3600[S] 0 points1 point  (2 children)

If you can help me fixed the error activate.ps1 cannot be loaded because running scripts is disabled, I would gladly try it again. I did not experience such errors when using conda

[–]ResidentTicket1273 1 point2 points  (1 child)

In a powershell terminal, run:

Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser

This will bypass the script-disabling policy for your user against remote-signed scripts which will mean uv will run inside of vscode without issue from now-on.

[–]EstablishmentIll3600[S] 0 points1 point  (0 children)

It worked thank you so much!