Environment Python paths are not appended to ftrack_connect_package
2 2

3 posts in this topic

Hi all,

is there any reason why the Python paths from environment are not appended to the compiled ftrack_connect_package (v0.5.0) when is launched?

If I create a simple action which print the sys.path I get this:

.../ftrack/3.3.31/connect/0.5.0/centos-6_x86-64/common.zip
.../ftrack/3.3.31/connect/0.5.0/centos-6_x86-64/ftrack_connect_package
.../ftrack/3.3.31/connect/0.5.0/centos-6_x86-64
.../ftrack/3.3.31/connect/0.5.0/centos-6_x86-64/ftrack_connect_package.zip
.../ftrack/3.3.31/connect/0.5.0/centos-6_x86-64/library.zip
.../ftrack/3.3.31/connect/0.5.0/centos-6_x86-64/common.zip/FTrackCore.egg


Even the python build in modules are not there. For example 'HTMLParser'.

Am I doing something wrong?

Share this post


Link to post
Share on other sites

Hi Remus,

We're using a library called cx_Freeze to create the executable. As part of the build step it excludes modules that are not used by the application. This is all fine if you have a "static" application, but in our case where we load plugins into the application it becomes a limit.

In the build step of ftrack-connect-package there are ways to force adding modules. We do this with e.g. the csv modules.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
2 2