-
-
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
master does not start (file missing) #7722
Comments
I think PR #4751 added new dependencies that need to be installed in order for Spyder to run. Those are After installing those, Spyder is starting correctly. @ccordoba12 I do not see these new dependencies in |
... but then Let's wait for an answer from @ccordoba12 or @andfoy. |
We're in the process of adding a new code completion architecture. Things are going to be a bit rough during the next couple of weeks, so we recommend to stay with beta1 until beta2 is released. By the way, @jnsebgosselin was right about the new packages that need to be installed. |
@ccordoba12 Thanks for your answer! Help is working after all, its the go to definition that is not. I think I was able to pinpoint why it is not working. Should I open a new issue for this or you guys got it all covered already? |
Yes, please do, but wait until PR #7725 is merged. That's our third huge PR in a row!! |
Oh nice! I've explained what I think the reason of the problem is in Issue #7726. I've created the issue already since I do not think the the split plugin merge will have an impact on this and it was already ready. |
It's not that that will interfere, it's just that all new work needs to be based on the layout defined by that PR. |
Closing because this should be fixed now by #7822. |
Yes it works for me (on windows). Thanks.
|
Great!! Thanks for letting us know about it. |
Today's version crashes on init
Sorry I tried to debug which file but I could not.
Back to last week commit works (eg b34a22a).
BTW the report issue window popped up but disappear instantaneously. I don't know why either. Maybe it is a separate issue?
The text was updated successfully, but these errors were encountered: