-
-
Notifications
You must be signed in to change notification settings - Fork 209
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.
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
[BUG] config.toml missing #684
Comments
If you can run the tool, then the config should be somewhere i guess. |
Well, in my effort to not put my username, I forgot about that in the second log. It's only 1 user and after starting the app it doesn't create a toml file there. I'm running windows 11 with the latest updates. I checked config.py and it doesn't account for first time use. Is it somewhere else? To reproduce what I'm doing, delete your steamrip folder in AppData (as you already have one) and run the CLI tool. It never creates a new toml config. |
Ok, I checked with a python installation from MS Store and it behaves like was described. An example of this that I found: https://stackoverflow.com/questions/76599722/python-creates-directories-and-files-in-a-different-place-than-specified I haven't found exactly how to manage that, but it's just a weird behaviour of the MS app(s). So as a quick and clean solution I'd recommend using a normal python installation if you can, from python.org, Or put the |
That was indeed the issue. I downloaded Python from python.org and now it works as intended. |
Describe the bug
The config.toml is not created in AppData on app startup, so when you try to open it through the CLI, it says there is no such file.
Command Used
Debug Traceback
Config File
:D
Operating System
Windows
streamrip version
rip, version 2.0.5
Screenshots and recordings
No response
Additional context
I installed the CLI tool through pip and I don't have my pip Scripts in PATH. I am able to run the CLI regardless, it's just an annoyance. Is it intended behavior (like the app being portable) and can that be fixed in future releases.
Thank you!
The text was updated successfully, but these errors were encountered: