Python SDK for Milvus. To contribute code to this project, please read our contribution guidelines first. If you have some ideas or encounter a problem, you can find us in the Slack channel #py-milvus.
The following collection shows Milvus versions and recommended PyMilvus versions:
| Milvus version | Recommended PyMilvus version |
|---|---|
| 1.0.* | 1.0.1 |
| 1.1.* | 1.1.2 |
| 2.0.0-RC1 | 2.0.0rc1 |
| 2.0.0-RC2 | 2.0.0rc2 |
| 2.0.0-RC4 | 2.0.0rc4 |
| 2.0.0-RC5 | 2.0.0rc5 |
| 2.0.0-RC6 | 2.0.0rc6 |
You can install PyMilvus via pip or pip3 for Python 3.6+:
$ pip3 install pymilvusYou can install a specific version of PyMilvus by:
$ pip3 install pymilvus==2.0.0rc6You can upgrade PyMilvus to the latest version by:
$ pip3 install --upgrade pymilvusDocumentation is available online: https://milvus.io/api-reference/pymilvus/v2.0.0rc6/install.html.
The release of PyMilvus is managed on GitHub, and GitHub Actions will package and upload each version to PyPI.
The release version number of PyMilvus follows PEP440, the format is x.y.z, and the corresponding git tag name is vx.y.z (x/y/z are numbers from 0 to 9).
For example, after PyMilvus 1.0.1 is released, a tag named v1.0.1 can be found on GitHub, and a package with version 1.0.1 can be downloaded on PyPI.
The commits on the development branch of each version will be packaged and uploaded to Test PyPI. Development branches refer to branches such as 1.0 and 1.1, and version releases are generated from the development branches, such as 1.0.1 and 1.0.2.
The package name generated by the development branch is x.y.z.dev, where is the number of commits that differ from the most recent release.
For example, after the release of 1.0.1, two commits were submitted on the 1.0 branch. At this time, the automatic packaging version number of the development branch is 1.0.1.dev2.
To install the package on test.pypi.org, you need to append the parameter --index-url after pip, for example:
$ python3 -m pip install --index-url https://test.pypi.org/simple/ pymilvus