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.
Interestingly, the docs from Microsoft are not afraid to say that there is an underlying "bridge" from python to .Net:
Source:
Please let me know how I might create a similar library for python (a lightweight wrapper around the "real code" that lives in .Net).
I'm assuming the bridge is entirely local, on the spark driver, and it is not a client connection via TCP to a different compute node. Else the verbage here would be considerably different than it is (and the callstacks would be a lot more complex, in the underlying exception details).