Django 1.0 Released

jgomo3 writes "Finally, the stable version 1.0 of Django (one of the most popular free Python based frameworks) has been released. Explained in the project blog, this achievement was in part due to the great users and developers community of the Django project, and recall the big effort with numbers like 4000 commits and 2000 bugs fixed since last stable version. Django is 'The Web framework for perfectionists with deadlines.' You can dive in by reading the overview."

Comments

Great work

[abigor]

Django is just a pleasure to work with. Congratulations to these guys for creating such a well thought-out and hugely productive framework. Now if only it would become more established and bulked up a bit so we could mostly ditch a certain other Enterprise Edition set of technologies...

Re:Great work

[Shaitan Apistos]

You can have my Visual Basic when you pry it from my cold dead.... oh, wait, you mean Java? Yeah that needs to go.

Re:Great work

[kiddygrinder]

You bring up an interesting point: Would it just be easier to euthanise all the vb programmers than kill off the language?

yay

[story645]

I just started playing with Django today, so I'm mostly just thrilled that the absolutely awesome tutorials still work. This is one of the most newbie friendly things I've ever worked with, in large part 'cause it's got awesome documentation and very clear tutorials and logically named well almost everything. (Plus it produces pretty and friendly sites.) I may not be as hyper about it once I start trying to use it for a real project, but it getting to a stable release is promising.

Re:obmoviequote

[Anonymous Coward]

vegetarians have a bitter after taste

The in-factor...

[Max Romantschuk]

It's too bad everyone and their dog are excited about Ruby on Rails, when a great platform like Django is out there as well.

I use Django on my own site, and CakePHP (a poor RoR clone) at work. While using PHP has advantages, CakePHP is really not anywhere near Django in terms of the ORM stuff and actually using your data in any complex way.

The one really great thing about Django is that it's consistent. There is usually one way of doing things, instead of a million different ways that apply in different situations.

Take a look at the Django tutorial:
http://docs.djangoproject.com/en/dev/intro/tutorial01/

And the Django book:
http://www.djangobook.com/

I don't think you'll be sorry.

PS. And on the whole Python indentation=block thing... It's not perfect, but only use spaces and it won't be a problem.

Re:The in-factor...

[Anonymous Coward]

And on the whole Python indentation=block thing...

...just give it a try. Most people who haven't written any Python think it's an awful idea. Most people who spend a few hours learning Python change their mind. It's just one of those cases where first impressions are totally wrong.

Re:The in-factor...

[Fweeky]

It's too bad everyone and their dog are excited about Ruby on Rails, when a great platform like Django is out there as well.

Even in the Ruby world, it's too bad Rails gets most of the attention; a lot of people would probably be better off with one of the many more lightweight frameworks there, or even no framework at all (really, your 3 page website needs an 80kLOC framework to support it?). So many people hyperfocus on one system and miss out on all the other ways of doing things; Nitro, Merb, Sanatra, Ramaze, even writing your own handlers in Rack. Given the size, complexity and overhead of these things, it'd really make more sense for people to start from the bottom (Rack) and work their way up, not the other way around.

Python wise this probably means starting by writing your own WSGI handlers, rather than starting with a huge framework to write Hello World in.

on the whole Python indentation=block thing... It's not perfect, but only use spaces and it won't be a problem.

Blegh, use tabs properly and it won't be a problem either. It's shocking how people can't even get a trivial thing like that right, though, is it really that difficult to configure your editor not to mix the two? Hint: Set your editor to highlight leading whitespace, doing tabs and spaces differently, then you'll never be surprised by either. I'll get you started:

highlight LeadingTab ctermbg=blue guibg=blue
highlight LeadingSpace ctermbg=darkgreen guibg=darkgreen
highlight EvilSpace ctermbg=darkred guibg=darkred
au Syntax * syn match LeadingTab /^\t\+/
au Syntax * syn match LeadingSpace /^\ \+/
au Syntax * syn match EvilSpace /[^\t]\+\zs\t\+/ " tabs not preceeded by tabs are never acceptable
au Syntax * syn match EvilSpace /\zs\ \+$/ " trailing space is silly

There, now you have no excuse. Well, except the first EvilSpace match broke at some point, anyone see why?

Market. People. they decide. and they did.

[unity100]

excuse me, i hate to break it to you people but we programmers dont decide what goes on to being popular.

a LOT of 'great' and truly great technologies were devised and pushed to the net, and what happened ?

people chose what they would.

php grown way over itself as of now. the demand for it, and the applications on it, regardless of how much you despise or belittle them, are growing boundless. phpbb, oscommerce, name your pick. especially oscommerce has grown over a cart, and kind of became an industry standard. every major provider of anything from ups, fedex to any payment provider SUPPORTS it. but call them and say 'hey i have a great cart on this and this great framework, i cant make it work with your service', and you'll learn that youre on your own.

a lot of you, i know, are career i.t. staff. working on positions in corporations, having little touch with the 'ordinary people' out there on the net.

this creates a sphere of isolation, and makes one mistake the trends. there is only one trend that decides everything - choice of the people. look at what php was 5 years ago, where it was, and where it is now, almost a default for shared web hosting, or small business apps for every kind of sector. its so default that, some people who are less technologically literate tend to take php as 'hosting'.

my a few cents. early in the morning. sleepless. coherency shouldnt be expected. random thoughts.

Re:Market. People. they decide. and they did.

[azgard]

excuse me, i hate to break it to you people but we programmers dont decide what goes on to being popular.

I don't think so. Things are not popular for no reason. Usually, things that become popular have some obvious advantage to existing technology, and that's why people chose it. Only later it is discovered there are also disadvantages to the new technology (usually because it's not so mature in other areas), and even later, the new technology is integrated with the technologies that existed before. It's a natural cycle of progress.

PHP is nice example. It had advantage in allowing having business logic directly in HTML pages (i.e. easy creation of dynamic pages compared to CGI), and was free. But there was a disadvantage to this approach, so the MVC model and frameworks using templates were invented. So the modern frameworks combine advantages of both technologies.

The same could be said about Rails. They use obscure language (sorry), but the basic ideas are sound. That's why they are copied by other frameworks, which combine advantage of more well-known language with the advantages of Rails.