Here are some links that may possibly useful as a quickstart for the Poser 11 to Poser 12 leap, and the need to tweak PoserPython scripts so they conform with Python version 3.<\/p>\n
1.<\/strong> The official 2to3 – Automated Python 2 to 3 code translation<\/a>.<\/p>\n 2.<\/strong> Futurize<\/a> calls in 2to3 and uses it to do automatic conversion of Poser 2 to Poser 3…<\/p>\n The futurize script passes Python 2 code through all the appropriate fixers to turn it into valid Python 3 code, and then adds __future__ and future package imports to re-enable compatibility with Python 2.<\/p><\/blockquote>\n 3.<\/strong> Python-Modernize<\/a> also calls in 2to3 and uses it to make…<\/p>\n a very thin wrapper around lib2to3 to utilize it to make Python 2 code more modern with the intention of eventually porting it over to Python 3.<\/p><\/blockquote>\n What breaks?<\/strong> <\/p>\n * It seems that the command print<\/strong> is handled differently in Python 3 scripts. So are strings<\/strong>. The way that iterated lists<\/strong> are done also seem to have changed. There’s a comparison page here<\/a>.<\/p>\n * Standard library Python ‘packages’ or ‘modules’, of the sort called in by a simple name placed at the top of some scripts, have been moved or renamed or lower-cased. There’s a list<\/a> on which Tkinter<\/strong> is now tkinter<\/strong>, and SimpleDialog<\/strong> is now tkinter.simpledialog<\/strong>. Tkinter is only relevant for Windows users, as Apple bans it from the Mac. It’s used in PoserPython to make user interfaces for scripts. I don’t recognise any of the others.<\/p>\n * Not only will Tkinter scripts need to have their in-script Tkinter ‘module call’ lower-cased to read tkinter, but on Poser 12 we may also have to download the latest Python and “then copy the tkinter directory, and the tcl8.6 and tk8.6 directories to the runtime\/python\/lib directory” of Poser 12.<\/p>\n
\n