Lorenzo Angeli

Thanks to all your feedback and bug reports, we are finally getting closer to a final release of the upcoming api 2.0 for python2/3 . If you want to install (at your own risk) the latest RC2 version please use the following command: pip install ftrack-python-api==2.0.0rc2 Full change log can be found here please report through the usual channels any issue or bug you might be finding. Cheers. L.

I'd suggest to stick to C7 as long as possible atm. By direct experience C8 is not ready yet for production. L.

@Nero Demaerschalk, Centos 8 is something we'll be looking into as soon as the distro is stable for desktop use (I'd suggest waiting more than .1 release) For python3 we have a dedicated thread in the forum at this address, feel free to test and let us know if you find any issue. We are working in these days to release a new api 2.0 for python 2 and python 3 for wider use, but the inclusion in connect will require more time due to some non backward compatible changes in the api. Hope it helps. L.

Hi @jen_at_floyd, there's a patch already merged in connect to mitigate this and it'll be available in an upcoming version of connect.

Hi @Paulo Nemotothanks for reporting, would you mind sending the same information and a higher resolution image to support@ftrack.com so we can further investigate ? Thanks a lot, I'll keep you posted on the status. L.

Hi @Tilt , having the python version to >= 2.7.9 has always been a soft requirement for the api, but was never enforced through the installation process itself. Once the amount of issues raised by having python not correct has got to an alarming level we decided to raise the requirement to hard. My suggestion would be to install a newer version of python on C7 (quite a straight forward process). Hope it helps. L.

Hi @Chandler there no boilerplate at the moment, but I'll try to find time new year to come up with one. As you find out though, there was one once, and is the one I'll try to bring back to life or close to what that was at least. Hope it helps. L.

Hi @Alican you cannot use the location.get_url(component) as path for the component as is relative to the server, path requires to be a local path to your file system. What you might be after, if I'm getting it right , is an event which collect the data which might have been manually uploaded and then transfer them first to you local disk , before being re uploaded as reviewable. For this to work , you need to have a listener running which will intercept the update event for components and use that to move the data from the ftrack.server to the local storage. Something along these lines should work (https://bitbucket.org/snippets/ftrack/ynxGp4) Hope it helps. L.

HI @Alican just gave it a go with default connect and actions and I can see them appearing on both Chrome instances I've open (application launchers). May I ask where the actions are hosted ? On each ftrack-connect-package plugin folder (local to the user) , in a shared place and mapped through FTRACK_CONNECT_PLUGIN_PATH / FTRACK_EVENT_PLUGIN_PATH or are running as standalone event listeners ? Also, to help us investigate, removing custom events and actions does still trigger your issue ? Looking forward to hear more from you . L.

Download 0.2.3 Originally written by Mike Datsik What's new * Ensure loads correctly under latest version of houdini (18.0) * Update to latest QtExt to Fix QStringListModel compatibility for PySide2 5.9+. * Update plugin built for pip 19+ * Update icon path How to install stop ftrack-connect-package download and uncompress the new version in : <ftrack-connect-package>/resource/connect-standard-plugins/ restart ftrack-connect-package

HI @Dimitri Lucy, glad to hear ! let us know if anything else comes up L.

Hi @Dimitri Lucy, whenever you are manipulating the PYTHONPATH I suggest extending it rather than overwriting it with something like : PYTHONPATH=%PYTONPATH%:C:\Python27\Lib\site-packages\ftrack_api On the error you are having though, seems to me that you are installing the new api , but trying to import the legacy ones. Could you please try to import ftrack_api rather than ftrack ? Let us know how it goes ! Cheers. L.

HI @Mani Varma, If all you need is an efficient api to represent a tree I'd suggest having a look at this widget from connect. It does use a qtmodel which is quite efficient. Hope it helps. L.

HI @Milan Kolar, Thanks for reporting it. I wasn't aware you were already using it ! Be aware that some breaking changes (session won't connect automatically to the event hub) are coming soon on the story branch so be careful. Feel free to get in touch through support to share any stack trace you might be getting. Cheers. L.

Hi @Julian Martinz looks like we are on the same page now let us know how it goes! L.