Forum Discussion
A bumpy journey with .Net (beneath the semantic-link/sempy library for python)
- 1 year ago
dbeavon3, Thank you for your continued engagement and feedback.
we want to provide you the best possible guidance to help you achieve your goals. Microsoft has not provided any documentation or best practices for modifying or extending this bridge and we do not recommend modifying the sempy library itself or creating a custom bridge unless you have extensive experience in both Python and .NET
As above mentioned, Microsoft's official support for such functionality is limited we recommend to submit your ideas here to Fabric team: https://ideas.fabric.microsoft.com/ideas/search-ideas/
Thanks,
Prashanth Are
MS Fabric community support.
I was able to find one of the engineers (in a github community) It sounds like there is in fact a dependency on .net under the covers. In addition they use the AdomdClient from .Net. And I believe they said pythonnet for the interop.
For the AdomdClient, they use the public nuget variety of the package, and it is not a home-grown integration with datasets. (That is a relief.)
Oddly the sempy library isn't fully supported from vscode (local development) or from other compute platforms like databricks.
... Given that the building blocks seem to be fairly standard ones, it seems like the team should be able to support this sempy library elsewhere. But I'm guessing there are only some minor reasons why they don't want to support it everywhere (eg. dependencies on fabric's "notebookutils" for getting access token). Or maybe they aren't prepared to keep up a regular cadence of changes to the pypi public library.