host and run section. • 2to3 is not used. • Scripts argument in setup.py is not used. • If console_script entrypoints are in setup.py, they are listed in meta.yaml. • No activate scripts. • Not a toml file Below is an example that configures setuptools using a pyproject.toml file (note that the setup.py file is optional if a pyproject.toml file is defined, and thus will not be discussed here): 1 configuration system has several keys that can be used to set up a mirrored context. The default setup By default, conda can serve packages from two main locations: • repo.anaconda.com: this is where

host and run section. • 2to3 is not used. • Scripts argument in setup.py is not used. • If console_script entrypoints are in setup.py, they are listed in meta.yaml. • No activate scripts. • Not a toml file Below is an example that configures setuptools using a pyproject.toml file (note that the setup.py file is optional if a pyproject.toml file is defined, and thus will not be discussed here): 1 directory as your source code. 2. In your .travis.yml file, replace the following line: - python setup.py install with these lines: - conda build your-conda-recipe - conda install your-package --use-local

host and run section. • 2to3 is not used. • Scripts argument in setup.py is not used. • If console_script entrypoints are in setup.py, they are listed in meta.yaml. • No activate scripts. • Not a toml file Below is an example that configures setuptools using a pyproject.toml file (note that the setup.py file is optional if a pyproject.toml file is defined, and thus will not be discussed here): 34 configuration system has several keys that can be used to set up a mirrored context. The default setup By default, conda can serve packages from two main locations: • repo.anaconda.com: this is where

host and run section. • 2to3 is not used. • Scripts argument in setup.py is not used. • If console_script entrypoints are in setup.py, they are listed in meta.yaml. • No activate scripts. • Not a toml file Below is an example that configures setuptools using a pyproject.toml file (note that the setup.py file is optional if a pyproject.toml file is defined, and thus will not be discussed here): 1 configuration system has several keys that can be used to set up a mirrored context. The default setup By default, conda can serve packages from two main locations: • repo.anaconda.com: this is where

host and run section. • 2to3 is not used. • Scripts argument in setup.py is not used. • If console_script entrypoints are in setup.py, they are listed in meta.yaml. • No activate scripts. • Not a toml file Below is an example that configures setuptools using a pyproject.toml file (note that the setup.py file is optional if a pyproject.toml file is defined, and thus will not be discussed here): 34 configuration system has several keys that can be used to set up a mirrored context. The default setup By default, conda can serve packages from two main locations: • repo.anaconda.com: this is where

configuration system has several keys that can be used to set up a mirrored context. The default setup By default, conda can serve packages from two main locations: • repo.anaconda.com: this is where host and run section. • 2to3 is not used. • Scripts argument in setup.py is not used. • If console_script entrypoints are in setup.py, they are listed in meta.yaml. • No activate scripts. • Not a toml file Below is an example that configures setuptools using a pyproject.toml file (note that the setup.py file is optional if a pyproject.toml file is defined, and thus will not be discussed here): Listing

host and run section. • 2to3 is not used. • Scripts argument in setup.py is not used. • If console_script entrypoints are in setup.py, they are listed in meta.yaml. • No activate scripts. • Not a toml file Below is an example that configures setuptools using a pyproject.toml file (note that the setup.py file is optional if a pyproject.toml file is defined, and thus will not be discussed here): 1 configuration system has several keys that can be used to set up a mirrored context. The default setup By default, conda can serve packages from two main locations: • repo.anaconda.com: this is where

configuration system has several keys that can be used to set up a mirrored context. The default setup By default, conda can serve packages from two main locations: • repo.anaconda.com: this is where host and run section. • 2to3 is not used. • Scripts argument in setup.py is not used. • If console_script entrypoints are in setup.py, they are listed in meta.yaml. • No activate scripts. • Not a toml file Below is an example that configures setuptools using a pyproject.toml file (note that the setup.py file is optional if a pyproject.toml file is defined, and thus will not be discussed here): Listing

configuration system has several keys that can be used to set up a mirrored context. The default setup By default, conda can serve packages from two main locations: • repo.anaconda.com: this is where host and run section. • 2to3 is not used. • Scripts argument in setup.py is not used. • If console_script entrypoints are in setup.py, they are listed in meta.yaml. • No activate scripts. • Not a toml file Below is an example that configures setuptools using a pyproject.toml file (note that the setup.py file is optional if a pyproject.toml file is defined, and thus will not be discussed here): Listing

configuration system has several keys that can be used to set up a mirrored context. The default setup By default, conda can serve packages from two main locations: • repo.anaconda.com: this is where host and run section. • 2to3 is not used. • Scripts argument in setup.py is not used. • If console_script entrypoints are in setup.py, they are listed in meta.yaml. • No activate scripts. • Not a toml file Below is an example that configures setuptools using a pyproject.toml file (note that the setup.py file is optional if a pyproject.toml file is defined, and thus will not be discussed here): Listing