Documenting Working Codes: Path and PipEnv
I didn’t even understand the error the command line keep returning
something about 'file path cannot load'
it's not like StackOverFlow does not try
it's just annoying once your situation looks unique
the problem: the django on my system was installed 2 years ago.
back then virtualenv was a thing
now, not so much
the python community moved on to pipenv
WHAT DID I DO THEN?
created a fresh user on my system (named it WorkMode)
deleted every path on the user variables except the default system paths
focused on my python 3.9.4
added the python39 to the “Path” in “user variables”
saved it
Ran the “echo %path%” on the command line
The python39 path added to the user variables DIDN’T reflect.
Went back.
added the python39 to the “Path” in “System variables”
Ran the “echo %path%” on the command line
The python39 path finally reflected.
ONCE
Meaning the python39 path are added to the user variables is not reflecting
Just the one added to the system variables.
Reason?
I don’t know.
In other words, welcome to programming.
Leave Documenting Working Codes: Path and PipEnv to:
Best Posts From HolyBranches
We have not curated any of holybranches's posts yet. But you can encourage our curation team to review posts by visiting them regularly and by referring other readers. Because we give priority to frequently read content.
More Posts From HolyBranches
- Trying to Manually set up a virtual environment with pipenv
- Documenting Working Codes: Re-Establishing The Fact That We Must Pipenv-Install Django Everytime We Create A New Project Inside The Directory Containing That New Project
- Documenting Working Codes: Must we pipenv-install django everytime we start a new project?
- Documenting Working Codes: Path and PipEnv
- Documenting Working Codes - A Django Setup Routine that actually Works
- Documenting Working Codes - Windows Powershell Trash?
- Documenting Working Codes - Django Setup
- A Hermit's Opinion - 3
- A Hermit's Opinion - 2
- A Hermit's Opinion - 1