Victor
Victor
@filmor we also scan already loaded assemblies. E.g. `AppDomain.CurrentDomain.GetAssemblies()`
@filmor upon initialization of Python.NET you can call that method and ensure there is only one Python.Runtime loaded, or throw otherwise.
This check can go in many places. For instance, you could use `PyObject` static constructor. Or you could add this check to `AssemblyManager.ScanAssembly`
I don't think there's anything for us to fix here. This is an unsupported situation. Detect and raise.
Please, split smaller fixes into individual PRs (e.g. #1776). I'd rather have #1774 also have its own PR as the code does not seem to be interdependent.
@rmadsen-ks btw generally speaking the code down at that level should not be using `PyObject` unless strictly necessary. Instead, `BorrowedReference` and `NewReference` should be used in conjunction with `Runtime.Py...` methods.
I found a workaround for this issue: you can use [`GetShortPathName` function](https://learn.microsoft.com/en-us/windows/win32/api/fileapi/nf-fileapi-getshortpathnamew) to generate a DOS-compatible name, and that name will work.
@sp00n if I'd be guessing I'd say it would not work for relative paths, but should have worked for absolute ones.
@LeoDavidson AFAIK by default they are on on NTFS and AFAIK ReFS can not be booted from. I can't imagine even 0.1% of all Windows users turning them off, so...
@sp00n AFAIK off on ReFS