Django Community Aggregator

Eric Florenzano: DjangoCon: Great conference, or greatest conference ever?

Mon, 08 Sep 2008 04:00:59 -0700

The internet is such a strange place. It allows us to collaborate on projects without ever seeing each other in person. It allows us to meet new people, discover interests that we never knew we had, and keep in touch with friends. However much the internet allows us to connect, though, there's simply no replacement for face-to-face contact. Who would have thought that a piece of software whose main goal is to ease the pain of creating websites could bring people together from Prague, London, Germany, and even Lawrence, Kansas? To me, it's nearly inconceivable. But inconceivable or not, Django now has its very own conference.

What I noticed about this first DjangoCon was a strange and exciting dichotomy of sorts, best exemplified by the opening and closing keynotes. On the one hand, it's difficult to believe just how far Django has come since it was first released in 2005. On the other hand, there are so many great ideas for Django and Django-related projects that it's nearly impossible to fight the urge to pop open your favorite text editor and start coding right now.

For some people, it was great to meet them for the first time, and for others, it was great to simply reconnect. (Apologies to those that I couldn't fit into those links, by the way.) Below is what I find to be a hilarious image, courtesy of Sebastian Hillig--whose Flickr page has some really well-shot photos of the conference.

For those of us involved in the Pinax project, DjangoCon was a bit of a coming out party. Firstly, in a literal sense--as cloud27, the flagship website built on Pinax, was launched (real men launch during presentations). But also in a figurative sense--as most of us sported our Pinax-branded shirts and trumpeted the features that Pinax provides out of the box. James Tauber's talk that kicked it all off couldn't have gone better, and I'm certain that when the video comes out on YouTube, it will enjoy a second and third life while people discover and become interested in the platform.

Another thing that surprised me about the conference was the amount of healthy criticism that went around in the conference. Only a select few presentations escaped the constructive criticism of James Bennett, the wrath of Cal Henderson, or the healthy reminders by Mark Ramm. Instead of people getting upset, though, I heard all sorts of conversations throughout the conference discussing ideas and strategies for how to overcome the shortcomings that were pointed out.

But in the end, what would DjangoCon be without a good old fashioned group hug? Thanks to everyone who made it possible, and here's to another year of friendship and achievement for everyone in Django-land!

(Picture by 704race, whose pictures are also really fun!)

David Cramer: Django Debug Toolbar

Mon, 08 Sep 2008 02:01:13 -0700

After the presentation yesterday evening, and Cal Anderson showing Pownce’s debug toolbar for a moment, it seemed like a great idea to create a pluggable out of it. It turned out I wasn’t the only one with this idea. I ended up creating a few “panels” inside of an overlay toolbar, which showed things like SQL [...]

Patrick Altman: Shifting Bits: Another Django Blog Engine

Sun, 07 Sep 2008 22:01:25 -0700

Tonight I released/open-sourced ShiftingBits. This blog is still on WordPress, but I believe I am close to having the all the features I need/require to make the migration possible. I pretty much stole a bunch from Brian Rosner’s oebfare code base so if any of it looks familiar, that’s where I copied a lot of [...]

Simon Willison: Django tickets with keyword "djangocon"

Sun, 07 Sep 2008 20:01:03 -0700

Django tickets with keyword “djangocon”. Adrian and Jacob ran an “I want a pony” session during their closing keynote at DjangoCon—I’ve filed the feature requests as tickets tagged with the “djangocon” keyword.

James Bennett: Slides

Sun, 07 Sep 2008 11:00:33 -0700

I’m sitting here in Building 40 at Google, waiting for this morning’s first DjangoCon keynote to start, and getting ready for the Django technical design panel which comes immediately afterward. Naturally, I’m taking advantage of the down time (and Google’s bandwidth) to upload my slides from yesterday’s talk. If you’ve seen/read the slides from the version of this talk I gave at PyCon, I can tell you that ...

Read full entry and comments

Patrick Beeson: How to upgrade to Django Comments 1.0

Sun, 07 Sep 2008 08:00:32 -0700

The release of Django 1.0 held many new developments for the Python-based framework that I've used to build several projects during the past few months. But one feature I was really looking forward to exploring was the new, refactored comments application.

Unfortunately, Django Comments 1.0 also comes with the scary prospect of database updates, data migrations, markup changes, CSS changes and other headaches. Here's how I tackled the upgrade.

Prepare your projects

My personal Web site was already running on a variation of Django trunk (pre-alpha) before I upgraded to Django 1.0 final. This made the update process somewhat easier since I'd already been through the updates for newForms admin and the like.

Also, I don't have a typical development environment for this site, which really puts an emphasis on reading through the documentation. You don't want surprises from backwards-incompatible changes!

Here are the steps I took for preparing my site for Django Comments 1.0:

Read the documentation on the Django Project site thoroughly (including the upgrade guide)
Comment out, or remove any references to the awesome, but incompatible (for now) django-comment-utils package
Change any reference to "FreeComment" to "Comment"
Change template tags to reflect the new methods of getting the list of comments or the comment count, like {% get_free_comment_list for blog.entry object.id as comment_list %} and {% get_comment_count for blog.entry object.id as comment_count %}
Update the template tag for rendering your comment form to {% render_comment_form for object %}
In your URLs, change (r'^comments/', include('django.contrib.comments.urls.comments')), to (r'^comments/', include('django.contrib.comments.urls')),
If you're providing an RSS feed for the latest comments, change this to from django.contrib.comments.feeds import LatestCommentFeed

You'll also need to take a look at the new template offerings provided with Django Comments 1.0:

reply_preview.html
posted.html
preview.html
moderation_queue.html
flagged.html
form.html
flag.html
reply.html
base.html
delete.html
deleted.html
approve.html
approved.html
400-debug.html

I had to update my modified versions of preview.html and posted.html to reflect the upgrade.

Once you've prepared your site for the upgrade, run the following, and hopefully familiar, command from shell: python manage.py syncdb

This will install the new "django_comments" table and index in your database.

Migrating your comments to Django Comments 1.0

For those with little knowledge of MySQL, don't fret. This part is very easy thanks to a code snippet provided in the Django Comments 1.0 upgrade guide. Simply use the following shell command to enter your database shell python manage.py dbshell and run the following SQL:

BEGIN;

INSERT INTO django_comments
    (content_type_id, object_pk, site_id, user_name, user_email, user_url,
    comment, submit_date, ip_address, is_public, is_removed)
SELECT
    content_type_id, object_id, site_id, person_name, '', '', comment,
    submit_date, ip_address, is_public, approved
FROM comments_freecomment;

INSERT INTO django_comments
    (content_type_id, object_pk, site_id, user_id, user_name, user_email,
    user_url, comment, submit_date, ip_address, is_public, is_removed)
SELECT
    content_type_id, object_id, site_id, user_id, '', '', '', comment,
    submit_date, ip_address, is_public, is_removed
FROM comments_comment;

UPDATE django_comments SET user_name = (
    SELECT username FROM auth_user
    WHERE django_comments.user_id = auth_user.id
) WHERE django_comments.user_id is not NULL;
UPDATE django_comments SET user_email = (
    SELECT email FROM auth_user
    WHERE django_comments.user_id = auth_user.id
) WHERE django_comments.user_id is not NULL;

COMMIT;

Your comments should be properly migrated into the new comments table.

Make sure you restart Apache after these changes!

New HTML in comments

Previous to this upgrade, Django Comments only provided fields for name, e-mail and the comment itself. New in Django Comments 1.0 are name, e-mail, URL and the comment field.

You'll probably need to change your CSS to hook into the new URL field, as well as the new "submit" options.

Also, keep in mind that the "name" database field has changed from person_name to user_name. This will require a change to your template variables.

Other updates includes a number of spam-prevention features such as the "honeypot" field.

For now, I'm relying on the new spam prevention instead of the django-comment-utils Akismet filter. But I'm quite certain I'll need to find a way to re-integrate this soon.

First impressions of Django Comments 1.0

Though it's only been a few hours since I've preformed the update, the new Django Comments app appears to be preforming very well. Unless you've hacked the older comments app to provide functionality that doesn't exist in the new version, it would be well-worth an upgrade.

I'd love to hear others' feedback on the new app; feel free to post your thoughts in the comments, or contact me directly.

Patrick Beeson: Upgrading to Django Comments 1.0

Sun, 07 Sep 2008 07:00:46 -0700

Unfortunately, Django Comments 1.0 also comes with the scary prospect of database updates, data migrations, markup changes, CSS changes and other headaches. Here's how I tackled the upgrade.

Prepare your projects

Also, I don't have a typical development environment for this site, which really puts an emphasis on reading through the documentation. You don't want surprises from backwards-incompatible changes!

Here are the steps I took for preparing my site for Django Comments 1.0:

Read the documentation on the Django Project site thoroughly

John DeRosa: Moving from Django to Plone

Sat, 06 Sep 2008 23:00:56 -0700

This is the first of what might be a series of posts about learning Plone. Or, maybe I’ll never write about this again… I’ve worked in Django since January 2006, when Joe Heck, Karen Williams, and I built the now-defunct TrenchMice site. I haven’t done any Django work since March, when I joined Fisher Communications, but I’ve followed [...]

David Cramer: High Performance Django

Sat, 06 Sep 2008 19:00:08 -0700

Below you will find resources from my presentation on High Performance Django. Slides Profiling Middleware Template Engine Benchmarks: Real-world Example, Benchmark Testcase

Arthur Koziel: Automatical superuser creation with Django

Fri, 05 Sep 2008 16:04:09 -0700

I delete and sync my database fairly often during development with Django because the "syncdb" command will not alter the table in the database after, for example, adding a new field to the corresponding model.

The problem I have with this is typing in the same data for a superuser over and over again. It's a very repetitive task, so I was grateful when I heard this tip from my co-worker Sebastian today.

Superuser from fixture

We're going to automatically load the superuser from a fixture. To do this, dump the data of the auth module into a fixture called "initial_data.json":

./manage.py dumpdata --indent=2 auth > initial_data.json

You'll see that along the superuser that you've already created during the usual "syncdb" execution, a few other credentials got dumped. Since we only need the data for the superuser, delete the irrelevant stuff. The file should look like this:

[
  {
    "pk": 1, 
    "model": "auth.user", 
    "fields": {
      "username": "arthur", 
      "first_name": "", 
      "last_name": "", 
      "is_active": true, 
      "is_superuser": true, 
      "is_staff": true, 
      "last_login": "2008-09-04 14:25:29", 
      "groups": [], 
      "user_permissions": [], 
      "password": "sha1$fooobar123", 
      "email": "arthur@arthurkoziel.com", 
      "date_joined": "2008-09-04 14:25:29"
    }
  }
]

The fixture called "initial_data.json" will automatically get loaded by Django every time you execute the "syncdb" command.

Delete your database and try to run the "syncdb" command with the "--noinput" option passed (it will prevent the script to go into interactive mode):

./manage.py syncdb --noinput

There shouldn't be a prompt for a superuser and you should see a message at the end of the output indicating that your fixture was loaded.

Admin login

Not having to create a superuser is great, but if you're working a lot with Django's contrib.admin application, you'll need to log-in again every time you sync the database and load the user fixture. Another repetitive task that can be eliminated:

After logging in into the admin backend, dump the data of the "session" table into stdout:

./manage.py dumpdata --indent=2 sessions

Copy the dictionary containing the session for your superuser and append it to the list in "inital_data.json" like this:

[
  {
    "pk": 1, 
    "model": "auth.user", 
    "fields": {
      "username": "arthur", 
      "first_name": "", 
      "last_name": "", 
      "is_active": true, 
      "is_superuser": true, 
      "is_staff": true, 
      "last_login": "2008-09-04 14:25:29", 
      "groups": [], 
      "user_permissions": [], 
      "password": "sha1$foobarbarfoo", 
      "email": "arthur@arthurkoziel.com", 
      "date_joined": "2008-09-04 14:25:29"
    }
  },
  {
    "pk": "9aadfe1de61b0937fasd684221f03", 
    "model": "sessions.session", 
    "fields": {
      "expire_date": "2008-10-20 14:34:59", 
      "session_data": "foobar123"
    }
  }
]

You might want to increase the "expire_date" a little bit, so that your session won't expire.

Now everytime you delete and sync your database (remember to pass "--noinput"), Django will automatically load the superuser and it's associated session from the fixture. You won't have to manually type in the data for the user and log-in into the backend everytime anymore.

Ville Säävuori: Django Release Party in Helsinki

Fri, 05 Sep 2008 08:07:25 -0700

Heads up Finnish Djangonauts! Join us for celebrating the Django 1.0 release at Kaapelitehdas, Helsinki tomorrow evening (Saturday 6th) starting at 5 pm. More information on the location and attendees can be found on the event wiki page.

This is an open invite — everyone is welcome!

See you there! :)

» Comment this entry

Will Larson: Migrating the 'This Week in Django' Concept

Fri, 05 Sep 2008 06:04:53 -0700

In honor of the fresh redesign at This Week In Django, I decided to spend a few moments considering why this amazing concept hasn't caught on with other projects yet. Sure--Michael, Brian and Kevin put in a huge amount of time week after week--but maybe there is something more?

This Week in iPhone Development

Soundtrack: any hit that allows silhouettes to groove violently.

Welcome to This Week in iPhone Development! We have a really exceptional show lined up for you.
Yes. Thats right. This week showed some crucial developments over at Apple. In fact, some of the engineers I have spoken to referred to the changes as "more exciting than my first child."
Really? So lets get started talking about those changes.
Ah.. right. Well, I'd love to. But our legal department is pretty sure we can't talk about it in public without violating the NDA.
Right. That's still a problem. How about this week in the blogs then?
Well, legal isn't really comfortable with us talking about those either. It might make us complicit or something.
Well. This has been another Week in iPhone Development. Tune in next week for more of the same great news!

This Week in Google Chrome

Soundtrack: something with the same levels of oddity and production values as the song for the Scala programming language¹.

Welcome to This Week in Google Chrome!
Google made a goddamn browser. Holy hell. It's amazing.
Well, beyond being a browser, it has some really impressive technical qualities.
Man. This is so amazing. Reddit Programming is loving Google Chrome! Google made a browser!
Well, if we take a look at John Resig's piece on Google Chrome's Process Manager, then we begin to see how Chrome has some technical merit and may open up a new spurt of browser development.

Browsers have been spending a considerable amount of time working on CSS rendering, and I think its exciting that we'll come back to having a more holistic approach to browser development, that spends time looking at intuitive and uncluttered interfaces as well as performance issues.
Its a browser, dude. I can't believe I'm getting a browser!
Fuck it. I quit. You're worse than the color anouncer in Best in Show.

Anyway, after reflecting on it, it does seem there may be some explanations for why This Week in Django's brilliance hasn't yet migrated into other communities.

Strangely enough, the song is no longer prominently featured on their website. I was able to find a possibly usable link though on a blogspot blog entry. If someone finds a better link, let me know.↩

Simon Willison: Think Wize crew celebrates the Django 1.0 release

Fri, 05 Sep 2008 06:04:53 -0700

Think Wize crew celebrates the Django 1.0 release. With a trip to the Django Reinhardt museum at his birthplace in the village of Liberchies, Belgium.

Eric Florenzano: [Link] This Week in Django

Fri, 05 Sep 2008 04:03:54 -0700

The TWiD guys have outdone themselves yet again! I have had the distinct honor of appearing and guest hosting on their show. Now they have completely re-done their website. This is one of the best redesigns I've seen in quite a while, and I'm certain that it will become a defacto goto for great Django information and news.

Eric Florenzano: [Link] Zerok's Blog

Fri, 05 Sep 2008 04:03:54 -0700

Zerok has committed a ton of great patches to my Django reusable application projects. Every time that I review one of his patches, it goes through without any modifications. This guy not only provides great patches, but he has some great Django tips and tricks. Subscribe to his blog for some serious Django tips and tricks.

Hugo: Django 1.0 released!

Fri, 05 Sep 2008 03:01:38 -0700

Django 1.0 released! - hat lange gedauert, aber das kann ja durchaus der Qualität zuträglich sein. Und hier ist es das. Gratulation!

Rafael Campos de Bastiani: NicEdit no Admin do Django

Thu, 04 Sep 2008 20:55:40 -0700

Depois de muito tempo sem postar algo aqui, devido a trabalho, faculdade e vícios em geral, eu resolvi fazer um pequeno tutorial de como usar um WYSIWYG, o que eu usarei neste artigo e que gostei muito dele é o NicEdit[url]http://nicedit.com[/url], ele é leve e bem pratico, e fácil de incorporar ao admin do Django.

O NicEdit é constituído de dois arquivos, o [b]nicEdit.js[/b] e o [b]nicEditorIcons.gif[/b] nos quais ...

Rafael Campos de Bastiani: NicEditor no Admin do Django

Thu, 04 Sep 2008 19:55:41 -0700

O NicEdit é constituído de dois arquivos, o [b]nicEdit.js[/b] e o [b]nicEditorIcons.gif[/b] nos quais ...

Shwagroo Team: Django 1.0

Thu, 04 Sep 2008 08:55:46 -0700

Jak już zapewne wszystkim wiadomo, zostało wydane Django 1.0. Wiedziałem, że chłopakom się uda :). Ostatnio powstało kilka niekompatybilnych wstecz zmian, jednakże w żaden sposób one mnie nie dotknęły. Pełną listę niekompatybilnych zmian możecie zobaczyć na...

Mercurytide: Django articles: Django cheat sheet

Thu, 04 Sep 2008 03:55:33 -0700

With the release of Django 1.0, we're pleased to announce the release of a completely updated version of our highly popular Django Cheat Sheet which is crammed with a whole host of useful Django information.

Alex Koshelev: Рождение Django 1.0

Thu, 04 Sep 2008 00:55:58 -0700

Ну вот. Даже как-то грустно. То чего все мы так долго ждали наконец свершилось. Джанга родилась в своем релизном варианте с гордым "1.0" на ярлыке.

Почему грустно? Да потому, что тот темп, с которым менялась джанга последний год(с лишним), приучил нас быть всегда в тонусе, следить за изменениями, подстраиваться под них и как-то менять своё видение этого чудесного фреймворка. А что теперь? Мне кажется что темп упадет, а значит и драйв обитания на trunk будет не такой как раньше.

Ну ладно с ним с драйвом, будем искать в других областях. Важно то что наконец джанга должна приобрести общепризнанный статус production/enterprice-ready и пойти в массы с ещё более быстрыми темпами. Компании (конечно в большей степени управленцы в них), которые раньше на этапе выбора платформы и инструмента воротили нос от продукта, который был, как им казалось, не готов для боевого применения, сейчас начнут пересматривать свои воззрения, и уже для новых проектов боле пристально смотреть на джагу как на реального кандидата в освоении и применении. Я на это надеюсь по крайней мере. Пусть для многих смелых и разумных, уже давно джанга вполне была готовой к бою, но всё равно оставались сомневающиеся.

Так же теперь в споре на лидерство на рынке веб-фреймворков для быстрой разработки приложений у джанго есть новый веский довод.

Кстати, то что была организована Django Software Foundation, тоже придает солидности и добавляет козырей в колоду нашего любимого фреймворка.

Ожидаю всплеск интереса как к самой джанги, так и к сообществу в целом, как это было например после релиза GAE. А это поможет нам, разработчикам и отчасти евангелистам, быть более на виду и на нас станут обращать больше внимания. А кому этого не хочется?:)

Главное, чтобы после вселенской гулянки, корные разработчики продолжали привносить новые идеи и концепции для улучшения существующего положения вещей внутри фреймворка. А мы в свою очередь будем продолжать их осваивать и использовать в своих разработках, пусть с меньшей скоростью чем раньше. Но может быть это и не плохо? А может вообще всё будет по другому? Посмотрим.

Огромный шаг в завоевании умов и сердец веб-разработчиков сделан, кто раньше ещё размышлял "быть или не быть", теперь с большей долей вероятности скажут - "быть"!

Что же, живем и работаем дальше, но уже с чуть другим чувством. Да, и приходим обязательно на локальную гулянку в честь этого события!

PS: Интересно, а я один был озабочен вопросом - кто быстрее: джанга или гугл хром:)

Теги:
django python web