Pelican Development Blog

Pelican 4.1 released

2019-07-14T00:00:00+02:00

Pelican 4.1 has been released and includes the following enhancements, fixes, and tweaks:

Live browser reload upon changed files (provided via Invoke task)
Add pyproject.toml, managed by Poetry
Support for invoking python -m pelican
Add relative source path attribute to content
Allow directories in EXTRA_PATH_METADATA
Add all_articles variable to period pages (for recent posts functionality)
Improve debug mode output
Remove blank or duplicate summaries from Atom feed
Fix bugs in pagination, pelican-import, pelican-quickstart, and feed importer

For more info, please refer to the release page or the Release History section of the documentation. For a more comprehensive list of changes, please review the respective milestone for this release. For the full list of changes, see: https://github.com/getpelican/pelican/compare/4.0.1...4.1.0

As always, we do everything we can to maximize backwards compatibility and ensure smooth Pelican upgrades. If you run into problems, please see the How to Get Help section of the documentation, and we will update this post with any upgrade tips contributed by the Pelican community.

Pelican 4.0 released

2018-11-13T00:00:00+01:00

Pelican 4.0 has been released, including many enhancements, fixes, and tweaks. Highlights include:

Replace develop_server.sh script with pelican --listen
Improved copy/link behavior for large static files (e.g., videos)
New {static} syntax to link to static content
Pages can now have draft status
Show current settings via new --print-settings flag
Replace Fabric’s fabfile.py with Invoke’s task.py
Importer improvements

Upgrading from previous releases

You may see deprecation warnings for certain settings. If that occurs, please change the specified setting to the new setting mentioned in the deprecation message.

Due to Python-Markdown changes, Markdown users must ensure they are using version < 3.0 or >= 3.1 to ensure proper rendering of code blocks.

Some user-submitted themes use positional argument formatting on object-related feed URLs, which will cause sites to fail to build with: "TypeError: not all arguments converted during string formatting". In that case, the theme needs to be updated. For example, substitute TAG_FEED_ATOM|format(tag.slug) with TAG_FEED_ATOM.format(slug=tag.slug). Affected variables include:

CATEGORY_FEED_ATOM
CATEGORY_FEED_ATOM_URL
CATEGORY_FEED_RSS
CATEGORY_FEED_RSS_URL
AUTHOR_FEED_ATOM
AUTHOR_FEED_ATOM_URL
AUTHOR_FEED_RSS
AUTHOR_FEED_RSS_URL
TAG_FEED_ATOM
TAG_FEED_ATOM_URL
TAG_FEED_RSS

Pelican 3.7 released

2016-12-12T00:00:00+01:00

Pelican 3.7 has been released, incorporating a year and a half worth of enhancements and bug fixes.

To see highlights, please refer to the release page or the Release History section of the documentation. For a more comprehensive list of changes, please review the respective milestone for this release. For the full list of changes, see: https://github.com/getpelican/pelican/compare/3.6.3...3.7.0

Upgrading from previous releases

Unlike Atom, the RSS feed specification does not contain a <content> field and only contains a <summary> field. Pelican previously put the full content in this field, which could cause odd behavior in feed readers that only expected a summary. For this reason, RSS feeds in Pelican 3.7 will by default only contain article summaries. To revert to the previous full-content behavior, either use Atom (which supports both <summary> and <content> fields) or set: RSS_FEED_SUMMARY_ONLY = False

If you have defined MD_EXTENSIONS in your settings file, you will see deprecation warnings since that setting has been replaced by the MARKDOWN setting in Pelican 3.7. Refer to the corresponding entry in the Settings documentation to see the new default value and replace any existing MD_EXTENSIONS settings with your preferred customized variation of the MARKDOWN setting.

Themes originally had access to two identical context variables: PAGES and pages. This redundancy was removed in Pelican 3.7, so any themes that use PAGES will need to be updated to use pages instead.

JINJA_EXTENSIONS has been replaced by the JINJA_ENVIRONMENT setting. Any plugins that refer to the former setting will need to be updated. Refer to the corresponding entry in the Settings documentation for more information.

Pelican 3.6 released

2015-06-15T00:00:00+02:00

Pelican 3.6 has been released. Highlights of the improvements contained in this release follow below.

For those who are new to Pelican, please refer to the Quickstart Guide. There is also a Tutorials page available, which also includes a link to a Pelican installation screencast.

Highlights

Disable caching by default in order to prevent potential confusion
Improve caching behavior, replacing pickle with cpickle
Allow Markdown or reST content in metadata fields other than summary
Support semicolon-separated author/tag lists
Improve flexibility of article sorting
Add --relative-urls argument
Support devserver listening on addresses other than localhost
Unify HTTP server handlers to pelican.server throughout
Handle intra-site links to draft posts
Move tag_cloud from core to plugin
Load default theme's external resources via HTTPS
Import drafts from WordPress XML
Improve support for Windows users
Enhance logging and test suite
Clean up and refactor codebase
New signals: all_generators_finalized and page_writer_finalized

For a full list of changes, see: https://github.com/getpelican/pelican/compare/3.5.0...3.6.0

Upgrading from previous releases

Content generation caching is now disabled by default. If you have a large site with many articles/pages and notice that site generation takes longer than you would prefer, follow these two steps:

Delete the cache folder, if it exists

Add the following to your settings file:

CACHE_CONTENT = True
LOAD_CONTENT_CACHE = True

While we do everything we can to maximize backwards compatibility and ensure smooth Pelican upgrades, it's possible that you may encounter un-anticipated wrinkles. If you run into problems, please see the How to Get Help section of the documentation, and we will update this post with any upgrade tips contributed by the Pelican community.

Pelican 3.5 released

2014-11-20T00:00:00+01:00

Today we are pleased to announce the release of Pelican 3.5. Highlights of the improvements contained in this release follow below.

For those who are new to Pelican, please refer to the Quickstart Guide. There is also a Tutorials page available, which currently includes a link to a Pelican installation screencast.

Highlights

Introduce ARTICLE_ORDER_BY and PAGE_ORDER_BY settings to control the order of articles and pages.
Include time zone information in dates rendered in templates.
Expose the reader name in the metadata for articles and pages.
Allow storing static files in the same directory as content source files, without causing the raw content sources to be published.
Introduce the {attach} internal link syntax for placing a static file in the same output directory as the document that links to it.
Prevent Pelican from raising an exception when there are duplicate pieces of metadata in a Markdown file.
Introduce the TYPOGRIFY_IGNORE_TAGS setting to add HTML tags to be ignored by Typogrify.
Add the ability to use - in date formats to strip leading zeros. For example, %-d/%-m/%y will now result in the date 9/8/12.
Ensure feed generation is correctly disabled during quickstart configuration.
Fix PAGE_EXCLUDES and ARTICLE_EXCLUDES from incorrectly matching sub-directories.
Introduce STATIC_EXCLUDE setting to add static file excludes.
Fix an issue when using PAGINATION_PATTERNS while RELATIVE_URLS is enabled.
Fix feed generation causing links to use the wrong language for month names when using other locales.
Fix an issue where the authors list in the simple template wasn't correctly formatted.
Fix an issue when parsing non-string URLs from settings.
Improve consistency of debug and warning messages.

For a full list of changes, see: https://github.com/getpelican/pelican/compare/3.4.0...3.5.0

Upgrading from previous releases

While we do everything we can to maximize backwards compatibility and ensure smooth Pelican upgrades, it's possible that you may encounter un-anticipated wrinkles. If you run into problems, please reach out via the #pelican channel on IRC, and we will update this post with any upgrade tips contributed by the Pelican community.

Pelican 3.4 released

2014-07-01T00:00:00+02:00

Today we are pleased to announce the release of Pelican 3.4, which is one of the more significant updates Pelican has ever seen. Take a look at the changelog and the Pelican 3.4 milestone issues list to see all the features, fixes, and miscellaneous improvements that are included in this release.

Major highlights

Faster rebuild times

Thanks to a new caching mechanism and selective output writing, rebuilding a site can take just a few seconds. Tinkering with posts and themes is now even easier.

Fixed locale and encoding issues

Finally URLs can include, for example, localized month names.

Improved documentation, both in style and content

The documentation has been ported to the new ReadTheDocs theme, including a functional search bar and a navigation side panel. A quickstart section is now provided to jump-start your Pelican experience.

Support for multiple post authors

The new :authors: metadata field makes it possible to easily manage multi-user sites.

Upgrading from previous releases

While we do everything we can to maximize backwards compatibility and ensure smooth Pelican upgrades, it's possible that you may encounter un-anticipated wrinkles. If you run into problems, please reach out via the #pelican channel on IRC, and we will update this post with any upgrade tips contributed by the Pelican community.

I18N Subsites plugin released

2014-02-05T00:00:00+01:00

Pelican has supported article and page translations since version 2.6. However, this functionality does not include translations of themes or the site name, something many have asked for.

The new I18N Subsites plugin makes it simple to:

override settings for each language, e.g. SITENAME or MENUITEMS
translate and localize themes using jinja2.ext.i18n
automatically create translated subsites such as http://example.com/fr/

The new plugin is available in the Pelican plugin repository.

A demo site has been put up to showcase the plugin. You can use the demo site source as a reference for using the plugin in your own site.

Although this plugin has been tested, it is quite possible that you will find some bugs or inconvenient behavior as it is very new. Do not hesitate to file an issue!

Finally, I would like to thank the Pelican developers for implementing and designing Pelican so well that making this plugin was straightforward, fast, and fun.

Pelican 3.3 released

2013-09-24T00:00:00+02:00

Today we are pleased to announce the release of Pelican 3.3. Highlights of the improvements contained in this release follow below.

For those who are new to Pelican, please refer to the Getting Started Guide. There is also a Tutorials page available, which currently includes a link to a Pelican installation screencast.

Highlights

Python 3.3 support

Following up on the last release's support for Python 3.2, this new version of Pelican now supports Python 3.3. In order to do so, support for Python 3.2 unfortunately had to be dropped.

Cross-platform automation via Fabric

Pelican has traditionally included a make-based workflow that works well enough for POSIX-based systems but at the expense of Windows users. In order to improve cross-platform publishing automation, Pelican 3.3 includes support for Fabric, a Python-based automation framework.

Retain certain files in output

Some folks apply version control to their output directories, the metadata for which is obliterated when using the DELETE_OUTPUT_DIRECTORY directive. Pelican 3.3 includes a new OUTPUT_RETENTION setting which allows you to define arbitrary files/folders that should be retained during the aforementioned output cleaning process (e.g., .hg, .git, et cetera).

Tumblr import

Tumblr posts can now be imported into Pelican sites.

Refactoring, fixes, and improvements

Pelican 3.3 includes a significant number of other improvements, as indicated by the long list of items in the changelog and the Pelican 3.3 milestone issues list.

Upgrade notes

While we do everything we can to maximize backwards compatibility and ensure smooth Pelican upgrades, it's possible that you may encounter un-anticipated wrinkles. Following are a few notes that may help:

The FILES_TO_COPY setting has been deprecated, so replace it with the STATIC_PATHS and EXTRA_PATH_METADATA settings. Refer to the corresponding entries in the Settings section of the docs for more information.
Due to minor changes to the plugin API, some plugins may not function properly if they are not updated accordingly. Most (if not all) of the plugins in the official Pelican Plugins Repository have already been updated, but externally-hosted plugins may not be. If you are heavily dependent on such a plugin, consider holding off on upgrading to Pelican 3.3 until you are certain that your desired plugins will function correctly.
PDF generation has been moved out of core and into a separate plugin. If you previously relied on this feature, please be sure to retrieve, install, and configure the new plugin from the Pelican Plugins Repository.
There is a new warning for <img> tags without alt="" attributes, which are important for accessibility reasons. Please consider adding these attributes to your <img> tags in order to improve accessibility (and eliminate the warnings).
The syntax for linking to source content has been changed in order to ensure compatibility with Markdown and reST extensions. For example, the new syntax for Markdown: [a link relative to content root]({filename}/article1.md) The previous |filename|/article1.md syntax will continue to be supported for backwards compatibility.

We will keep the above list updated with any additional items as we find them, so please let us know if we missed anything.

Using Pelican with Heroku

2013-07-25T00:00:00+02:00

Using Pelican with Heroku couldn't be easier. We have recently been working on a buildpack allowing you to publish your Pelican site directly to Heroku.

This allows you to host your Pelican site on the Heroku platform with very little effort. Simply create a Heroku application and push your repository to it.

You don't need to deal with generating the HTML with the Pelican command — the buildpack takes care of this. Just push a git repository with the pelicanconf.py file in the root directory.

To enable the Heroku buildpack for existing sites, run:

heroku buildpacks:set https://github.com/getpelican/heroku-buildpack-pelican

Alternatively, for those of you switching to Heroku, you can use the following command to create your Pelican site on Heroku.

heroku create myapp --buildpack https://github.com/getpelican/heroku-buildpack-pelican

Pelican 3.2 released

2013-04-24T00:00:00+02:00

Today we are pleased to announce the release of Pelican 3.2. Highlights of the improvements contained in this release follow below.

For those who are new to Pelican, please refer to the Getting Started Guide. There is also a Tutorials page available, which currently includes a link to a Pelican installation screencast.

Highlights

Python 3 support

As noted in Pelican's Unified Codebase, this new version of Pelican includes support for Python 3. All tests currently pass on Python 3.2, and we expect the same for Python 3.3 in the near future. (Pelican interacts with a number of third-party components that have not yet been fully updated for Python 3.3 compatibility.)

Override page save-to location from meta-data

Instead of blog or a site with dated articles, some people want to use Pelican to publish sites with non-chronological content. Pelican 3.2 enables this by providing a way to override the save-to location from within a page's meta-data, so for example, you can have a pages/index.md file that will replace your site root's index.html.

Time period archives

For folks who use date-based URL schemes such as /2013/04/23/my-post/, you can now create per-year and per-month archives that will appear at /2013/ and /2013/04/, respectively.

Posterous blog import

With Posterous shutting down on April 30th, this release offers the timely ability to import an existing Posterous blog. There are only a few days remaining, so if you have a Posterous blog and want to import it into a Pelican-powered site, please act quickly!

Separate Pelican plugins repository

Pelican plugins have been moved out of the core Pelican repository and into their own repository. This allows us to focus on the Pelican core while simultaneously encouraging the community to extend Pelican's functionality in the form of modular plugins.

Refactoring, fixes, and improvements

There have been a large number of improvements under the hood. While not an exhaustive list, the Pelican 3.2 milestone issues should provide a good overview of the many enhancements that are part of this release.

Upgrade notes

Add from __future__ import unicode_literals near the top of your settings file.
As noted above, Pelican plugins are now located in their own repository. If you currently use any plugins bundled with Pelican 3.1.1 or earlier, you should follow the instructions located in the Pelican plugins repository to re-enable those plugins.
Document-relative URL generation is now off by default. If you previously relied on this feature and fully understand its potential disadvantages, you can re-enable it by adding RELATIVE_URLS = True to your settings file.
The CSS class generated by the reST and Markdown processors was unified into a single highlight class. If you find that your code syntax highlighting has disappeared after upgrading, ensure that any instances of codehilite in your CSS are replaced with highlight.
Support for Python 2.6 has been dropped as of Pelican 3.2. For those running on distros that do not have a more recent version of Python available, one possible solution is to compile Python 2.7.x and use it from within a virtualenv (e.g., via virtualenv -p $HOME/bin/python2.7 pelican).

We will keep the above list updated with any additional items as we find them.

Special thanks

As evidenced by our growing THANKS file, there were many people who contributed to this release. A few folks deserve special mention for the many hours they put into this new version of Pelican:

Dirk Makowski added support for Python 3, including provisional ports for third-party components such as Typogrify and SmartyPants.

W. Trevor King has undertaken a significant refactoring of the Pelican core, improving a wide swath of the codebase that will continue to surface in future versions of Pelican.

Deniz Turgut (Avaris) contributed so many features and fixes to this release that it would be silly to even try to list them. He's put so much work into Pelican that one of the maintainers insisted that he set up a Gittip profile (which Deniz did under much duress), to which an anonymous donor has already made a sizeable contribution. If you want to thank Deniz for his hard work, please consider doing the same. It would be great to see him on the "Top Receivers" list next week!

Staying in touch

2013 has been a busy year so far, as evidenced by both the number of commits to Pelican as well as the lack of updates here on the Pelican blog. (^_^) We'll do our best to post more frequently in the months to come, both here on the blog and also via the @getpelican Twitter account.

Pelican's Unified Codebase

2013-04-16T00:00:00+02:00

In this post by Dirk Makowski, he explains how he added preliminary Python 3.x support to the forthcoming Pelican 3.2 release.

When referring to Pelican's "unified" codebase, this means the code runs without changes (or requiring 2to3) on both Python 2.x and 3.x. Specifically, this unified codebase is tested on Python 2.7 and 3.2.

At the time of this writing all tests pass, whether manually invoked via python -m unittest discover within manually-created virtual environments or via tox, which automatically creates virtual environments for Python 2.7 and 3.2 and runs tests on both Python versions:

74 tests, 9 skips, no errors

During my first attempt to port Pelican to Python 3, I had used 2to3 and manually applied corrections to achieve syntactical correctness. But as the tests showed, more subtle bugs in the encoding of strings remained (e.g. outputting b'...' instead of '...'). Also, the code was suitable for Python 3 only and would not run properly on Python 2.

Building on the lessons learned with 2to3, the current in-development version of Pelican now provides a single codebase for Python 2 and 3. The following section lists some hints about what had to be changed in order to achieve this. These hints may also be valuable for anyone who wants to contribute new Pelican features or bug fixes, since all Pelican code submissions must now run on both Python versions.

Unification

Assume every string and literal is Unicode (import unicode_literals):
- Do not use prefix u'.
- Do not encode/decode strings in the middle. Follow the code to the source (or target) of a string and encode/decode at the first/last possible point.
- In other words, write your functions to expect and to return Unicode.
- Encode/decode strings if the source is a Python function that is known to handle this badly, e.g., strftime() in Python 2.
Use new syntax: print function, "except ... as e" (not comma) etc.
Refactor method calls like dict.iteritems(), xrange() etc. in a way that runs without code change in both Python versions.
Do not use magic method __unicode()__ in new classes. Use only __str()__ and decorate the class with @python_2_unicode_compatible.
Do not start int literals with a zero. This is a syntax error in Py3k.
Unfortunately I did not find an octal notation that is valid in both Pythons. Use decimal instead.
use six, e.g.:
- isinstance(.., basestring) -> isinstance(.., six.string_types)
- isinstance(.., unicode) -> isinstance(.., six.text_type)
setlocale() in Python 2 bails when we give the locale name as Unicode, and since we are using from __future__ import unicode_literals, we do that everywhere! As a workaround, I enclosed the localename with str(); in Python 2 this casts the name to a byte string, and in Python 3 this should do nothing, because the locale name is already in Unicode.
Kept range() almost everywhere as-is (2to3 suggests list(range())) — just changed it where I felt necessary.
Changed xrange() back to range(), so it is valid in both Python versions.

About External Libraries

Core

Pelican core depends on feedgenerator. To run on Py3k, you will need feedgenerator 1.5, which also now has a unified codebase and is available on PyPI.

BeautifulSoup had to be upgraded to bs4 (only bs4 supports Py3k), which has some consequences:

To parse XML (e.g., which the WordPress importer does), the lxml package is now required.
bs4 does not have convertEntities anymore.

Plugins

On Python 2 you still can use all plugins and their dependencies as they are. But if you want to use Pelican plugins on Python 3, you must seek out and install compatible packages yourself.

For Typogrify and SmartyPants, on which Typogrify depends, I provide ready-made 2to3'd code:

For webassets, I also have 2to3'd code available:

https://github.com/dmdm/webassets/tree/py3k

But webassets still has issues. One is that the less-css compiler is not correctly invoked when I build the blog (e.g., with make html); I have to manually invoke the compiler afterwards:

lessc themes/pymblog/static/less/pymblog.less > output/theme/css/pymblog.css

Be aware that the 2to3'd code of aforementioned libraries runs on Python 3 only.

Testing

Testing on Python 2 is straightforward.

On Python 3, if you have installed the Python 3.x-compatible versions of the plugins, like shown in the previous chapter, manual testing with python -m unittest discover is also straightforward.

However, you must tell tox to use those Py3k libraries. If you forget this, tox will pull the regular packages from PyPI and the tests will fail.

Tell tox about the local packages thusly: enter the source directory of SmartyPants and run tox there. Do this again for Typogrify and webassets. SmartyPants and Typogrify do not have real tests, and webassets will fail noisily, but as a result we get these libraries neatly packaged in tox's distshare directory. And this is what we need to order to run tox for Pelican.

See also the comments in tox.ini for more detail.

Pelican 3.1 released

2012-12-03T00:00:00+01:00

Pelican development has progressed steadily over the last few months, and we're pleased to announce the release of version 3.1, which can be obtained via Crate.io or GitHub. This release contains some exciting new features; following is a summary of changes since the last 3.0.1 release.

Easier intra-site linking

Whether linking from one post to another or including locally-hosted images on a page, linking to intra-site resources has been significantly enhanced. In addition to improving reliability, it's now possible to link to a resource in your source content hierarchy instead of the generated hierarchy.

Find more information here: http://docs.getpelican.com/en/3.1.1/getting_started.html#linking-to-internal-content

Metadata extraction from filename

There is a new FILENAME_METADATA setting that adds support for metadata extraction from the filename via regular expressions. For example, if you would like to extract both the date and the post slug from the filename, you could set your FILENAME_METADATA setting to something like: '(?P<date>\d{4}-\d{2}-\d{2})_(?P<slug>.*)'

Web asset processing moved to separate plugin

We are trying to move non-essential features out of the Pelican core and instead make them available as plugins. Web asset management is an example of this effort — we don't think this is a core component of Pelican, but it's still a useful feature and remains available to those who want to use it.

New gzip cache plugin

The gzip cache plugin allows generated text files to be compressed once during site generation and thus served without needing any server-side compression. This obviates the need for the web server to compress these text files on-the-fly, which can result in lower web server CPU utilization.

Basic functional tests restored

We now have a way to fully test Pelican's output, which helps us understand whether code changes break Pelican's intended behavior (for developers and for end users) while we are developing new features.

Template pages

If you want to generate custom pages besides your blog entries, you can use any Jinja template file with a path pointing to the file and the destination path for the generated file. For instance, if you have a blog with three static pages — a list of books, your resume, and a contact page — you could set them up via:

TEMPLATE_PAGES = {'src/books.html': 'dest/books.html',
                  'src/resume.html': 'dest/resume.html',
                  'src/contact.html': 'dest/contact.html'}

Feed improvements

The FEED_ALL_ATOM and FEED_ALL_RSS directives have been introduced as distinct from their FEED_ATOM and FEED_RSS brethren. The former show entries in all available language translations, while the latter only include entries written in the site's primary language.

Use folders as category

Until now, Pelican made the assumption that the folders used to organize your content should be used as the respective categories of the articles contained within. You now can configure this behavior via the USE_FOLDER_AS_CATEGORY setting.

New signals

Plugins now have additional signals at their disposal:

We now provide a generator_init signal that is sent when the generator is initialized. You'll receive the generator as an argument.
get_generators is invoked in Pelican.get_generator_classes and can return a Generator or several generators in a tuple or list. This is useful when you want to add your own generators.
article_generate_preread is invoked before an article is read in ArticlesGenerator.generate_context. Use this if the code needs to do something before every article is parsed.

Minor enhancements and fixes

Empty value for the AUTHOR setting is now allowed
Improved WordPress importing
Generated content doesn't contain as much blank lines as it did previously
New icon for Google+ and improvements to many others
Many small documentation and bug fixes not described here

On the horizon

We are working on moving plugins out of the main Pelican repository and into a separate repository.
We would like to implement measures designed to speed up site generation in order to reduce processing time.
In order to provide more regular updates on development progress, we intend to publish blog posts on a more frequent basis.

That's all for now. More to come soon! :-)

Pelican 3.0 released

2012-08-08T00:00:00+02:00

Today marks the release of Pelican 3.0! Some of the new features include:

Improved URL structure flexibility
Support for Typogrify
Support for LESS CSS
New development server script for previewing auto-regenerated changes
Improved recognition of alternate content filename extensions
... and much more!

Feel free to check out the package listing on PyPI or the project source at GitHub. If you want to give Pelican a spin, check out the Getting Started section of the Pelican Documentation.

Thanks to all the folks who helped out with testing, reporting bugs, fixing bugs, contributing features, and improving the documentation. Pelican's third major release would not be the same without you!

Pelican now has a blog of its own!

2012-07-23T00:00:00+02:00

Since Alexis started working on the project almost two years ago, a bunch of happy hackers have joined the effort to make Pelican an even better tool. Among these contributors are Kyle, Justin, and tBunnyMan, all of whom have done an amazing job recently.

We thought having a project blog would be a good way to keep users and developers updated on the status of Pelican's development.

We have version 3.0 coming soon with a lot of niceties that will hopefully be ready by the end of the week. Kyle is working on Py3k support for integration after 3.0, and we are getting rid of old things that don't make sense anymore for 3.0, so expect some changes. :)