3.0.1 3.2-series add_multi_theme_support cache-readers caching_warning content-written-signal faq_index_save_as fix-1493 master multiple-authors static_symlink_1042
Nothing to show
Commits on Sep 9, 2013
Commits on Sep 8, 2013
This question comes up on IRC quite frequently.
I have added reference to "Linking to internal content" section because without it, it is difficult to explain the usage. I have also updated changelog. Closes getpelican/pelican#1061
Commits on Aug 29, 2013
Commits on Aug 10, 2013
`get_instance()` returns two values. Old code, instead of unpacking two values in two variables, placed the tuple in a single variable `pelican`. Later in the same block when `pelican.run()` was called, it resulted in error. ``` -> Modified: content, theme, settings. re-generating... CRITICAL: ("'tuple' object has no attribute 'run'",) CRITICAL: 'tuple' object has no attribute 'run' Traceback (most recent call last): File "/Users/talha/Repos/VirtualEnvs/pelican-dev/bin/pelican", line 8, in <module> load_entry_point('pelican==3.3', 'console_scripts', 'pelican')() File "/Users/talha/Repos/VirtualEnvs/pelican-dev/lib/python2.7/site-packages/pelican-3.3-py2.7.egg/pelican/__init__.py", line 353, in main pelican.run() ``` Either the returned value should be unpacked properly or `pelican.run` should be called.
Commits on Mar 10, 2013
Mar 10, 2013
reST example of the section "Linking to internal content" had incorrect metadata. Moreover, time was missing from the date of both markdown and reST example. This was pointed out by [lefromage at #pelican](https://botbot.me/freenode/pelican/msg/2235275/)