ID 381596 - Mari fails to open a project via the API when the colorspace differs from the one set in the project.

Problem summary
Mari fails to open a project via the API when the colorspace differs from the one set in the project.

Customer reported version

Customer reported platform
centos6

Steps to reproduce

1) Open Mari and the Example Project

2) Make sure that the colorspace is set to nuke-default, save the project and close Mari 

3) Change the OCIO environment variable to point to a different than nuke-default colorspace

4) Open Mari and in the python console execute the following: 

import mari

test = "ExampleProject_4.2"
mari.projects.open(test, mari.projects.AllowedVersions.ANY)
#mari.projects.AllowedVersions.OLDER_OR_EXACT)

Result: The project fails to load and Mari returns the following error: 

Traceback (most recent call last):
  File "<string>", line 4, in <module>
IOError: Project load failed for 'ExampleProject_4.2': 

Workaround
Unknown. 

Reproduced by support
This bug has been reproduced in:

Mari 4.2v2 - CentOS 6.9

Mari 4.2v1 - CentOS 6.9

Mari 4.1v1 - CentOS 6.9

Mari 3.4v4 - CentOS 6.9

Mari 3.4v3 - CentOS 6.9

Mari 3.4v2 - CentOS 6.9

Mari 3.4v1 - CentOS 6.9 - regression

Unable to reproduce bug in:
Mari 4.0v1 - CentOS 6.9

Mari 3.3v1 - CentOS 6.9

Earliest version tested
3.3v1 - This issue no longer appears in this version and has regressed

Expected behaviour
The following pop up window should appear:

​

Actual behaviour
Mari fails to load the project and returns the following error: 

Traceback (most recent call last):
  File "<string>", line 4, in <module>
IOError: Project load failed for 'ExampleProject_4.2':