Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Django 1.6 released

djangoproject.com

Post reply on HN
Print view View original

81–90 of 107 posts

Re: Django 1.6 released

#81

Post by azio_m »

jroseattle wrote: post #38

Django is one of my favorite open-source projects. I owe the project a lot. Years ago, when I was a Microsoft-only shill (yeah, I'll say it), I knew how to build almost anything as long as something from Microsoft was under the covers. I was proud of my abilities, and in spite of the anti-MS crowd, I stood up for my platform and was a good developer. In 2006, I had a short two-week break from my startup job, and my w…

I had a somewhat similar experience. I was using PHP for many, many years and after hearing all the fuzz about Ruby/Rails I tried to learned it but it didn't really click with me. However, when I tried Python/Django I was immediately hooked. The main deciding factors were Django admin site and the (cleaner than Ruby) Python syntax.

Django admin site is still my favourite feature.

Re: Django 1.6 released

#82

Post by kkwok »

phpnode wrote: post #39
d0m wrote: post #36

For those who works with designers or html people who don't use the command line, how do you collaborate with them with Django? For me it's a perpetual issue to get them up and running, commit/push with git, etc etc. Is there an easier solution? Basically, I'd like them to get started and be able to tweak the templates and css as effortless as possible. It's kind of very hard to have people working directly in templa…

I don't use django, but one of the easiest ways to get designers and non technical folks working directly on projects is to run virtual machines with vagrant[0] and automate everything as much as possible. [0] http://vagrantup.com/

As someone with no experience with this, any resources you'd recommend on how to set this up?

Re: Django 1.6 released

#83

Post by collyw »

mhurron wrote: post #41
mbell wrote: post #25

Earlier quoted context omitted.

It's hard to imagine using an ORM for anything high volume that just got around to adding (still very limited) connection pooling. I'd tend to think anyone overly concerned with performance would use SQLAlchemy, if they use any ORM at all.

> I'd tend to think anyone overly concerned with performance would use SQLAlchemy, if they use any ORM at all. Or they did connection pooling outside the development framework.

right tool for the job. Djangoś ORM is great for simple stuff. And it works with the admin interface (which is worth a lot). If You need something complex enough, use raw SQL.

The admin was too much to give up to swap the ORM to SQLAlchemy for me.

Re: Django 1.6 released

#85

Post by scardine »

d0m wrote: post #36

For those who works with designers or html people who don't use the command line, how do you collaborate with them with Django? For me it's a perpetual issue to get them up and running, commit/push with git, etc etc. Is there an easier solution? Basically, I'd like them to get started and be able to tweak the templates and css as effortless as possible. It's kind of very hard to have people working directly in templa…

PyCharm (a Python IDE from JetBrains) is excellent, designers from my team love it.

Re: Django 1.6 released

#86

Post by phpnode »

kkwok wrote: post #82
phpnode wrote: post #39

Earlier quoted context omitted.

I don't use django, but one of the easiest ways to get designers and non technical folks working directly on projects is to run virtual machines with vagrant[0] and automate everything as much as possible. [0] http://vagrantup.com/

As someone with no experience with this, any resources you'd recommend on how to set this up?

well, it's mainly geared towards PHP but you might find https://puphpet.com/ useful to get a reasonably sane vagrant/puppet installation which you can then customize for django or whatever. You could just remove the php specific stuff from the generated configurations if you don't want it

Re: Django 1.6 released

#87

Post by paganel »

andybak wrote: post #10

Yay. Major usability wart fixed: "ModelAdmin now preserves filters on the list view after creating, editing or deleting an object."

I was always opening an object link in a new tab and then going back and hitting refresh in the main tab with the admin listing. Guess I won't have to do that anymore.

Re: Django 1.6 released

#88

Post by paganel »

smaili wrote: post #58

It's amazing to see how far along Django has come. Anyone remember when Django first came out? Good times :)

Yeap, it was early 2006 for me, in the pre- 0.96 days. I came to Django from Zope, that seems so long ago.

Re: Django 1.6 released

#89

Post by FilterJoe »

kkwok wrote: post #82
phpnode wrote: post #39

Earlier quoted context omitted.

I don't use django, but one of the easiest ways to get designers and non technical folks working directly on projects is to run virtual machines with vagrant[0] and automate everything as much as possible. [0] http://vagrantup.com/

As someone with no experience with this, any resources you'd recommend on how to set this up?

http://gettingstartedwithdjango.com/

Doing the first 2 lessons will not only get your a vagrant powered VM up and running, it will also give you a good feel for normal use. And you'll also be learning Django.

Re: Django 1.6 released

#90

Post by codygman »

mhurron wrote: post #57
daGrevis wrote: post #13

It's a small change yet I'm really happy with it. > BooleanField no longer defaults to False It caused quite a few headaches. Boolean can't have default.

> Boolean can't have default. I don't see the problem.

Warning: default was False previously so this example is backwards

Think about this code:

    class Missile(models.Model):
        # we can only attack short countries
        target = models.CharField(max_length=7)
        should_launch = models.BooleanField()
        
        def launch(self):
            """
            pass launches the missile
            """
            pass
You recently added a new missile: # add new missile in case we have to attack Merica # it won't be launched until we set should_launch to True Missile.objects.create(target="Merica")

Then you have a view:

    /missile/launch_missiles
with the code:

    for missile in Missile.objects.filter(should_launch=True):
        missile.launch()
You'll have the unexpected behavior of launching that missile you just added. With the new behavior your missile wouldn't be launched until you told it to. Basically this update has everything to do with the missile above failing this conditional:

    missile.should_launch is True
Since 'None is not True and None is not False', it is a sensible default for Booleans.
Post reply on HN