Fix datetime import error in get_today_str function #169
Conversation
This file contains hidden or 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
Co-authored-by: Qwen-Coder <[email protected]>
… graph and register in langgraph.json\n- Add scripts/call_api.py for parametric server calls (invoke/stream)\n- Add Makefile targets (dev, invoke/stream, essay/deep shortcuts, compare-models)\n- Add Streamlit prototype (app.py) and local JSON storage\n- Add AGENTS.md contributor guide and docs/ESSAY_WRITER_CLI_GUIDE.md\n- Update .gitignore (sessions, out/)
|
Fixed -- |
|
Please open separate PR for anything unrelated to the |
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.
This PR resolves an import error in the get_today_str function where datetime.datetime.now() was being used
but only datetime was imported, causing a NameError.
Changes:
Related Issue:
This addresses a bug where the function would raise a NameError when called.
Testing:
The fix has been tested locally and resolves the import error.
Please review and let me know if any changes are needed.