Other articles


  1. Pelican's Unified Codebase

    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 ...

    read more
  2. Pelican 3.1 released

    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 ...

    read more

Page 1 / 2 »

blogroll

follow