What's new in 1.5.2 (December 2011)
===================================
Pertinent to users:
1. Fixed a warning that pops up when doing ``pip install pyblosxom``
2. Removed debug logging from pycategories
What's new in 1.5.1 (December 2011)
===================================
Pertinent to users:
-------------------
1. Fixed a problem with the manifest so ``python setup.py install``
works again.
2. Fixed the WHATSNEW so it shows correct version and date for
1.5 release.
What's new in 1.5 (December 2011)
=================================
Pertinent to users:
-------------------
1. Renamed the project from PyBlosxom to Pyblosxom (no more CamelCase).
2. I moved all the plugins again. This time, instead of being in
``plugins/``, they're now in ``Pyblosxom/plugins/``.
You no longer have to copy core plugins into your plugins
directory. Instead of copying core plugin files, refer to the
plugins in your ``config.py`` file using their full Python path in
the Pyblosxom package.
For example, the pycalendar plugin is now in
``Pyblosxom/plugins/pycalendar.py`` and thus its Pyblosxom
package path is ``Pyblosxom.plugins.pycalendar``. Your
``config.py`` file would look have this::
py["load_plugins"] = [
...
"Pyblosxom.plugins.pycalendar",
...
]
If you do this, then the next time you upgrade PyBlosxom, the
plugins will be upgraded automatically.
Further, documentation for plugins is at the top of the individual
plugin files, but also in the documentation. This includes a list
of the plugins available in the core.
.. only:: text
You can see the plugin documentation in docs/plugins/.
.. only:: html
You can see the plugin documentation at :ref:`part-two`.
3. Plugins added: markdown_parser, readmore
4. Plugins changed:
pages
* Fixed documentation and error messages for ``pagesdir``.
* Fixed frontpage checking. Should catch / as well as /index
now.
* Adds more examples to documentation.
tags
* Increased tag cloud range from 3 sizes to 5.
* Adds truncate support.
* Fixes problems with initialization when building tags so that
it initializes plugins allowing them to do startup things.
This fixes problems with plugins that augment entry parsers.
rst
* renamed it to rst_parser so it's clearer what it is
pycategories
* fixed category_start/category_begin behavior for root category
* fixed the first example of settings in the documentation
the rest of the plugins: pep8 fixes and documentation updates
5. Plugins removed from Pyblosxom: commentAPI
6. Fixes error handling for loading plugins. When doing
``pyblosxom-cmd test`` and a plugin fails to load, it'll now tell
you. When using the debug renderer and a plugin fails to load,
it'll now tell you.
7. Lot of work on simplifying and improving the documentation.
8. Added a ``static_yearindexes`` setting. Set it to True to generate
year indexes and False to not generate year indexes.
Pertinent to developers
-----------------------
1. I removed all the extra infrastructure for testing plugins.
Plugins that come with the core are now in the Pyblosxom package
and their tests are in ``Pyblosxom/tests/``.
2. Adds *generate* subcommand to pyblosxom-cmd. This makes it easier
to test blogs and plugins that do things with entries.
3. Renamed ``PyBlosxomWSGIApp`` class to ``PyblosxomWSGIApp``.
4. Renamed ``PyBlosxom`` class to ``Pyblosxom``.
5. Moved the project from gitorious to github. The new git repository
is at `<http://github.com/willkg/pyblosxom>`_.
6. Removed ``VERSION_DATE`` and ``VERSION_SPLIT``. They're kind of
silly and don't really help much.
I moved the version to ``Pyblosxom/_version.py``. Use it like
this::
from Pyblosxom import __version__
print __version__
I updated the documentation accordingly.
new major release, many changes, most notably:
-syntax scanner speed improvement
-UI and feature improvements
-new languages: Google Go, Vala and Ada
-zencoding support
Change from previous:
---------------------
20111025
- Do not add CA's only trusted for email and/or code signing (RT#70967)
(if you need that, please let us know and we can see about putting it
in as an option)
Changes from previous:
----------------------
0.15 2011-12-23 11:10:47 EST5EDT
Fixed:
- Repeated captures from a custom filehandle would return undef instead
of the empty string (and would warn). This has been fixed.
[rt.cpan.org #73374 part two. Thank you to Philipp Herz for help
in reproducing this bug.]
Other:
- Commented out debugging code for slightly less runtime overhead
0.14 2011-12-22 10:14:09 EST5EDT
Added:
- Capturing with custom filehandles will return only newly appended
output instead of everything already in the file.
[rt.cpan.org #73374]
0.13 2011-12-02 13:39:00 EST5EDT
Fixed:
- Fixed t/18-custom-capture.t failures on Windows due to tempfile
removal problems in the testfile
0.12 2011-12-01 16:58:05 EST5EDT
Added:
- New functions capture_stdout, capture_stderr, tee_stdout, tee_stderr
[rt.cpan.org #60515]
- Capture functions also returns the return values from the executed
coderef [rt.cpan.org #61794, adapted from patch by Christian Walde]
- Capture functions take optional custom filehandles for capturing
via named files instead of anonymous ones [inspired by Christian Walde]
Fixed:
- Tied filehandles based on Tie::StdHandle can now use the ":utf8"
layer; removed remaining TODO tests; adds Scalar::Util as a dependency
Changed:
- When Time::HiRes::usleep is available, tee operations will
sleep during the busy-loop waiting for tee processes to be ready
[rt.cpan.org #67858]
1.) Set minimum required GCC version to 4.1.3 because that is what has
been tested. Based on the bug-report it also seems that GCC 4.0.1
doesn't work.
2.) GCC 4.1.3 (as distributed with NetBSD 5.*) works fine under
NetBSD/macppc as reported by Matthias Kretschmer on IRCnet.
So don't insist on GCC 4.2.1 for this platform. This fixes seems
to fix the build as the GCC 4.4.6 package doesn't build for
this platform.
- add progress message for one more errno value (EAGAIN) in response to failed
mlock; BSDs use this to indicate the lock failed due to being over a system
or process limit, much like ENOMEM.
* Extensive, extensive unit test refactoring
* Convert the Docbook documentation to ReST
* Include the documentation in the source distribution
* Consolidate the disparate README files into one
* Support Jython somewhat (almost all unit tests pass)
* Support Python 3.2
* Fix Python 3 issues exposed by improved unit tests
* Fix international domain name issues exposed by improved unit tests
* Issue 148 (loose parser doesn't always return unicode strings)
* Issue 204 (FeedParserDict behavior should not be controlled by `assert`)
* Issue 247 (mssql date parser uses hardcoded tokyo timezone)
* Issue 249 (KeyboardInterrupt and SystemExit exceptions being caught)
* Issue 250 (`updated` can be a 9-tuple or a string, depending on context)
* Issue 252 (running setup.py in Python 3 fails due to missing sgmllib)
* Issue 253 (document that text/plain content isn't sanitized)
* Issue 260 (Python 3 doesn't decompress gzip'ed or deflate'd content)
* Issue 261 (popping from empty tag list)
* Issue 262 (docs are missing from distribution files)
* Issue 264 (vcard parser crashes on non-ascii characters)
* Issue 265 (http header comparisons are case sensitive)
* Issue 271 (monkey-patching sgmllib breaks other libraries)
* Issue 272 (can't pass bytes or str to `parse()` in Python 3)
* Issue 275 (`_parse_date()` doesn't catch OverflowError)
* Issue 276 (mutable types used as default values in `parse()`)
* Issue 277 (`python3 setup.py install` fails)
* Issue 281 (`_parse_date()` doesn't catch ValueError)
* Issue 282 (`_parse_date()` crashes when passed `None`)
* Issue 285 (crash on empty xmlns attribute)
* Issue 286 ('apos' character entity not handled properly)
* Issue 289 (add an option to disable microformat parsing)
* Issue 290 (Blogger's invalid img tags are unparseable)
* Issue 292 (atom id element not explicitly supported)
* Issue 294 ('categories' key exists but raises KeyError)
* Issue 297 (unresolvable external doctype causes crash)
* Issue 298 (nested nodes clobber actual values)
* Issue 300 (performance improvements)
* Issue 303 (unicode characters cause crash during relative uri resolution)
* Remove "Hot RSS" support since the format doesn't actually exist
* Remove the old feedparser.org website files from the source
* Remove the feedparser command line interface
* Remove the Zope interoperability hack
* Remove extraneous whitespace
