conda-forge / python-ternary-feedstock

A conda-smithy repository for python-ternary.

About python-ternary

Home: https://github.com/marcharper/python-ternary

Package license: MIT

Feedstock license: BSD-3-Clause

Summary: Make ternary plots in matplotlib

Current build status

All platforms:

Current release info

Name	Downloads	Version	Platforms

Installing python-ternary

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

conda config --add channels conda-forge

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

conda install python-ternary

It is possible to list all of the versions of python-ternary available on your platform with:

conda search python-ternary --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 python-ternary-feedstock

If you would like to improve the python-ternary 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/python-ternary-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

• @marcharper
• @ocefpaf

python-ternary-feedstock's Issues

Maintainers

Hi @marcharper,

conda-forge is a community led packaging system for use with conda, and I just wanted to let you know that we added python-ternary to the list of packaged software on conda-forge.

The conda-forge infrastructure revolves around the idea of a feedstock, which is just a git repo containing a conda recipe (the build instructions) and automatically generated CI scripts necessary to build the recipe on Linux, OS X and Windows where appropriate.

We would love for you, and anybody else you can recommend, to be part of the python-ternary-feedstock maintenance team. Adding somebody to the team is simply a matter of adding your GitHub handle to recipe-maintainers in the recipe/meta.yaml of the feedstock (i.e. it is part of the metadata itself) - conda-forge's automatic team management will take care of the rest and give you write access to the feedstock. Being part of the maintainer's team typically involves changing the version string when a new release of your software is made, responding to issues raised by users, as well as merging the occasional PR when automatic updates to the CI scripts are proposed.

If you'd like to be part of the feedstock maintainers list, but would rather not raise the PR yourself, just let me know and I'd be happy to update recipe-maintainers on your behalf.

Thanks again for working on such useful library!

@conda-forge-admin, please update circle

@conda-forge-admin, please update circle