-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't view objects in object explorer, when using spyder installer with custom python interpreter #17065
Comments
Maybe adding to this, if the class do not have any methods (is it called methods in python? I mean functions in classes) only variables I can open the object in Object Explorer.
--EDIT-- Is viewing other objects than the supported objects like numpy, pandas and so generally not supported?
I can't look at the object either with installer or installed via conda like stated above Also there is no error message in the normal / internal console --Edit2-- |
Hi @Hawxxer thank you for your feedback! I was unable to reproduce this on Windows 10. In my case this is what I'm seeing: Also, did you update from a previous installer version without uninstalling the previous one first? Could be possible for you to uninstall the current version of the standalone Spyder you have and install Spyder again? Any new info in order to reproduce this is greatly appreciated. Let us know! |
Yes, this could have been the problem, after reinstalling spyder (installer) and miniconda it's working fine. |
@dalthviz @Hawxxer |
Hi @roteiro, is this happening only with a specific custom interpreter env in your setup or with all the envs? Could you try to create a new env to test if the custom interpreter continues raising the error message when using the object explorer? Also, do you have some example code that triggers this for you or the original one posted here also triggers the error message dialog in your case? Let us know! |
Hi @dalthviz, thanks for the quick reply. Here is my setup, example code and results from my tests. SetupSpyder Version: 5.2.2 (current Windows installer) DependenciesMandatory:atomicwrites >=1.2.0 : 1.4.0 (OK) Optional:cython >=0.21 : 0.29.26 (OK) My envCreation
Info
My Codeimport acoustics
standard_object = [1, 2, 3] #displays correctly in variable explorer
non_standard_object= acoustics.Signal(data=standard_object, fs=1) #does not display correctly in variable explorer Results
|
@roteiro checking a little bit I'm getting a |
Just want to add, that the issue occurred again for me i just gave up and lived with it. Maybe reinstall helps again. It occurres with the installer version under both windows 11 and MacOs Monterey with Spyder Version 5.2.2. I add a comparison, left is standalone, right via miniconda. Will try to reinstall the standalone when I find time. |
Hi @Hawxxer I think the issue with Let us know if the info there helps! |
I have a similar configuration: base environment with My working environment had |
Issue Report Checklist
spyder --reset
Problem Description
When trying to open an object I defined myself with, I get this error
While it says, don't report this to github, I think it is a problem with Spyder itself because I don't encounter this problem when using a Spyder version that is installed in a conda env.
Maybe the current spyder-kernels from conda-forge is not compatible with the current spyder installer?
When I use the default python interpreter the problem below does not occur, the object is viewable in the Object Explorer
What steps reproduce the problem?
What is the expected output? What do you see instead?
Object Explorer should open to view the object, instead it shows the error message above
Versions
It's Windows 11, but it says Windows 10 in Spyder about section, maybe also a bug to fix? (I know Windows 11 is Windows 10 with updates)
Dependencies
The text was updated successfully, but these errors were encountered: