![]() ![]() Many times this is while sitting with a director, production designer, manager, or client. Offer ends August 16, 2019.Many of our LightWave 3D® users work daily in situations where they need to make iterative modifications to models from a real world camera. ![]() We will answer in the forum and also update the blog entry with the information.Īnd if you haven’t seen it yet, here’s the information on LightWave 3D 2019.1:įor a limited time, registered users of any earlier LightWave version can upgrade to 2019.1 for US$395, less VAT. ![]() LightWave 3D General Techniques, Tips and Tricks Forum Section If you have questions about the information, images and videos we share in a LightWave 3D blog entry, just drop your questions into the forum here: There are language-based methods for making your existing Python v2 scripts function within both environments ( ), as well as external tools that can help promote v2 scripts to Python v3 compatibility (e.g., ). However, we are providing this roadmap more than a year ahead of time so customers can start considering how it will impact their existing pipelines and assets. To be sure, this will be a major change in the scripting support of LightWave. This EOL version will continue to be included in LightWave through the lifespan of the next major release-which means it will be present in any patches provided for it-but it will be completely replaced with the latest release of Python v3 in subsequent major releases of LightWave. Of course, all of this has a singular implication for users of LightWave Python: The next major release of LightWave will also be the last version to support Python v2. However, if timing prevents the final Python v2 patch from being incorporated into a major release, it will be included in a nearby patch version. This final patch release of Python v2 may fall within the time frame of the next major release of LightWave. As of next January, Python v2 will be cut adrift by the Python development team to float away into the sunset, with no further official support. Well, v3 is now quite mature, so there will be no more reprieves for Python v2. Python v2 was scheduled for EOL in 2015 by, but was extended for a 5-year period to provide time for v3 to mature, and to give users time to migrate. This looming EOL date is actually 5 years longer than originally planned. At that time, this version of Python will have officially and finally reached its end-of-life (EOL), and will receive no further patches, whether to correct defects, or to address security vulnerabilities (e.g., ). However, come January 2020, Python v2 is scheduled to have its last patch released (2.7.18). Not everybody keeps their fingers directly on the pulse of the Python community nor on its current events. If this comes as a surprise, that’s quite understandable. ![]() However, a change is on the horizon, one for which all LightWave™ Python users need to prepare: The demise of Python v2. I think I can say without fear of contradiction that Python has enjoyed a long and successful pairing with LightWave 3D®. By Bob Hood, Director of 3D Engineering, NewTek ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |