Canopy 2.1 Known Issues (supplemental)

Please read the list of known issues in the Canopy 2.1 release notes (updated June 16, 2017, for Canopy 2.1.3).

Clarification of Canopy 2.1's change in "default User environment": 

  1. In Canopy 1.x, there was only one Canopy User Python 2.7 environment. You could optionally tell Canopy to make this be the default Python on your system, and Canopy would add it to your PATH environment variable.
  2. Similarly, when Canopy 2 is first started, it creates one Canopy Python environment (either Python 2.7 or 3.5, depending on which installer you run) named "User". 
  3. But in addition, in Canopy 2.1, you can create multiple environments (Python 2.7, 3.5, or 3.6). At any given time, one of these environments is active within the Canopy application
  4. Canopy's active environment is also the default python in any Canopy Command Prompt / Terminal that you open from the Canopy Tools menu.
  5. By default, the active environment in Canopy is the "User" environment mentioned in (2). You can change which environment is active from the Canopy Preferences dialog. See "Switching Python Environments" in the Canopy 2.1 documentation.
  6. Canopy no longer offers an option, as in (1), to make a Canopy Python environment be the default Python on your system by adding it to your PATH environment (though you can still do this manually if you wish; documentation forthcoming.)

Other known issues:

  • (none yet)

Please do not enter support requests in article comments

Please use article comments for suggestions to improve the article. See "How to submit Enthought Canopy/EPD support requests".

Have more questions? Submit a request

Comments

Powered by Zendesk