ElasticSearch 1.0, TokuMX 1.4, Plan 9 GPLv2’d and Python 3.4RC1 – Snippets


ElasticSearch 1.0 springs out: The search-oriented NoSQL database, built upon Lucene, ElasticSearch has hit version 1.0. It’s a big release with a lot of changes and a lot of new features – an API for selective snapshot/restore, federated search, aggregation, distributed percolation and software “circuit breakers” to stop some more dangerous actions from overwhelming the system. An interesting post from Found.no on ElasticSearch sums up the pros and cons (like no authentication or authorisation) places ElasticSearch in the domain of “secondary store” to be used alongside a primary database.

TokuMX 1.4: Tokutek’s “MongoDB-with-Toku-engine”, TokuMX, has hit version 1.4 and is addressing the performance of sharding and replication. Toku’s engine is reputed to be very good for particular use cases and it’s interesting to see alternative storage engines under the MongoDB infrastructure.

Plan 9 goes GPL2: It’s been a long time under a open source (but unblessed-by-the-FSF) licence, but the venerable and inspiring Plan 9 has not been relicensed (mostly) under the GPLv2. In an announcement. It can be downloaded from the Akaros project (or cloned from the GitHub repo) which seems to be breeding Inferno/Plan 9 with their own many-core large-smp research.

Python 3.4 on final approach: Out of beta and hitting release candidate a few days ago, Python 3.4 is now imminent. It’s expected to land just over a month from now on March 16. Check back to our coverage of the last beta for more details of what’s coming.

Python 3.4 Betas and 3.3.4 RCs, UEFI bootsplaining and Bro pages – Snippets


Python 3.4’s last beta: Over the weekend, the last beta of Python 3.4 arrived. With two more release candidates and a final date of March 16, those interested should be testing now. The time scale was bumped by three weeks to allow last minute changes to the Argument Clinic, a DSL for parsing arguments, to settle in.

What’s also in 3.4? A new pathlib module, standardised enums, better object finalisation semantics, a C API for custom memory allocators, non-inheriting subprocess file descriptors, new statistics, asyncio and tracemalloc modules, a new hash algorithm for strings and binary data and better pickling. And of course, standardised use up “pip” as the package manager.

At this point, 5 Python Enhancement Proposals didn’t make the 3.4 cut – improved time zone database support and zip application support, the locallookup metaclass method, more unpacking generalisations and a key transforming dictionary are all pushed to after 3.4. For more details on whats in and out, check out the release schedule and the download page for 3.4 beta 3.

Python 3.3.4’s RC: There’s also a release candidate now available for Python 3.3.4 – details of fixes in the change log for that. Thats due for a final release on February 9, so not much time for final testing of the large wedge of fixes.

All About UEFI: There’s a lot of controversy, mostly unecessary or ill-informed, about UEFI’s boot process mainly down to it being confused with the optional SecureBoot element of UEFI that Microsoft lean on for validation. Adam Williamson, by day Red Hat Fedora QA, by night massive essay writer, has produced a huge and useful essay on what and how UEFI does its thing and the things it enables called UEFI Boot: How does that actually work then. Well worth a read.

Good idea, bad name: A shortened man page which just gives you examples? Sounds like a great idea. With a central repository for new pages? Excellent. And cross platform and packaged like a ‘gem’? Still with you. And you’re calling them “bro” pages. Oh, ah… this won’t end well. But good idea.