always-cautious/ortools-clone
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

python: Fix internal doc

Browse Source
This commit is contained in:
Corentin Le Molgat
2021-08-30 10:10:21 +02:00
parent 28804fd612
commit 58c971fb3b
1 changed files with 3 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
ortools/python/README.md
View File

@@ -31,9 +31,6 @@ To Create a native dependent package which will contains two parts:
* A bunch of native libraries for the supported platform targeted.
* The Python code depending on it.
[`platform` names](https://github.com/java-native-access/jna/blob/cc1acdac02e4d0dda93ba01bbe3a3435b8933dab/test/com/sun/jna/PlatformTest.java#L31-L100)
come from the JNA project (Java Native Access) which will be use to find at
runtime on which platform the code is currently running.
### Local Package
@@ -59,7 +56,7 @@ python3 -m pip install --user --find-links=dist ortools
If everything good the package (located in `<buildir>/python/dist`) should have
this layout:
```
{...}/dist/ortools-8.0.9999-cp38-cp38-<platform>.whl:
{...}/dist/ortools-X.Y.9999-cp3Z-cp3Z-<platform>.whl:
\- ortools
\- __init__.py
\- .libs
@@ -74,7 +71,7 @@ this layout:
\- _pywrap....so
...
```
note: `<platform>` could be `manylinux2010_x86_64`, `macosx_10_9_x86_64` or `win-amd64`.
note: `<platform>` could be `manylinux2014_x86_64`, `macosx_10_9_x86_64` or `win-amd64`.
tips: since wheel package are just zip archive you can use `unzip -l <package>.whl`
to study their layout.
@@ -88,6 +85,7 @@ Few links on the subject...
* [Packaging Python Project](https://packaging.python.org/tutorials/packaging-projects/)
* [PEP 513 -- A Platform Tag for Portable Linux Built Distributions](https://www.python.org/dev/peps/pep-0513/)
* [PEP 571 -- The manylinux2010 Platform Tag](https://www.python.org/dev/peps/pep-0571/)
* [PEP 600 Future 'manylinux' Platform Tags](https://www.python.org/dev/peps/pep-0600/)
## Misc