The Django web development framework has cranked out a second beta release on its way to the final 1.0 due in September. The latest release sees some welcome additions like a refactored comments application, rewritten documentation and the removal of some legacy code.
The leaner Django 1.0 beta 2 also marks the feature and string freezes, which means the only things left to do are bugs fixes and some more documentation improvements. For complete details on what beta 2 brings to the table, check out the release notes.
The Django Project has also announced a release party for Django 1.0. The party will coincide with the Django Conference, but unlike the conference, the party is open to anyone. The party will be at the Tied House in Mountain View on Saturday, September 6th at 7pm. The party looks like a nice way to catch some conference highlights:
To make the night extra fun, we’ll be holding “lightning talks” at the party — five minute presentations on various Django-related topics. We’ll be asking speakers at the conference to present vastly trimmed-down versions of their conference talks, and we’ll be opening the floor up to anyone to present their own cool shit.
The popular Django Project, a Python web-development framework, appears to be on track for its scheduled 1.0 release in September 2008. The Django Blog recently announced the release of Django 1.0 alpha 1, which includes all of the major features due land in the final Django 1.0.
There are a few minor things that haven’t been included, but the Django team reports that those lower-priority items will be added before before the 1.0 feature freeze.
While today’s release is an alpha and not meant to be used in production sites, if you’ve been itching to get your hands on the newforms Admin code, alpha 1 makes a good candidate for testing.
To grab a copy, head over to the downloads page, but make sure you read through the release notes and if you find bugs, report them so they can get fixed before the final release.
The next stop on the Django roadmap is the first beta, which is due to arrive August 5. In the mean time, if you’d like to learn a bit of Django, be sure to check out our ongoing Django tutorial series. The latest installment walks you through how to build urls and views.
Django, one of our favorite web frameworks, has announced a new Django Foundation designed to oversee the project similar to the way Mozilla and the Apache foundation work. The Django Foundation will also accept donations and pay individuals.
The founding board members of the foundation are Django’s co-creators Adrian Holovaty and Jacob Kaplan-Moss, as well as Dan Cox.
According the announcement, The foundation’s goals are to:
Support development of Django by sponsoring sprints, meetups, gatherings and community events.
Promote the use of Django among the world-wide Web development community.
Protect the intellectual property and the framework’s long-term viability.
Advance the state of the art in Web development.
This should be good news for Django developers since it puts a much stronger, uh, foundation in place and shows that Django is here to stay. It also creates a way for interested large companies to offer grant money to Django. Companies like IBM and Sun often give money to open-source foundations in an effort to speed development.
Perhaps even more exciting for Django fans though is news that roadmap to 1.0 has been announced. Although the developers caution that the date is subject to change, if all goes well Django should be have a 1.0 release in September 2008.
That means many long awaited improvements (like the newforms-admin branch) should be rolled into the Django trunk code relatively soon.
We’re currently hard at work on some tutorials guiding you through the Django development stack so stay tuned to the Webmonkey RSS feeds for more details and congratulations to the Django team on the new Foundation.
As part of its ongoing I/O developer event, Google has announced a pricing plan for those looking to build and host sites on the company’s App Engine platform.
Google App Engine, which allows developers to build and host Python-based web applications, is still in a testing phase, but when the service hits prime time later this year developers will be able to purchase additional storage space and bandwidth as needed.
Currently App Engine offers 500 MB of storage and enough CPU and bandwidth for about 5 million pageviews per month for free. Those numbers will remain unchanged, but if you need more storage and bandwidth you’ll be able to buy it.
The prices are roughly comparable to Amazon’s S3 service, here’s the breakdown from Google’s press release:
$0.10 – $0.12 per CPU core-hour
$0.15 – $0.18 per GB-month of storage
$0.11 – $0.13 per GB outgoing bandwidth
$0.09 – $0.11 per GB incoming bandwidth
Perhaps more interesting for developers is the announcement of two new App Engine APIs. One allows for image manipulation (crop, scale, rotate, etc) and the other puts the memcached cache engine at your disposal.
Given that App Engine is written in Python using the Django framework, it seems likely that the image API will offer most of the things you’ll find in PIL (and is, we suspect, powered by PIL).
Also welcome news for developers: App Engine is now open to anyone. More than 150,000 developers have joined the waiting list over the past 6 weeks but only about half of those people have been given access. If you’ve been on the waiting list, today is your day.