Slashdot Mirror

← Back to Stories (view on slashdot.org)

Django 1.0 Released

Posted by timothy on from the by-djove-they've-done-it dept.

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."

21 of 104 comments (clear)

  1. Great work by abigor · · Score: 4, Interesting

    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...

    1. Re:Great work by Shaitan+Apistos · · Score: 5, Funny

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

    2. Re:Great work by kiddygrinder · · Score: 4, Funny

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

      --
      This is a joke. I am joking. Joke joke joke.
    3. Re:Great work by Bogtha · · Score: 2, Informative

      well, if they were smart, they'd have used Jython to run Django on the JVM.

      Django already runs on Jython.

      --
      Bogtha Bogtha Bogtha
  2. yay by story645 · · Score: 5, Informative

    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.

    --
    open source modern art: laser taggi
  3. But... by PC+and+Sony+Fanboy · · Score: 2, Funny

    But does it run linux? And, Imagine all the djangos in a beowulf cluster...

    awww, who am I kidding. This is slashdot, I can't sound smart without referencing wikipedia. *siiigh*

    Seriously tho, Django is so much better than some of the other options (read:java!)

    1. Re:But... by siDDis · · Score: 3, Interesting

      Groovy for Grails http://grails.org/ which is based on Java/Hibernate/Spring is an excellent alternative to Django.

      It's just about choosing the right tool for the job.

    2. Re:But... by mcvos · · Score: 2, Interesting

      Seriously tho, Django is so much better than some of the other options (read:java!)

      You're now comparing a framwork with a language. For a meaningful comparison, compare Django with Wicket.

      It's not very surprising that new web frameworks are better than JSP, Struts or JSF. I want to know how they measure up to stuff like Wicket or the latest Tapestry.

  4. Re:obmoviequote by Anonymous Coward · · Score: 4, Funny

    vegetarians have a bitter after taste

  5. Django . . . by pembo13 · · Score: 3, Interesting

    it's what you come home to after a day with .NET at work.

    --
    "Thanks for all the money you paid to us. We've used it to buy off ISO among other things" -Microsoft
  6. The in-factor... by Max+Romantschuk · · Score: 5, Interesting

    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.

    --
    .: Max Romantschuk :: http://max.romantschuk.fi/
    1. Re:The in-factor... by Anonymous Coward · · Score: 4, Insightful

      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.

    2. Re:The in-factor... by Fweeky · · Score: 5, Informative

      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?

    3. Re:The in-factor... by Max+Romantschuk · · Score: 2, Informative

      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.

      Anyone who has ever worked in a larger organization will know that it's impossible to get people to configure their software identically, unless we're forcing every one.

      Also, a lot of people aren't that smart anyway...

      That's why I advocate spaces only: There is a single way to render a single space, so the margin for error is smaller. :)

      --
      .: Max Romantschuk :: http://max.romantschuk.fi/
    4. Re:The in-factor... by Peter+Cooper · · Score: 3, Insightful

      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.

      Consistence is good, but why it "one way of doing things" good in any sense? It's not a good thing in all scientific or artistic disciplines I can think of. There are multiple ways to heal all parts of the body and resolve medical issues, multiple ways to perform the same scientific experiments, multiple ways to build a bridge - why do you want "one way" to do something when it comes to developing software? That sounds like a code style dictatorship..

    5. Re:The in-factor... by Daimaou · · Score: 2, Informative

      I jumped on the Rails bandwagon for a bit, but I jumped back off after finding Django.

      I think Django has several advantages over Rails. It runs faster, is better organized, and is easier. I also like how Django limits the functionality of templates in order to force your logic into the controller, which is where it belongs.

      The only thing that bugs me about Django really is that they call the controller the view, and the view the template; which is mildly confusing at first.

  7. Market. People. they decide. and they did. by unity100 · · Score: 4, Interesting

    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.

    --
    Read radical news here
    1. Re:Market. People. they decide. and they did. by azgard · · Score: 4, Insightful

      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.

    2. Re:Market. People. they decide. and they did. by DragonWriter · · Score: 2, Informative

      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.

      Yes, the Model-View-Controller model was invented to deal with problems identified in PHP-based webapps. The amazing part of this is that MVC was first described in 1979, and PHP wasn't invented until 1995, so clearly there was considerable time travel involved.

  8. Django Sites by rmansuri · · Score: 3, Informative

    Well done to all who work hard for this !!!! Job done !! umm or i can say Job Started !! Have look at most comprehensive listing of websites that are powered by Django, the python web framework for perfectionists with deadlines.

    www.djangosites.org

  9. Re:Tab/space mangling (was Re:The in-factor...) by GrievousMistake · · Score: 2, Informative

    I'd recommend 4-space indents for Python, it's what the standard library uses, and what anyone who wants to use something 'standard', like any large project, will be using as well. One reason the tab/space things isn't a problem is that the language comes with a clear recommendation.
    I still use tabs for everything else, so I've added to my .vimrc:
    autocmd FileType python set et ts=4 sw=4 sts=4

    --
    In a fair world, refrigerators would make electricity.