Give more explicit ImportErrors #261
Milestone
Comments
|
related? #111 |
|
Could be. I just recognised this today as a problem, when I (again) had to do an |
|
@filmor the problem is that some third-party packages try to import some libraries and have backup logic if no success. So how would we distinguish between package -handled and -unhandled imports? |
|
We should still raise an import error, we should just add information to the message, which assembly could not be loaded and why, basically the information that the.NET exception contains. |
|
what I meant is actually cases like this and we would bug down the user with optional imports failing: https://github.com/pydata/pandas/blob/master/pandas/computation/__init__.py |
|
10000
That's not what I'm saying, I'm suggesting keeping the |
|
@filmor agreed! we need to extend the passed information. |
fdanny
pushed a commit
to fdanny/pythonnet
that referenced
this issue
Dec 1, 2016
…missing dependencies with ImportError Exceptions
fdanny
pushed a commit
to fdanny/pythonnet
that referenced
this issue
Dec 2, 2016
vmuriart
pushed a commit
to vmuriart/pythonnet
that referenced
this issue
Feb 22, 2017
…missing dependencies with ImportError Exceptions
vmuriart
pushed a commit
to vmuriart/pythonnet
that referenced
this issue
Feb 22, 2017
vmuriart
pushed a commit
to vmuriart/pythonnet
that referenced
this issue
Feb 22, 2017
…missing dependencies with ImportError Exceptions
vmuriart
pushed a commit
to vmuriart/pythonnet
that referenced
this issue
Feb 22, 2017
lostmsu
added a commit
to losttech/pythonnet
that referenced
this issue
Mar 4, 2020
…ore info when CLR assemblies are failed to be loaded 1. When trying to implicitly load assemblies, and that fails NOT because an assembly is missing, but because loading failed for some reason, emit Python warning. 2. When trying to import a module in our import hook, if the module name is an assembly name, and we fail to load it, and Python also fails to find a module with the same name, add the exceptions we got during the attempt to load it into __cause__ of the final ImportError BREAKING: clr.AddReference will now throw exceptions besides FileNotFoundException. Additional: a few uses of BorrowedReference This addresses pythonnet#261 It is an alternative to pythonnet#298
2 tasks
lostmsu
added a commit
to losttech/pythonnet
that referenced
this issue
Mar 4, 2020
…ore info when CLR assemblies are failed to be loaded 1. When trying to implicitly load assemblies, and that fails NOT because an assembly is missing, but because loading failed for some reason, emit Python warning. 2. When trying to import a module in our import hook, if the module name is an assembly name, and we fail to load it, and Python also fails to find a module with the same name, add the exceptions we got during the attempt to load it into __cause__ of the final ImportError BREAKING: clr.AddReference will now throw exceptions besides FileNotFoundException. Additional: a few uses of BorrowedReference This addresses pythonnet#261 It is an alternative to pythonnet#298
lostmsu
added a commit
to losttech/pythonnet
that referenced
this issue
Apr 23, 2020
…ore info when CLR assemblies are failed to be loaded 1. When trying to implicitly load assemblies, and that fails NOT because an assembly is missing, but because loading failed for some reason, emit Python warning. 2. When trying to import a module in our import hook, if the module name is an assembly name, and we fail to load it, and Python also fails to find a module with the same name, add the exceptions we got during the attempt to load it into __cause__ of the final ImportError BREAKING: clr.AddReference will now throw exceptions besides FileNotFoundException. Additional: a few uses of BorrowedReference This addresses pythonnet#261 It is an alternative to pythonnet#298
|
@filmor the right way to do it is to enable Fusion Log on Windows or set Mono debug environment variables for Mono. |
lostmsu
added a commit
to losttech/pythonnet
that referenced
this issue
Apr 27, 2020
…ore info when CLR assemblies are failed to be loaded 1. When trying to implicitly load assemblies, and that fails NOT because an assembly is missing, but because loading failed for some reason, emit Python warning. 2. When trying to import a module in our import hook, if the module name is an assembly name, and we fail to load it, and Python also fails to find a module with the same name, add the exceptions we got during the attempt to load it into __cause__ of the final ImportError BREAKING: clr.AddReference will now throw exceptions besides FileNotFoundException. Additional: a few uses of BorrowedReference This addresses pythonnet#261 It is an alternative to pythonnet#298
lostmsu
added a commit
to losttech/pythonnet
that referenced
this issue
May 13, 2020
…ore info when CLR assemblies are failed to be loaded 1. When trying to implicitly load assemblies, and that fails NOT because an assembly is missing, but because loading failed for some reason, emit Python warning. 2. When trying to import a module in our import hook, if the module name is an assembly name, and we fail to load it, and Python also fails to find a module with the same name, add the exceptions we got during the attempt to load it into __cause__ of the final ImportError BREAKING: clr.AddReference will now throw exceptions besides FileNotFoundException. Additional: a few uses of BorrowedReference This addresses pythonnet#261 It is an alternative to pythonnet#298
lostmsu
added a commit
to losttech/pythonnet
that referenced
this issue
Aug 18, 2020
…ore info when CLR assemblies are failed to be loaded 1. When trying to implicitly load assemblies, and that fails NOT because an assembly is missing, but because loading failed for some reason, emit Python warning. 2. When trying to import a module in our import hook, if the module name is an assembly name, and we fail to load it, and Python also fails to find a module with the same name, add the exceptions we got during the attempt to load it into __cause__ of the final ImportError BREAKING: clr.AddReference will now throw exceptions besides FileNotFoundException. Additional: a few uses of BorrowedReference This addresses pythonnet#261 It is an alternative to pythonnet#298
lostmsu
added a commit
to losttech/pythonnet
that referenced
this issue
Aug 18, 2020
…ore info when CLR assemblies are failed to be loaded 1. When trying to implicitly load assemblies, and that fails NOT because an assembly is missing, but because loading failed for some reason, emit Python warning. 2. When trying to import a module in our import hook, if the module name is an assembly name, and we fail to load it, and Python also fails to find a module with the same name, add the exceptions we got during the attempt to load it into __cause__ of the final ImportError BREAKING: clr.AddReference will now throw exceptions besides FileNotFoundException. Additional: a few uses of BorrowedReference This addresses pythonnet#261 It is an alternative to pythonnet#298
lostmsu
added a commit
to losttech/pythonnet
that referenced
this issue
Aug 18, 2020
…ore info when CLR assemblies are failed to be loaded 1. When trying to implicitly load assemblies, and that fails NOT because an assembly is missing, but because loading failed for some reason, emit Python warning. 2. When trying to import a module in our import hook, if the module name is an assembly name, and we fail to load it, and Python also fails to find a module with the same name, add the exceptions we got during the attempt to load it into __cause__ of the final ImportError BREAKING: clr.AddReference will now throw exceptions besides FileNotFoundException. Additional: a few uses of BorrowedReference This addresses pythonnet#261 It is an alternative to pythonnet#298
lostmsu
added a commit
to losttech/pythonnet
that referenced
this issue
Aug 18, 2020
…ore info when CLR assemblies are failed to be loaded 1. When trying to implicitly load assemblies, and that fails NOT because an assembly is missing, but because loading failed for some reason, emit Python warning. 2. When trying to import a module in our import hook, if the module name is an assembly name, and we fail to load it, and Python also fails to find a module with the same name, add the exceptions we got during the attempt to load it into __cause__ of the final ImportError BREAKING: clr.AddReference will now throw exceptions besides FileNotFoundException. Additional: a few uses of BorrowedReference This addresses pythonnet#261 It is an alternative to pythonnet#298
lostmsu
added a commit
to l
7C3B
osttech/pythonnet
that referenced
this issue
Aug 18, 2020
…ore info when CLR assemblies are failed to be loaded 1. When trying to implicitly load assemblies, and that fails NOT because an assembly is missing, but because loading failed for some reason, emit Python warning. 2. When trying to import a module in our import hook, if the module name is an assembly name, and we fail to load it, and Python also fails to find a module with the same name, add the exceptions we got during the attempt to load it into __cause__ of the final ImportError BREAKING: clr.AddReference will now throw exceptions besides FileNotFoundException. Additional: a few uses of BorrowedReference This addresses pythonnet#261 It is an alternative to pythonnet#298
lostmsu
added a commit
that referenced
this issue
Aug 19, 2020
…ore info when CLR assemblies are failed to be loaded 1. When trying to implicitly load assemblies, and that fails NOT because an assembly is missing, but because loading failed for some reason, emit Python warning. 2. When trying to import a module in our import hook, if the module name is an assembly name, and we fail to load it, and Python also fails to find a module with the same name, add the exceptions we got during the attempt to load it into __cause__ of the final ImportError BREAKING: clr.AddReference will now throw exceptions besides FileNotFoundException. Additional: a few uses of BorrowedReference This addresses #261 It is an alternative to #298
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, an
ImportErrorraised from Python.NET does not include information on the actual dependency that failed to load.The text was updated successfully, but these errors were encountered: