diff options
| author | Stella Stamenova <stilis@microsoft.com> | 2023-02-01 10:25:20 -0800 |
|---|---|---|
| committer | Stella Stamenova <stilis@microsoft.com> | 2023-02-01 10:25:58 -0800 |
| commit | ca174f12c45b79869f2324a853f1fcc082506e71 (patch) | |
| tree | 23042e5c055d991c0340c4cfb6e173c430d8ab53 /mlir/python | |
| parent | 35aa73746c85563912765567850346b48c6610e6 (diff) | |
| download | llvm-ca174f12c45b79869f2324a853f1fcc082506e71.tar.gz | |
[mlir] Pin for the PyPi requirements for mlir
This change is pinning the requirements to a specific version (or a range) depending on the requirement. A couple of considerations:
* numpy 1.24 deprecates np.object, np.bool, np.float, np.complex, np.str, and np.int which are used heavily in onnx-mlir
* not all versions of each package are available on every platform - to the best of my knowledge, these ranges should work on Ubuntu, CentOS and Windows
Adding a minimum and maximum version, or pinning to a specific versions where possible, helps with two major goals - security and maintainability. It gives us an opportunity to make sure that the packages being used are not part of a security attack as well as guaranteeing that they support the features that mlir depends on (see note about numpy deprecation).
Let me know if you are aware of better versions or ranges to pin to.
Reviewed By: stellaraccident
Differential Revision: https://reviews.llvm.org/D142563
Diffstat (limited to 'mlir/python')
| -rw-r--r-- | mlir/python/requirements.txt | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/mlir/python/requirements.txt b/mlir/python/requirements.txt index 991e8eb24335..aaf480f0bdc7 100644 --- a/mlir/python/requirements.txt +++ b/mlir/python/requirements.txt @@ -1,4 +1,4 @@ -numpy -pybind11>=2.8.0 -PyYAML -dataclasses +numpy>=1.19.5, <=1.23.5 +pybind11>=2.8.0, <=2.10.3 +PyYAML==6.0 +dataclasses>=0.6, <=0.8 |