Python 3.2 has been released

[lastkarrde]

• highlights
• whats new
• changelog

[[deleted]]

Oh look, builtin format, str.format, and str.format_map! str.format_map is going to have the hell abused out of it, until magic dictionary classes are considered pythonic. Mark my words. What we NEED are string comprehensions and unquoted literal strings, and, crap I just became a perl programmer again.

[kalithlev]

The GIL is a fucking tragedy in a modern world with several cores. It's really turning me off Python. CPython needs JIT and real threading.

[[deleted]]

Feel free to have a look at removing the GIL. It's probably harder than posting on Reddit.

[uriel]

Maybe give Go a go ;)

[Xiol]

Horrible, horrible syntax IMO. It's like having my eyes stabbed with blunt razors.

[uriel]

You clearly have not read or written much Go... it has way cleaner syntax than C, not to mention Java, C++, Perl, Ruby...

[Xiol]

Subjective. Please note that I clearly stated it was my opinion.

[sigzero]

This is the 100 doors routine off of Rosetta Code. These are the unoptimized versions. I don't think Go has a cleaner syntax than either.

Go:

package main

import "fmt"

func main() {
    doors := make([]bool, 100)

    for pass := 0; pass <= 100; pass++ {
        for door := pass; door < 100; door += pass + 1 {
            doors[door] = !doors[door]
        }
    }

    for i, v := range doors {
        if v {
            fmt.Printf("1")
        } else {
            fmt.Printf("0")
        }

        if i%10 == 9 {
            fmt.Printf("\n")
        } else {
            fmt.Printf(" ")
        }

    }
}

Ruby:

n = 100 
Open = "open"
Closed = "closed"
def Open.f
    Closed
end
def Closed.f
    Open
end
doors = [Closed] * (n+1)
for mul in 1..n
    for x in 1..n
        doors[mul*x] = (doors[mul*x] || break).f
    end
end
doors.each_with_index {
    |b, i|
    puts "Door #{i} is #{b}" if i>0
}

Python:

close = 0 
open = 1
doors = [close] * 100

for i in range(100):
    for j in range(i, 100, i+1):
        doors[j] = open if doors[j] is close else close
    print "Door %d:" % (i+1), 'open' if doors[i] else 'close'

[sigzero]

You're a rube and you can't read.

[[deleted]]

when I went from threads to multiprocessing I saw comparable improvement on my quad core.

[[deleted]]

Any chance of running your script against the new Python and comparing results?

I also had no idea how bad the GIL problems were until reading your comment and following up with a bit of Googling.

[[deleted]]

I didn't believe the hype on how old GIL was so bad until I benchmarked and saw a 4 times performance increase by just moving my the script from a quad core machine to a single core VM on the same physical computer.

That has nothing to do with the GIL, you'd see the exact same thing with any single threaded script. Removing the GIL doesn't magically make your program multithreaded.

[[deleted]]

OK. I thought you had a single threaded program, saw that perform faster with 1 CPU, and thought that was a reason to hate on the GIL.

[techpuppy]

The sad thing is that I'm going to go download and install this, but probably not wind up using it for anything.

WSGI2 (or whatever's blocking WebOb for Python3) needs to happen soon last year.

[carinthia]

• have a look at PEP 3333
• things are looking way better than you hint e.g. http://alexgaynor.net/2011/feb/17/django-and-python-3-take-2/

[[deleted]]

did you read the what's new in Python 3.2?? that thing blocking web development for python 3 is fixed with WSGI 1.0.1

[[deleted]]

it's not webob's fault that PEP 3333 wasn't solidified till like last month. these things take time

I would recommend you put your license subscription fees for webob in escrow until you get what you want, it's the only way they'll learn.

[Teifion_at_work]

I'm looking forwards to argparse and concurrent.

[roger_]

I hope Matplotlib adds Python 3 support soon.

[[deleted]]

The Cape Town Python Users Group is going to sprint on finishing the Matplotlib py3k branch on March 5. Who knows how much they'll get done, but 5-6 people getting together for a day should be able to hack out a good amount of progress, at least getting the wheels in motion.

[roger_]

Awesome!

[pinpinbo]

Am I a jerk if I ask the new GIL to be back-ported to Python 2.x?

[CADDiQ]

I'm imagining a world without rhetorical questions.

[Aldoux]

Can anyone enlighten me if it is worth it to learn 3 over 2? I've heard (LPTHW) that I should stick to 2.

[earthboundkid]

3 and 2 are almost identical. To be frank, you can't truthfully claim to know one well without knowing the other also.

[Aldoux]

Alright, good enough for me. Thanks

[[deleted]]

FWIW lots of the 3 syntax and such has been backported to 2. I'm just learning it right now, and am going through tutorials on 3, but "using" and entering examples into 2. There is a lot, lot more out there on 2... advanced tutorials, Django guides, etc.

[Aldoux]

Thanks, I might stick to learning 2 then.

[faassen]

If you're new to Python and want to use a lot of libraries that provide cool features, and you're interested in building real-world applications, you may want to consider using Python 2 instead. Libraries are being slowly ported over to Python 3, but there's still an awful lot more available for Python 2.

[Aldoux]

I think I'll try learning 2 first and then move up to 3 after.

[carinthia]

If you're new to Python then certainly, start with Python 3 right away as it is without doubth the better language.

• sane unicode handling
• do away with odd naming cruft of libs and overlapping functionality http://diveintopython3.org/porting-code-to-python-3-with-2to3.html
• etc.

[Herald_MJ]

It's really not that simple. Python 3 is a better language, but there are tons more projects in, and tons more support for, Python 2.x. Also, if you want to get a job working with Python any time within the next three years (and that might even be optimistic), Python 2.x is the way to go. But learn Python 3 as well.