These are chat archives for spyder-ide/public
conda install -c defaults pygletwhich was installed with conda-forge but a
conda listhas still a conda-forge mark on pyglet, normal ? I probably used conda-forge because pyglet was not available through defaults...
conda install -c defaults pygletwhich was installed with conda-forge
@jproy This was likely because
conda-forge was set as a channel in, e.g. your global or environment
.condarc file (or it otherwise remembered the channel from before). To clarify, the
-c option only adds the selected channel to your channel list and gives it priority, but doesn't override it entirely.
If you want to install a package that's only on
conda-forge, you have two options, in the order from simplest to safest/"best":
defaultsworking environment (I don't ever recommend this on
base, though): use
conda install -c defaults -c conda-forge PACKAGE-NAMEto install only the package(s) (hopefully, just the actual package you want) that aren't on
conda-forgepackages and either putting
conda-forgeat the top of the
.condarcfile for the env, or always doing
conda install -c conda-forgewith every install command. You can use Spyder wit hthis environment by just selecting its Python interpreter (under
Anaconda3/envs/YOUR_ENV_NAME/python.exe) in Spyder's Preferences, under
Python interpreter > Use the following Python interpreter.
Check out our guide to working with packages and environments in Spyder for more information about the latter part, which will be even easier in Spyder 4 with our built-in package and environment management GUI. Also, AD and CF are currently working to unify their compiler stack, so that you can mix packages from each channel without these sorts of problems.