-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Import env from yaml file #49
Comments
@AlbertDeFusco I think that if you have an Is not this the case @havocp ? |
Yes, if you put environment.yml in a folder and |
Are things working for you, can this issue be closed? |
Perhaps not. I created a new project in Navigator # This is an Anaconda project file.
#
# Here you can describe your project and how to run it.
# Use `anaconda-project run` to run the project.
# The file is in YAML format, please see http://www.yaml.org/start.html for more.
#
#
# Set the 'name' key to name your project
#
name: new_proj
#
# Set the 'icon' key to give your project an icon
#
icon:
#
# In the commands section, list your runnable scripts, notebooks, and other code.
# Use `anaconda-project add-command` to add commands.
#
commands: {}
#
# In the variables section, list any environment variables your code depends on.
# Use `anaconda-project add-variable` to add variables.
#
variables: {}
#
# In the services section, list any services that should be
# available before your code runs.
# Use `anaconda-project add-service` to add services.
#
services: {}
#
# In the downloads section, list any URLs to download to local files
# before your code runs.
# Use `anaconda-project add-download` to add downloads.
#
downloads: {}
#
# In the packages section, list any packages that must be installed
# before your code runs.
# Use `anaconda-project add-packages` to add packages.
#
packages: []
#
# In the channels section, list any Conda channel URLs to be searched
# for packages.
#
# For example,
#
# channels:
# - https://conda.anaconda.org/asmeurer
#
channels: []
#
# You can define multiple, named environment specs.
# Each inherits any global packages or channels,
# but can have its own unique ones also.
# Use `anaconda-project add-env-spec` to add environment specs.
#
env_specs: {default: {packages: [anaconda], channels: []}} I then copy the
Is there something I have to do to register the environment name? |
Ah, the issue is that you already have a project here when you init. I opened #53 on that, it should say "project is already initialized" or something maybe. If you do What should also work is if you had not initialized already, i.e. you had environment.yml and NOT anaconda-project.yml, then Maybe it's simpler to just have a command like |
Thanks! That's what I needed. I removed the env_specs: {my_env: {packages: [python=3, jupyter, nbformat, pandoc, bokeh, pygithub,
{pip: [pypandoc]}], channels: [conda-forge]}} |
Still works |
I'd like to convert an environment.yml file into a blank anaconda project. Is there a command like
anaconda-project add-env-file
to import the conda environment specification? Here's an example environment.The text was updated successfully, but these errors were encountered: