new_post: log .meta path only when it exists (fix #3731) #3843
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.
Pull Request Checklist
AUTHORS.txt
andCHANGES.txt
.flake8 nikola tests
andpydocstyle …
— no new warnings.nikola init -qd demosite && nikola build
) and testednikola new_post
in the scenarios below.Description — fix #3731
nikola new_post --import
printed a misleading line about a “metadata” file even when the post was created in one‑file mode (or when the.meta
file did not actually exist).This tiny patch:
exists_txt
,exists_meta
).meta
path only if it really existsflake8
/pydocstyle
No functional changes beyond quieter, more accurate logging.
Testing
nikola new_post --title "X" --import foo.rst
(new title)--twofile
Everything behaves as described, both with
ONE_FILE_POSTS = True
andFalse
.