Post #2563356
2024-08-27 16:29 UTC
@corbin@defcon.social @stargirl@hachyderm.io Maybe I should elaborate: imagine you have a project that uses protobuf-python, and you want to use it together with tensorflow. Chances are, tensorflow's outdated protobuf does not work for you. Rather trying to patch your project or patch tensorflow for compatibility with the older/newer protobuf, I'd want a solution where we instruct python to resolve `import protobuf` into one "package" when the import happens under `${prefix}/tensorflow`, and another package elsewhere
Replies (1)
-
@nobody@mastodon.acm.org 2024-08-27 16:31
@corbin@defcon.social @stargirl@hachyderm.io There's two obvious challenges: 1) multi-tenancy support in python import cache (needs implementing), 2) potential symbol collision issues for native libraries (potentially solved by dlmopen, I suspect, but maybe not on windows and what do I know actually)