Modified date is a standard feature in most blog engines.
Theme developer can use this date to show last updated time of an
article and enclose its value in `<time>` element.
We cannot use mtime of a file for modified_date because it is already
used for date metadata.
Secondly, a file mtime can be affected in a lot many ways, for example,
a sync service can change it, which will be incorrect to show as last
updated time of an article.
This adds a line to the settings file generated by pelican-quickstart
that ensures the automatically-generated "content" directory is
specified in said settings file. Fixes#1116
Folks keep running into this error, which probably signals a need to
change this behavior. After all, it wouldn't be hard for us to detect
what's going on and provide a better error message, such as: "It looks
like you're trying to process Markdown, but the Markdown library is not
currently installed. Please install the Python-Markdown library via 'pip
install markdown'."
Until we implement something akin to the above, this should serve as a
slightly-improved FAQ entry in the interim.
Since built-in exception "StandardError" does not exist in the latest python version (at least in version 3.3), use RuntimeError instead (which exists from python2.6 to python3.4)
smartypants is now py3 compatible but the default settings for double quotes has
been changed (http://pythonhosted.org/smartypants/changes.html).
This commit:
- update the typogrify test (change quotes, and add more test casesi: caps word,
ellipsis)
- install typogrify on travis
- uses upstream version of smartypants in tox instead of dmdm's fork for py3
It appears that BSD sed, unlike Linux, has a requirement that you
provide an extension to the -i option. So, while Linux allows:
sed -i "sed-command"
... to edit in-place, the BSD variant needs to have:
sed -i "" "sed-command"
i.e., with an empty backup suffix.
There are currently some minor problems when running tox that are not
present when running "python -m unittest discover". Once those problems
have been resolved, we should probably change this setting back to tox.
