FEATURE: Allowing the User to Define the Path for PyWhatKit_DB.txt #307
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added a function to set the absolute path for where the PyWhatKit_DB.txt file is to be made and edited (I needed this for a thing I was doing and thought it might be helpful to others as well - this is my first pull req, be gentle fr fr)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
Added a function to set the absolute path for where the PyWhatKit_DB.txt file is to be made and edited.
Why is this Necessary?:
I wanted to launch a script using PyWhatKit on startup, but the relative pathing kept getting me Erno 13's and I had to give it an absolute path to fix the issue
Changes:
I defined a function that allows the user to enter a path and sets the value of a variable 'log_path'. This variable is then used as the path for all logging.