Timeline for How to make Blender use Python2.x?
Current License: CC BY-SA 3.0
17 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 7, 2017 at 22:11 | answer | added | Ajmal Kunnummal | timeline score: 0 | |
| Jan 29, 2015 at 19:07 | history | edited | ideasman42 | CC BY-SA 3.0 | edited title |
| Jun 9, 2013 at 14:30 | answer | added | ogeid | timeline score: 0 | |
| Jun 1, 2013 at 21:07 | comment | added | zeffii | @Gwenn might want to look into VirtualEnv, so you can have several python installations going on. | |
| Jun 1, 2013 at 17:41 | history | tweeted | twitter.com/#!/StackBlender/status/340885847043874817 | ||
| May 31, 2013 at 16:12 | comment | added | ideasman42 | Python3.x was being release about the same time blender was undergoing a complete api rewrite (which meant we had to rewrite all our scripts anyway), we had had trouble supporting multiple python versions already (2.4x -> 2.6x), so we made the move to a single, bundled Python version - and using Python3.x was a good choice to avoid yet-another rewrite/update later on. | |
| May 31, 2013 at 16:02 | comment | added | Gwen | I use Python 2.x for my work doing desktop application design, and I haven't yet switched over all of my code/packages/IDE to Python 3.x. I'll have to switch over sometime, but until then I would like to use the same version of Python for all of my coding projects. | |
| May 31, 2013 at 15:57 | comment | added | ideasman42 | Out of curiosity, can you say why you want to use Python2.x ? | |
| May 31, 2013 at 3:04 | vote | accept | Gwen | ||
| S May 31, 2013 at 3:02 | history | suggested | CommunityBot | CC BY-SA 3.0 | kill mixed caps in title |
| May 31, 2013 at 2:59 | review | Suggested edits | |||
| S May 31, 2013 at 3:02 | |||||
| May 26, 2013 at 16:15 | answer | added | Gwen | timeline score: 1 | |
| May 25, 2013 at 19:10 | history | edited | JNF | edited tags | |
| May 25, 2013 at 13:46 | history | edited | CharlesL | CC BY-SA 3.0 | fixed grammar |
| May 25, 2013 at 7:27 | comment | added | zeffii | Maybe you would like to clarify what bit of python 2 is more comfortable than python 3. I know plenty of people who took a long time to step over to py3, but eventually concluded that their original resistance could only be justified in a select set of scenarios (like some modules not being available for py3 - yet) Is it the print() statement? the try-except stuff? or the xrange vs range?. Progress to py3 is inevitable, for many use cases it is faster and has more conveniences. | |
| May 24, 2013 at 22:02 | answer | added | jesterKing | timeline score: 29 | |
| May 24, 2013 at 21:56 | history | asked | Gwen | CC BY-SA 3.0 |