Change of Python Integration



  • On 15/07/2015 at 05:27, xxxxxxxx wrote:

    With the next major version Cinema 4D R17 (SP1 to be precise) we will move from Python 2.6.4 to Python 2.7.9.
    From then on Python 2.6.4 will not be used anymore.

    The reason for this decision were minor issues in Python 2.6 and increased compatibility with other 3D packages.

    In most cases this change should be no problem. Tests with existing scripts/plugins showed, almost
    all scripts, plugins, etc. are compatible with Python 2.7. Only in very rare cases adjustments need to be made.

    Note for Custom compiled Python C-modules:
    If a plugin is based on a Python C-module, this module needs to be recompiled. Latest Xcode version and Visual Studio 2012 SP4 should be used for this.

    New in Python 2.7
    Detailed changelog of Python 2.7.9



  • On 15/07/2015 at 05:56, xxxxxxxx wrote:

    Same goes for byte-compiled Python code. You can do something like this

    if sys.version.startswith('2.7') :  
      module_path = 'res/modules_27'
    else
      module_path = 'res/modules_26'
      
    with _localimport(module_path) :  
      import module_a
      import module_b
    

    More info on Third Party Modules in Plugins can be found here.



  • On 31/08/2015 at 22:06, xxxxxxxx wrote:

    Hello

    I test several cython and with numpy/scipy plugins

    got errors with finding of Python.h and etc. Dead

    Who moved headers from:
    resource\modules\python\Python.win64.framework\ include
    to:
    resource\modules\python\Python.win64.framework\include\ **python27

    ** and why? **😉

    ** p.s. libs same, resource\modules\python\Python.win64.framework\libs\



  • On 01/09/2015 at 01:11, xxxxxxxx wrote:

    Hi,

    Originally posted by xxxxxxxx

    I test several cython and with numpy/scipy plugins

    got errors with finding of Python.h and etc. Dead

    Who moved headers from:
    resource\modules\python\Python.win64.framework\ include
    to:
    resource\modules\python\Python.win64.framework\include\ **python27

    ** and why? **😉

    ** p.s. libs same, resource\modules\python\Python.win64.framework\libs\

    We're sorry we didn't revealed that the python includes are now in a "python27" subfolder in R17.
    But this isn't a big issue. The paths can be changed in your project and that fix it.



  • On 01/09/2015 at 01:27, xxxxxxxx wrote:

    Thanks.
    I caught it when installing of scipy wheel. I copy headers.
    I thought it will be something new... probably methods to switch between different versions of python.

    P.s.

    We're sorry we didn't revealed that the python includes are now in a "python27" subfolder in R17.

    Yannick
    Does it fit to standards of python distribution?
    for example to install cython or py modules like in install packages



  • On 08/09/2015 at 05:10, xxxxxxxx wrote:

    Hello
    Me again.
    I wanna say thanks a'lot to teams for new python core!👏🍺
    I'm glad as little child! Sorry for such expression of feelings!

    Primitive test

    _<_img src="http://www.c4dcafe.com/ipb/uploads/monthly_2015_09/fb.png.25cf3095814cdf9e7020d94cd236be83.png" border="0" /_>_



  • On 08/09/2015 at 05:20, xxxxxxxx wrote:

    Great job! Nice to see it's working.
    Btw, the headers were moved to python2.7 so includes are now more future proove.

    #include "python27/Python.h"



  • On 08/09/2015 at 05:31, xxxxxxxx wrote:

    Hello Sebastian. Thanks a'lot for hard job!
    No-no, i simply modify FabricEngine\Samples\EDK\HelloWorld est.py
    adding c4d stuff and simplify node-operator(to string, without externals)

    I rethink about Python.win64.framework , made another dir py27_vc11 as source for compilation of 3dparty stuff and use User-Dir python for store of 3dparties modules
    or use mingw



  • On 08/09/2015 at 05:40, xxxxxxxx wrote:

    Very Cool Ilya! Will you share the Fabric Engine binaries?



  • On 08/09/2015 at 05:47, xxxxxxxx wrote:

    Originally posted by xxxxxxxx

    Very Cool Ilya! Will you share the Fabric Engine binaries?

    Not cool. 😉 I copy&paste
    About binaries, i used native python modules which include in beta FB 2.0. I copy to user dir.
    I think you can to ask Fabric team to beta-testing, at their site. http://fabricengine.com/get-fabric



  • On 21/10/2016 at 14:11, xxxxxxxx wrote:

    Is there a pyside binary that works with R17?
    I'm guessing I'll have to compile this my self?



  • On 21/10/2016 at 14:20, xxxxxxxx wrote:

    P.s i'm trying a pip install now... hope fully that works...


Log in to reply