Tue, Nov 19, 7:40 AM CST

Renderosity Forums / Poser Python Scripting

All Forums

Welcome to the Poser Python Scripting Forum

Forum Moderators: Staff

Poser Python Scripting F.A.Q (Last Updated: 2024 Sep 18 2:50 am)

We now have a ProPack Section in the Poser FreeStuff.
Check out the new Poser Python Wish List thread. If you have an idea for a script, jot it down and maybe someone can write it. If you're looking to write a script, check out this thread for useful suggestions.

Also, check out the official Python site for interpreters, sample code, applications, cool links and debuggers. This is THE central site for Python.

You can now attach text files to your posts to pass around scripts. Just attach the script as a txt file like you would a jpg or gif. Since the forum will use a random name for the file in the link, you should give instructions on what the file name should be and where to install it. Its a good idea to usually put that info right in the script file as well.

Checkout the Renderosity MarketPlace - Your source for digital art content!

Subject: Possible to use Python 2.3 with ProPack?

rrkknight3 opened this issue on Feb 26, 2004 · 4 posts
Back to Forum Print
rrkknight3 ( ) posted Thu, 26 February 2004 at 5:42 AM · edited Thu, 14 November 2024 at 11:39 PM

I keep bumping into unmodern things in ProPack's Python and would like, if it is possible, to replace the 1.5 version with the current one. I've looked a little at the various pieces of Poser Python (DLL's and such) and don't see the obvious spot (other than just dropping a newer pythonxxx.dll in. If someone has already solved this, please let me know.

WeirdJuice ( ) posted Thu, 26 February 2004 at 9:18 AM

We've been looking at exactly the same possibility to improve ProPack performance on our products. Apart from updating the dll in the main Poser directory its likely that ProPack would also benefit from updating the files in the "RuntimePythonDLLs" and "RuntimePythonLibs" directories, especially the older and flakier Tk/Tcl version 8.0. Bill Weird Juice Software

nruddock ( ) posted Sat, 28 February 2004 at 4:17 PM

Most likely to cause problems are the changes between 1.5.2 and 2.0 in the C interface
Quote from What's New in Python 2.0, 11 Extending/Embedding Changes

"The version number of the Python C API was incremented, so C extensions compiled for 1.5.2 must be recompiled in order to work with 2.0. On Windows, it's not possible for Python 2.0 to import a third party extension built for Python 1.5.x due to how Windows DLLs work, so Python will raise an exception and the import will fail."

A minor irritation would be the fact that the poser.exe of ProPack explicitly refers to python15.dll (any replacement could be renamed to suit), but in light of the need to have the poser module recompiled to work with the newer Python, it would seem to be irrelevant.
For anyone who really wants to try this, you might be able to fixup the dll references with a hex editor (a whole bunch of caveats apply, so don't try this at home unless you know what your doing), but again it seems unlikely to work for the reason above.

ockham ( ) posted Mon, 01 March 2004 at 5:35 PM

I tried the renaming trick once, but it didn't work. There are some "magic numbers" in the DLLs that have to match up properly.

My python page
My ShareCG freebies

Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.