-
Notifications
You must be signed in to change notification settings - Fork 140
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
qudi does not work in up-to-date python 3.8 conda environment #584
Comments
Hi Tobias, We have also encountered this problem when we tried extracting a qudi-core. As python 3.8 is doing some more radical changes and some of the packages have to be adopted we will (at least for the core) first get everything clean for python 3.7 and then tackle any change to python 3.8 or higher. At least that is how I see it. @drogenlied @Neverhorst what do you think? |
Yes, I agree. Some packages do not work the same way as before with Python 3.8. Since this is explicitly not supported by qudi at the moment and does not cripple qudi functionality it should not be considered a bug. |
On linux the installation of ipykernel version 5.2.1 solves the issue. Windows is to be seen. |
adding Since |
What is affected by this bug?
Windows 10, current qudi version from github, anaconda with up-to-date python 3.8 environment
When does this occur?
Starting the manager gui module
Where on the platform does it happen?
Manager gui, ipython console
How do we replicate the issue?
Start qudi
Expected behavior (i.e. solution)
The console should be started
Other Comments
The text was updated successfully, but these errors were encountered: