Dive Into Python 3 now finished and downloadable as HTML and PDF | Hacker News Reader

Dive Into Python 3 now finished and downloadable as HTML and PDF

diveintopython3.org

121 pointssrid19 comments

Open articleView on HN

The footnote is funny,

"""

This site is optimized for Lynx just because fuck you.

I’m told it also looks good in graphical browsers.

"""

Yeh, it confused me too.

One day, I asked diveintomark on twitter:

  Why there's an unpleasant 'fuck you'?

and get the reply from Mark: http://twitter.com/diveintomark/statuses/1914075749

Now I'm just wondering, has Mark been greatly annoyed by the Internet Censorship?

That's a really funny reply. I suggest Mark try "^__^ fuck you ^__^"

Oh, you ruined all fun

"Also available in dead trees" for the print edition. Can't stop laughing.

"dead trees", that's a very common expression; why would you find it funny?

Because I hadn't heard/read it before.

you, my friend, are a bleeding-edge internet newb :-P

http://catb.org/jargon/html/D/dead-tree-version.html

http://catb.org/jargon/html/index.html <-- start here and spend a weekend.

Thanks Mark!

I followed a lot of diveinto series by Mark, so, Thank you!

Über-geeks can also clone the Mercurial repository:

you@localhost:~$ hg clone http://hg.diveintopython3.org/ diveintopython3

I know I'm a DBA, but I think this is the first time I've qualified as an Uber-geek.

Hacker News continues to keep me informed. I was just looking two or three weeks ago for a refresher course on Python and found everything outdated. Stellar.

Why is the section "What's New in Python 3" the last section?

Yes! Now, only the small matter that more than 9/10 modules will break under python 3, but hey, at least now we have a finished Dive Into Python 3!

Nothing is stopping you from using Python 2.x. Writing a new version of a language is never intended to be backwards compatible. Indeed, breaking backwards compatibility is essentially a perquisite because a new version is the opportunity to add all the useful features that couldn't be added before.

That doesn't seem completely true. I could imagine default language syntax changing from one version to another, but still being modifiable via "from __future__ import ..." or "from __past__ import ...", respectively. Unless the bytecodes of the VM are incompatible (which is possible), there isn't any reason py26 code can't talk to py30 code...

So go port them!

Two types:

1) People worth paying attention to.

2) Whiny bitches.

I wasn't being sarcastic... I actually like this

Reply on news.ycombinator.com