Dear Flow Production Tracking (FPTR) Community,
FPTR integrations running on Python 3.7 will no longer be supported starting March 1st 2025. We are required to take this step to align with the Python 3.7 End Of Life from June 2024. After February 2025, users running FPTR Toolkit pipelines and integrations with Python 3.7 will no longer receive support. Eventually, after this date, new Toolkit component versions will break compatibility with Python 3.7.
For FPTR desktop users, ShotGrid Desktop 1.7 will no longer be supported after February 2025 because it is the last version supporting Python 3.7, forcing the end of support of this version.
If your studio currently uses Python 3.7, please migrate to one of the supported Python versions (3.9 and later) before the end of February 2025. We recommend using the latest supported Python version (3.11).
For the FPTR desktop application, please update to version 1.8 as a minimum before the end of February 2025. We recommend migrating to version 1.9 or later, if possible.
For more information about the currently supported versions of Python and FPTR desktop, visit our Platform Supported Versions document. Upgrading should not introduce any breaking changes, but we always recommend you proceed with care, testing all your critical workflows before propagating the changes more broadly.
We acknowledge that this change could be disruptive, but updating our products to the latest standards is required for Autodesk to deliver secure software.
F.A.Q.
What will happen on March 1st, 2025?
Autodesk will stop providing support to users on Python 3.7 and/or ShotGrid Desktop 1.7.
New versions of Toolkit components will not support Python 3.7.
Why are you discontinuing Python 3.7?
Python 3.7 reached End-Of-Life on June 2024. For security reasons, Autodesk can no longer provide support for this version.
Why are you discontinuing ShotGrid Desktop 1.7.X?
ShotGrid Desktop 1.7 shipped with Python 2.7 and 3.7. As both of these Python versions will be unsupported by March 2025, we can no longer provide support for ShotGrid Desktop 1.7.
What about previous versions of ShotGrid Desktop?
Autodesk has stopped supporting ShotGrid Desktop versions earlier than 1.7 ever since the drop of support for Python 2.
For more information about the currently supported versions, visit our Platform Supported Versions document.
I am using FPTR Toolkit with Python 3.9/3.10/3.11, am I impacted by this change?
No.
But please have a look at the point below about DCC versions.
I am using ShotGrid Desktop 1.8 or FPTR desktop 1.9+, am I impacted by this change?
No.
But please have a look at the point below about DCC versions. Also, please check that none of your project’s configs is using Python 3.7.
Will this change affect the support of Toolkit engines (for DCCs)?
Yes, DCC versions using Python 3.7 will no longer be supported after February 2025.
Current supported DCC versions including Python 3.7 are the following:
- 3dsMax 2022
- Flame 2022
- Houdini 18.5 and 19.0
- Mari 5.0x
- Maya 2022
- Motion Builder 2022
- Nuke 13.X
- VRED 2022
These versions will no longer be supported after February 2025.
For more information about the currently supported engines, visit our Engine Supported Versions document.
Which Python versions are currently supported for FPTR Toolkit?
Autodesk supports the following Python version for FPTR Toolkit:
- Python 3.11 (CY2024)
- Python 3.10 (CY2023)
- Python 3.9 (CY2022)
- Python 3.7 (CY2021) - End of support Feb 28th 2025
Up-to-date information can be found in our Platform Supported Versions document.
Which ShotGrid Desktop/FPTR desktop versions are currently supported?
Autodesk support the following versions:
- FPTR desktop 1.9
- ShotGrid Desktop 1.8
- ShotGrid Desktop 1.7 - End of support Feb 28th 2025
Up-to-date information can be found in our Platform Supported Versions document.
I need to continue using Python 3.7, what should I do?
While integrations using Python 3.7 may not stop functioning immediately, Autodesk will no longer be able to support users using these versions. Over time, that may lead to an integration that stops working. You will also stop receiving important fixes and security updates, potentially putting you and your company at risk.
If you wish to continue using an unsupported integration, make sure to disable automatic component updates to avoid disruptions.
I migrated to Python 3.9/3.10/3.11 but my pipeline is now broken
This is not expected so please open a case with support, making sure to include all related configuration details.
Review any custom scripts and hooks in your configuration and workflow.
Don’t hesitate to reply in this thread if you have questions, or reach out to our support team.
The Flow Production Tracking Team