conda-forge / qiskit-terra-feedstock

A conda-smithy repository for qiskit-terra.

About qiskit-terra-feedstock

Feedstock license: BSD-3-Clause

Home: https://qiskit.org/

Package license: Apache-2.0

Summary: Software for developing quantum computing programs

Development: https://github.com/Qiskit/qiskit

Documentation: https://qiskit.org/documentation/index.html

Current build status

Azure

Variant Status linux_64_python3.10.____cpython linux_64_python3.11.____cpython linux_64_python3.12.____cpython linux_64_python3.8.____cpython linux_64_python3.9.____73_pypy linux_64_python3.9.____cpython osx_64_python3.10.____cpython osx_64_python3.11.____cpython osx_64_python3.12.____cpython osx_64_python3.8.____cpython osx_64_python3.9.____73_pypy osx_64_python3.9.____cpython osx_arm64_python3.10.____cpython osx_arm64_python3.11.____cpython osx_arm64_python3.12.____cpython osx_arm64_python3.8.____cpython osx_arm64_python3.9.____cpython win_64_python3.10.____cpython win_64_python3.11.____cpython win_64_python3.12.____cpython win_64_python3.8.____cpython win_64_python3.9.____73_pypy win_64_python3.9.____cpython

Current release info

Name	Downloads	Version	Platforms

Installing qiskit-terra

Installing qiskit-terra 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, qiskit-terra can be installed with conda:

conda install qiskit-terra

or with mamba:

mamba install qiskit-terra

It is possible to list all of the versions of qiskit-terra available on your platform with conda:

conda search qiskit-terra --channel conda-forge

or with mamba:

mamba search qiskit-terra --channel conda-forge

Alternatively, mamba repoquery may provide more information:

# Search all versions available on your platform:
mamba repoquery search qiskit-terra --channel conda-forge

# List packages depending on `qiskit-terra`:
mamba repoquery whoneeds qiskit-terra --channel conda-forge

# List dependencies of `qiskit-terra`:
mamba repoquery depends qiskit-terra --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 Azure, GitHub, CircleCI, AppVeyor, Drone, and TravisCI it is possible to build and upload installable packages to the conda-forge anaconda.org 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 qiskit-terra-feedstock

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

• @BastianZim
• @wshanks

qiskit-terra-feedstock's Issues

@conda-forge-admin, please update version

Additional comment:

No response

Repo rename and `qiskit` package

Comment:

With the 0.25.0 release of qiskit-terra, the corresponding 0.44 release of qiskit on PyPI now lists only qiskit-terra as a dependency. This is part of this plan to merge qiskit and qiskit-terra. With the next release, qiskit-terra will jump up to version 0.45 to match the 0.45 release of qiskit and going forward qiskit will list only qiskit-terra as a dependency with version pinned to match qiskit's. Also as part of this release cycle, the qiskit-terra repo will be renamed to qiskit. It is planned that qiskit will remain an empty package pointing to qiskit-terra rather than trying to rename qiskit-terra to qiskit as a Python package, but I think the "terra" name will be de-emphasized and projects will be encouraged to depend on qiskit rather than qiskit-terra. Both qiskit and qiskit-terra will be generated from the same qiskit repo.

So, what should be done in conda-forge? Here are some steps we could take:

1. Update the recipe to point to the qiskit repo after the rename. I think this is a given though GitHub redirects will probably make it not urgent.
2. Update the recipe to publish both qiskit and qiskit-terra packages starting with 0.45. I hope this should not be too hard since they will both be generated from the same source repo.
3. Generate a qiskit 0.44 package depending on qiskit-terra 0.25.0 which we just published a conda package for. qiskit==0.44 was generated from https://github.com/Qiskit/qiskit-metapackage, so it is a different source repo. It feels like a waste to create a new feedstock just for this one release if we can generate the package from the same repo as terra for future releases though. Maybe we could create it from a branch here?
4. Rename this feedstock to qiskit-feedstock after the repo rename. I don't know how many side effects this will have. It might not be worth the trouble. Another option might be to make a new qiskit-feedstock that produces 0.44 from the metapackage for now and then produces a qiskit-terra package for 0.45 and we archive this qiskit-terra-feedstock then.

@BastianZim Any thoughts?