Sat, Feb 1, 2:37 PM CST

Renderosity Forums / Poser Python Scripting



Welcome to the Poser Python Scripting Forum

Forum Moderators: Staff

Poser Python Scripting F.A.Q (Last Updated: 2024 Dec 02 3:16 pm)

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: from __future__ import print_function & other Python 3 compatibility issues


an0malaus ( ) posted Mon, 12 August 2019 at 7:20 AM · edited Wed, 08 January 2025 at 4:37 PM

Since virtually all of my Python experience has been within the realm of Poser (with the exception of uncompyle explorations), I am less than comfortably familiar with the differences between 2.7 & 3.x. I see others who appear to religiously future-proof their code by adopting the python 3 style print() function, rather than the 2.x era print statement, but are there many other gotchas that are likely to bite us when [ahem, h*ck-ptooie] the new devs catch a whiff of that new kool-aid and shoehorn Python 3 up Poser's back passage/addons framework?



My ShareCG Stuff

Verbosity: Profusely promulgating Graham's number epics of complete and utter verbiage by the metric monkey barrel.


adp001 ( ) posted Mon, 12 August 2019 at 12:59 PM

I'm using the print function with 2.7 since it is available. Reason: In (old) 2.7 "print" is a statement. It can not be used in an expression. Think of something like this:

print("Enough") if a >10000 else make_more_money() #:)


If Poser changes to 3.x, lots of old scripts should go down (even newest Cinema 4D is still with 2.7 for the same reason). I think Poser will stay with 2.7 for the next few [years|centuries]. What I hope for: A recent version of wxPython. Working with graphics within the actual implementation is a pain in the ass.




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.