Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

python env #549

Open
V70024 opened this issue Oct 7, 2023 · 2 comments
Open

python env #549

V70024 opened this issue Oct 7, 2023 · 2 comments

Comments

@V70024
Copy link

V70024 commented Oct 7, 2023

What is the reason for this problem?

2023-10-07_16-58
@Aswin-00
Copy link

can you explain more about the issue .i think its some sort of naming error

@b-ryan
Copy link
Owner

b-ryan commented Oct 24, 2023

I'm unsure what the issue is here. It looks like you are using fish shell and sourcing the venv activate file didn't work, but sourcing activate.fish did, which looks like what I would expect. powerline-shell is then showing (v-env) to indicate that you have the virtualenv in the v-env directory activated. Looks normal from what I can see.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@b-ryan @V70024 @Aswin-00