Rather new to pipenv, though not to all of virtual environments under python, my app is trying to create an INI file in my Windows user home directory, but running my code from within VSCode or from the command line, the INI file always gets created in a very different path, such as: C:\Users...... \AppData\Local\Packages\PythonSoftwareFoundation.Python.3.12_qbz5n2kfra As far as I can tell, this happens whether I am running the code within VSCode, or directly with python wppa.py from the command line. Even deleting the python cache file, removing the pipenv specific files.env, pipfile & pipfile.lock from the work directory has no effect. I can see why this might be desirable/helpful/needed in some cases, but how can I go back to have the file created where the paths I see seem to indicate it should be?? Right now it seems the only way forward is to abandon all of the alleged pipenv advantages and do without. Continue reading...
