=== _thumper_ is now known as thumper [23:33] hey [23:33] does anyone know where bzr is on python3 support? [23:33] I don't think it's gotten anywhere really [23:34] its odd that while almost the entire python community has finished migrating now the vcs tools are still lagging [23:34] bzr is pretty dead-ish [23:35] did you see jelmer's blog post? [23:35] no [23:35] Arc: Is Python 3k really supposed to entirely supersede 2.x? [23:36] That's the intent, as I understand it [23:36] rozzin: yes. 2.7 was released to aid in migration, but no more features will be added to 2.x [23:36] rozzin: they dropped the k, and I assume they were hoping to stop doing security updates to 2.7 at some point ... [23:36] there will never be a 2.8 so says guido, and i agree with that. [23:36] Meh. [23:37] ive been using py3 as my /usr/bin/python for years just fine [23:37] and with both gnome and kde making the switch, and the major python web frameworks, etc... its only a matter of time before /usr/bin/python2 becomes unnecessary [23:38] im trying to trim down a raspberrypi image and looking at the things that rely on python2, it'd be a boon to be able to cut it out entirely [23:38] It's like hearing "C++ is expected to replace C. All C developers are expected to migrate to C++", for me. [23:39] It's not really comparable, IMO [23:39] Although I have to admit I haven't even started writing Python 3 myself yet [23:39] rozzin: more like "Perl5 is expected to replace perl4. All Perl developers are expected to migrate to Perl5" [23:39] Partly because I have to still deal with some ridiculously old installations at work [23:39] maxb: the differences are so subtle as to be almost ignorable. [23:39] its akin to going from python 2.4 to 2.6 [23:40] a bigger jump than a minor, but no more than 2 or 3 minor revisions [23:41] Arc: I don't know. Never knew Perl4. [23:41] At some point I'm probably going to have to sort out backported packages for Debian oldoldoldstable, if I'm going to use it at work :-/