-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Migrate matplotlib matplot_dep to Python 3.4 #5
Comments
Yes pip install pods I tried to get every 'from pylab import' out and replace it with 'from On 15/09/15 14:34, finmod wrote:
|
I installed one more time GPy devel this morning (0.8.8). Just looked into matplot_dev, bases_plot, models_plot, priors_plot. They are still on the old template. Init_conf.py should also be aligned. On Python 3.4, this morning’s version was not working. Calculations are fine so far on almost all tests. Denis Richard
From: Max Zwiessele [mailto:notifications@github.com] Yes pip install pods I tried to get every 'from pylab import' out and replace it with 'from On 15/09/15 14:34, finmod wrote:
— |
Could you please cross link an issue on GPy, so we can fix it. On 15/09/15 14:50, finmod wrote:
|
Running these demo notebooks with the following configuration:
Python 3.4.3,
IPython 4.0,
OS Windows 8.6.2.9200,
conda 3.17.0,
GPy 0.8.8,
matplotlib 1.4.3,
numpy 1.9.2.
There are some plotting issues with matplotlib and matplot_dep in the migration from MATLAB-like API to matplotlib object-oriented API. In short, the "from pylab import..." is no longer acceptable to Python 3.4. The same for plotting.matplot_dep in GPy-0.8.8.
Also similar problems in building datasets with pods. Is there a standard "conda install" or "pip install" for pods?
The text was updated successfully, but these errors were encountered: