Canopy 2.1.x Known Issues (supplemental)

Please read the list of known issues in the Canopy 2.1.x release notes (updated May 24, 2017, for Canopy 2.1.1).

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; Canopy would add it to your PATH environment variable.
  2. Similarly, when Canopy 2 is first started, one Canopy Python environment (either Python 2.7 or 3.5) named "User" is created. 
  3. 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, and in any Canopy Command Prompt / Terminal that you open.
  4. 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.
  5. 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:

  • Canopy will fail to set up its default User Python environment if your PATH environment variable contains non-ASCII characters. This will be fixed in or before Canopy 2.2.0 (#1483 EDM). For help modifying environment variables on Windows, see this article.
Have more questions? Submit a request

Comments

Powered by Zendesk