You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
conda env export -n my-environment does not produce an environment file. The Conda documentations shows the command conda env export > environment.yml. Seem like it should be conda env export -n my-environment > environment.yml
Note: It appears conda env upload my-environment works only if there is an environment.yml file. This requirement is not clear from the documentation. However, Conda does not require an environment file to be called environment .yml. It seems that uploading an environment file should not require the file to be called environment.yml. I would expect users would like to have different names for their environment files so they can tell at a glance what environment it might contain. This is mitigated somewhat that the environment "package" is the name given in the upload. It would be swell if a user could name their uploaded environment file whatever made sense to them. Or if they can already upload environment files with arbitrary names then an example should be given.
The text was updated successfully, but these errors were encountered:
In the Managing Environments section of the docs, http://docs.anaconda.org/using.html#Environments, the command given for exporting and uploading a conda environment do not seem to work.
conda env export -n my-environment
does not produce an environment file. The Conda documentations shows the commandconda env export > environment.yml
. Seem like it should beconda env export -n my-environment > environment.yml
Note: It appears
conda env upload my-environment
works only if there is an environment.yml file. This requirement is not clear from the documentation. However, Conda does not require an environment file to be called environment .yml. It seems that uploading an environment file should not require the file to be called environment.yml. I would expect users would like to have different names for their environment files so they can tell at a glance what environment it might contain. This is mitigated somewhat that the environment "package" is the name given in the upload. It would be swell if a user could name their uploaded environment file whatever made sense to them. Or if they can already upload environment files with arbitrary names then an example should be given.The text was updated successfully, but these errors were encountered: