conda-forge / aospy-feedstock

A conda-smithy repository for aospy.

About aospy

Home: https://github.com/spencerahill/aospy

Package license: Apache-2.0

Feedstock license: BSD-3-Clause

Summary: Automated gridded climate data analysis and management

Development: https://github.com/spencerahill/aospy

Documentation: https://aospy.readthedocs.io/

A framework that enables automated calculations using gridded climate data. Following some basic description of where your data lives and defining any functions of variables stored in that data you want to compute, aospy enables you to fire off an arbitrary number of calculations using that data.

Current build status

All platforms:

Current release info

Name	Downloads	Version	Platforms

Installing aospy

Installing aospy from the conda-forge channel can be achieved by adding conda-forge to your channels with:

conda config --add channels conda-forge
conda config --set channel_priority strict

Once the conda-forge channel has been enabled, aospy can be installed with:

conda install aospy

It is possible to list all of the versions of aospy available on your platform with:

conda search aospy --channel conda-forge

About conda-forge

conda-forge is a community-led conda channel of installable packages. In order to provide high-quality builds, the process has been automated into the conda-forge GitHub organization. The conda-forge organization contains one repository for each of the installable packages. Such a repository is known as a feedstock.

A feedstock is made up of a conda recipe (the instructions on what and how to build the package) and the necessary configurations for automatic building using freely available continuous integration services. Thanks to the awesome service provided by CircleCI, AppVeyor and TravisCI it is possible to build and upload installable packages to the conda-forge Anaconda-Cloud channel for Linux, Windows and OSX respectively.

To manage the continuous integration and simplify feedstock maintenance conda-smithy has been developed. Using the conda-forge.yml within this repository, it is possible to re-render all of this feedstock's supporting files (e.g. the CI configuration files) with conda smithy rerender.

For more information please check the conda-forge documentation.

Terminology

feedstock - the conda recipe (raw material), supporting scripts and CI configuration.

conda-smithy - the tool which helps orchestrate the feedstock. Its primary use is in the construction of the CI .yml files and simplify the management of many feedstocks.

conda-forge - the place where the feedstock and smithy live and work to produce the finished article (built conda distributions)

Updating aospy-feedstock

If you would like to improve the aospy recipe or build a new package version, please fork this repository and submit a PR. Upon submission, your changes will be run on the appropriate platforms to give the reviewer an opportunity to confirm that the changes result in a successful build. Once merged, the recipe will be re-built and uploaded automatically to the conda-forge channel, whereupon the built conda packages will be available for everybody to install and use from the conda-forge channel. Note that all branches in the conda-forge/aospy-feedstock are immediately built and any created packages are uploaded, so PRs should be based on branches in forks and branches in the main repository should only be used to build distinct package versions.

In order to produce a uniquely identifiable distribution:

• If the version of a package is not being increased, please add or increase the build/number.
• If the version of a package is being increased, please remember to return the build/number back to 0.

Feedstock Maintainers

• @spencerahill

aospy-feedstock's Issues

@conda-forge-admin, please update circle

@conda-forge-admin, please update circle

aospy supports python 3.5+, but conda-forge builds were for 2.7 and 3.6 only

Issue:

Title says it all. I couldn't find anything definitive in the documentation about how to control this, but I did find several candidates:

• In https://github.com/conda-forge/aospy-feedstock/tree/master/.ci_support there are the 2.7 and 3.6 yaml files for each platform, but AFAICT they get automatically generated by conda smithy. So I assume just deleting the 2.7 ones isn't the right path (nor would manually creating 3.7 ones).

• I also found this section of the conda docs about specifying build variants within a conda_build_config.yaml file, but I don't see that anywhere in our feedstock. Do I just create it at the top level?

• I noticed in xarray's conda_forge.yaml they have a max_py_ver option. Is there an analogous min_py_ver option?

Please advise on how to fix this. Thanks!

Environment (conda list): n/a

$ conda list

Details about conda and system ( conda info ): n/a

$ conda info