Open mgiammaria-phd opened 2 months ago
In this case, you're importing a C# library into the Python wrappers. If you check the tableau_migration/bin folder (where the Python library is installed), you should see Tableau.Migration.dll there, which contains this particular function reference.
This is a correct import for Python.net interop. In this case we're invoking ServerToCloudPipeline.ContentTypes the next line down to loop over the supported content types.
We currently don't wrap static field/properties in Python because the equivalent in Python (class properties) were deprecated in 3.11. I understand the source of confusion, and we do consider Python.net invocations "advanced usage" that we try to avoid in our samples. I'll bring this up to the team and we'll discuss options.
Hi Team, in the Python.ExampleApplication folder, within the print_result.py method it is included the library Tableau.Migration.Engine.Pipelines to import ServerToCloudMigrationPipeline It seems that this specific library is missing in the current release 4.3.1 and previous for python. It is an uncorrect migration from C# developing maybe. It seems that also the documentation does not report such python library: From Python API Reference From C# API Reference