3 ms·

Python 3.0 came out in 2008 and 3.3 came out in 2012. Are you really saying that nobody used Python3 for the first 4 years of its existence? I was certainly usi

by opencl 9y ago

Python 3.0 came out in 2008 and 3.3 came out in 2012. Are you really saying that nobody used Python3 for the first 4 years of its existence? I was certainly using 3.1 and 3.2 back then.

sametmax 9y ago
Pretty much yes. Some Linux distrib where still using 2.6, and not a lot of them had even 3.2 in their packages. Only a few like you and me tried it. I can't recall of any big project or lib ever supporting < 3.3.
- UncleEntity 9y ago
  Blender was using py3k for quite a while before 3.3. I was doing blender dev work back then and can recall the almost immediate upgrades as soon as the newest python release came out -- kind of painful really since I prefered to use the fedora installed version instead of building from scratch so would often stall my dev work until fedora caught up to blender. They jumped on so early the python devs were saying "WTF are you people thinking?!?"
  - sametmax 9y ago
    Given blender is mostly c bindings and a huge code base, it's kinda impressive, and a good example that it's not an impossible task to migrate even a very hard project, let alone the most common ones.
    - UncleEntity 9y ago
      It wasn't a migration as much as a bottom-up rewrite of the entire bpy and big chunks of blender itself. Most of the bindings are generated by makesrna at compile (compile compile?) time which is fairly simple once you go deep diving into the sources. It actually takes a fair bit of shenanigans to get hand-coded bindings into blender, my last(?) patch was bindings for the kdtree and I had to do some convincing to get that accepted. I'd guess that 99% of bpy is generated bindings. If they stuck with python 2 when they started the initial overhaul they'd probably still be using it since artists are very vocal when their scripts break.
dagw 9y ago
Django never had support for python < 3.3 and numpy and scipy only supported python 3.2 and up. The story is similar for most other packages. So if you where using python with any of its major libraries then python 3 was pretty much useless for you the first 3-4 years.
- collinmanderson 9y ago
  Django had support for 3.2 and 3.3, but not 3.0 and 3.1. Django didn't add support for 3.x until it was able to drop 2.5 (Feb 2013). https://docs.djangoproject.com/en/2.0/faq/install/#what-python-version-can-i-use-with-django https://docs.djangoproject.com/en/2.0/faq/install/#what-pyth...

by opencl 9y ago

Python 3.0 came out in 2008 and 3.3 came out in 2012. Are you really saying that nobody used Python3 for the first 4 years of its existence? I was certainly using 3.1 and 3.2 back then.

sametmax 9y ago

Pretty much yes. Some Linux distrib where still using 2.6, and not a lot of them had even 3.2 in their packages. Only a few like you and me tried it. I can't recall of any big project or lib ever supporting < 3.3.

UncleEntity 9y ago
Blender was using py3k for quite a while before 3.3. I was doing blender dev work back then and can recall the almost immediate upgrades as soon as the newest python release came out -- kind of painful really since I prefered to use the fedora installed version instead of building from scratch so would often stall my dev work until fedora caught up to blender. They jumped on so early the python devs were saying "WTF are you people thinking?!?"
- sametmax 9y ago
  Given blender is mostly c bindings and a huge code base, it's kinda impressive, and a good example that it's not an impossible task to migrate even a very hard project, let alone the most common ones.
  - UncleEntity 9y ago
    It wasn't a migration as much as a bottom-up rewrite of the entire bpy and big chunks of blender itself. Most of the bindings are generated by makesrna at compile (compile compile?) time which is fairly simple once you go deep diving into the sources. It actually takes a fair bit of shenanigans to get hand-coded bindings into blender, my last(?) patch was bindings for the kdtree and I had to do some convincing to get that accepted. I'd guess that 99% of bpy is generated bindings. If they stuck with python 2 when they started the initial overhaul they'd probably still be using it since artists are very vocal when their scripts break.

dagw 9y ago

Django never had support for python < 3.3 and numpy and scipy only supported python 3.2 and up. The story is similar for most other packages. So if you where using python with any of its major libraries then python 3 was pretty much useless for you the first 3-4 years.

collinmanderson 9y ago
Django had support for 3.2 and 3.3, but not 3.0 and 3.1. Django didn't add support for 3.x until it was able to drop 2.5 (Feb 2013). https://docs.djangoproject.com/en/2.0/faq/install/#what-python-version-can-i-use-with-django https://docs.djangoproject.com/en/2.0/faq/install/#what-pyth...