Canopy 2.0.1 is a limited release for users who want to prepare for the full release in Canopy 2.1, and/or use Canopy with Python 3.5 or 2.7 only (not both).
Please read the original list of known issues in the Canopy 2.0.1 release notes.
Other known issues:
- Upgrading from Canopy 1. Because Canopy 2 uses a simpler architecture than Canopy 1, it's not possible to upgrade within the Canopy application. Instead, it's necessary to do a complete uninstall and removal of Canopy 1 before installing Canopy 2. Please see the article "Updating from Canopy v1 to Canopy v2".
- See the article "Python 3.5 in Canopy 2.0 - 'No module named PyQt4' error". For most users, the solution is simply to install PyQt in the Package Manager.
- Canopy's Data Import Tool does not yet support Python 3.
- There is no Linux version of Canopy 2.0. Canopy 2.1 will provide a 64-bit RHEL6+ installer. (The RHEL5+ installer for Canopy 1.7 was the last Canopy installer for RHEL5.) The Enthought Deployment Manager (EDM) can be used now to install both RHEL5+ or RHEL6+ command-line Enthought Python environments.
- When creating a new Jupyter notebook from the Canopy File menu, if you rename the notebook (e.g. from "Untitled") the notebook will not be created, and the Canopy bug reporter might pop up with the error:
. (There's no need to submit the bug report as it has already been fixed for Canopy 2.1, thanks!)
ValueError: No JSON object could be decoded
The workaround in Canopy 2.0 is to temporarily keep the default notebook name, then rename it in the Jupyter Notebook's File menu. To reopen this renamed notebook later from Canopy requires a few extra steps (first time only):
- Right click on the original name of this notebook (e.g. "Untitled2") in the Canopy File Browser.
- Select the command "Add directory as Top Level". This will add a new "Notebooks" directory to the File Browser.
- Click on the arrow to expand this newly added "Notebooks" directory in the File Browser.
- You will see your renamed notebook in this directory.
- Canopy 2.0 supports either Python 2.7 or Python 3.5, but not both. If you install one Python version, you must manually remove its User Python environment before you can use the other Python version.
For example, if you install Canopy 2.0's Python 2.7 installer, use it, and then install Canopy 2.0's Python 3.5 installer, you'll still be using Python 2.7 in your User Python environment, until you manually remove it. To manually remove your User Python environment in Canopy 2.0, see the article "Uninstalling and resetting Canopy v2". In the section for your operating system, go to Step 4, and do the first part (delete the edm directory). Then, after you restart Canopy, you'll be using Python 3.5.
Dynamically choosing either Python 2.7 or 3.6 will be supported in Canopy 2.1. Using multiple Python versions and environments and switching easily between them will be supported in Canopy 2.2.