Blogofile 0.8b1 Released

[Doug Latornell]

I'm happy to announce the release of Blogofile 0.8b1 and blogofile_blog 0.8b1.

What's Changed?


* Blogofile is now the static site builder that has always been at the core of the Blogofile project. blogofile_blog is a Blogofile plugin that provides templates, controllers, and filters (and even some sample posts) to use Blogofile to create a simple HTML5Boilerplate_ based blog.

* The codebase has been unified for Python 2.6, 2.7 and 3.2 (no 2to3 or 3to2 conversion required).

* The documentation source files have been moved into the project repository. They are built and rendered at http://docs.blogofile.com/ thanks to the readthedocs.org service.

* The ``init`` sub-command syntax and functionality have changed; see ``blogofile help init``.

* The configuration system has been refactored. The default configuration settings are now in the default_config.py module.

* As a result of the refactoring of the initialization function, and the configuration system, the site_init directory has been eliminated.

* There is improved Unicode handling in slugs, thanks to Wasil Sergejczyk.

* The command line completion feature has been removed.

The plugin interface isn't all that it needs to be yet, so you need to install both Blogofile and blogofile_blog, in that order. You can use pip, easy_install, or download the tarballs from PyPI or crate.io and use python setup.py.

There are more details about the changes in this release, and plans for the future in the release announcement blog post at http://www.blogofile.com/blog/2012/10/13/blogofile-0-8b1-release/

One of the reasons that this is a beta release is that I don't have a good handle on what it takes to migrate a 0.7 Blogofile site to 0.8. I would really appreciate it if some of you who are using 0.7 or 0.7.1 could please try out 0.8b1 and tell the community how you migrated your site. You can reply here, or start a new thread, leave a comment on the release announcement post, or you can clone the GitHub repo, add to the Migrating Sites from 0.7.x to 0.8 section of the docs, or add a migration helper script to the converters/ directory, and send a pull request.

Finally, I'd like to thank Ryan for creating Blogofile, and for his support of my efforts to move it forward. Thanks also to the community for you patience as 0.8 took shape, and to the many of you who have contributed bug reports, pull requests, and discussion and answers on the mailing list.

[Mike Pirnat]

Congrats and thanks for all of your hard work to move this forward! I
hope I'll be able to try a conversion from 0.7 soon...

--
"I am a leaf on the wind; watch how I soar..."

[Michael Bayer]

On Saturday, October 13, 2012 9:27:20 PM UTC-4, Doug Latornell wrote:

I'm happy to announce the release of Blogofile 0.8b1 and blogofile_blog 0.8b1.

this is fantastic news, thanks for all your efforts here!   I'll try to get some time to test out 0.8.

 

[Viktor Haag]

Congratulations on this major release!

I have one small question: is there a reason that you're pinning a dependency to pytz-2012d, and not the most recent version? pytz-2012f (at least) seems to now be available...

--

v

[Viktor Haag]

Hmmm -- you also seem to have dependencies upon six 1.1.0 (1.2.0 available) and textile 2.1.4 (2.1.5 available) as well.

Are these intentional single-version dependencies?

Thanks!

[Doug Latornell]

The install dependencies come from the pip freeze generated requirements file requirements/production.txt. I updated it a few weeks ago to reflect the current releases of all of the dependencies, but obviously pytz and six have done releases since then.

Textile is a little more complicated. It's 2.1.5 release (and probably earlier ones) uses Unicode literals in a couple of places. That's okay for Python 2.6 and 2.7, but not for 3.2. (And just to add to the fun it's okay again for Python 3.3). Ryan ran textile-2.1.4 through 2to3 to create textile-2.1.4-py3k and that's what gets installed if you install Blogofile under Python 3.2. For consistency we install textile-2.1.4 for Python 2.6 & 2.7. I'd send a pull request to six-ify textile-2.1.5 upstream, but the GitHub repo linked from PyPI has disappeared.

As to whether pinning the dependencies is overly cautious, I don't know. I do it on most of the projects I work on because I've been burned in the past by breaking changes in packages several layers down in the dependency chain. I welcome opinions on whether or not the dependencies for Blogofile should be pinned, and I'll give the matter some more thought before the 0.8 final release.

--
You received this message because you are subscribed to the Google Groups "blogofile-discuss" group.

To view this discussion on the web visit https://groups.google.com/d/msg/blogofile-discuss/-/WdgNyLZqk4AJ.

To post to this group, send email to blogofil...@googlegroups.com.
To unsubscribe from this group, send email to blogofile-disc...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/blogofile-discuss?hl=en.

[Michael Bayer]

I'd pin as few of these as possible so to best support environments that already have newer versions of those libs installed.

also are all of "markdown", "texttile", "docutils" required at all times ?   what if I only use one of those markup formats ?   it might be nice to use late-imports for these.    I have a lot of experience with that if you need advice.

[Doug Latornell]

On Tue, Oct 16, 2012 at 9:09 AM, Michael Bayer <mik...@zzzcomputing.com> wrote:

I'd pin as few of these as possible so to best support environments that already have newer versions of those libs installed.

That is the direction my thinking was heading as I was replying to Viktor's question.

Cautious pinning makes sense the in the product deployment realm that I've been burned in when I haven't used it. But it's not really appropriate for the release of a frameworky-tooly thing like Blogofile - unless there is a specific incompatibility that has to be avoided.

also are all of "markdown", "texttile", "docutils" required at all times ?   what if I only use one of those markup formats ?   it might be nice to use late-imports for these.    I have a lot of experience with that if you need advice.

Good question. The same question applies to template libraries. Do you need Jinja2 installed if you only use Mako templates. I would probably look at this as a feature for 0.9. I welcome any pointers you can give though because, off the top of my head, I don't know how I would implement it.

[EJelome]

Thanks Doug! I really like blogofile's simplicity, much more when separate controllers and filters were introduced.

There's one thing that I'm sure is missing with the 'blogging' of blogofile. How I wish that tagging works like categories. Tagging has been part of the blog system and making it difficult to implement especially for non-programmers and python beginners alike will push them away.

I've found a tag cloud controller but it's created 2 years ago and is 0.7+ compatible, and it doesn't work in 0.8.

Again, thanks!

[Doug Latornell]

On Wed, Oct 17, 2012 at 4:20 AM, EJelome <eje...@gmail.com> wrote:

Thanks Doug! I really like blogofile's simplicity, much more when separate controllers and filters were introduced.

Glad you like it!

There's one thing that I'm sure is missing with the 'blogging' of blogofile. How I wish that tagging works like categories. Tagging has been part of the blog system and making it difficult to implement especially for non-programmers and python beginners alike will push them away.

I've found a tag cloud controller but it's created 2 years ago and is 0.7+ compatible, and it doesn't work in 0.8.

One way for you to get tagging on the development radar would be to open an issue at https://github.com/EnigmaCurry/blogofile_blog/issues Please add some details about what you have in mind, and include a link to the code that you mentioned.

Again, thanks!

--
You received this message because you are subscribed to the Google Groups "blogofile-discuss" group.

To view this discussion on the web visit https://groups.google.com/d/msg/blogofile-discuss/-/jhk75kQVp9MJ.

[Davide Del Vento]

Congrats! However this release broke both
http://blogofile.readthedocs.org/en/0.7.1docs/quick_setup.html
and
http://blogofile.readthedocs.org/en/latest/quick_setup.html

The former can be fixed replacing the installation command with:

sudo pip install -I Blogofile==0.7.1

The latter I have no idea :-) I get the following error:

blogofile $ blogofile init mysite blog
blog plugin not installed; initialization aborted

installed plugins:
blogofile $

[Davide Del Vento]

Congrats! However this release broke both
http://blogofile.readthedocs.org/en/0.7.1docs/quick_setup.html
and
http://blogofile.readthedocs.org/en/latest/quick_setup.html

The former can be fixed replacing the installation command with:

sudo pip install -I Blogofile==0.7.1

The latter I have no idea :-) I get the following error:

blogofile $ blogofile init mysite blog
blog plugin not installed; initialization aborted

installed plugins:
blogofile $

In case anybody is still stuck on this error, you can fix it doing a:
git checkout 558444ca0064a4d78f291a2e25ecb73355e0bb89

(I know both fixes are pretty simple, but worth mentioning in the 0.7 docs)