You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are working on build shared lib on windows but symbols export make it more complicated than on unix system.
Reasons for the request
ortools is a native python package.
On unix we use a shared lib aka libortools.so (so macos and linux packages are ~25MB) while on windows we use/build as static library libortools.lib (to avoid mess with C++ import/export dll stuff)
unfortunately ortools is composed of a dozen of module using pybind11 which each link against the underlying libortools.lib making each modules having a .pyd with ~20Mo (pybind11 wrapper + (duplicated) ortools symbols) .
For the new release v9.9 we just add a new module (ortools.math_opt) increasing the windows wheel packages (3.8 to 3.12) to 108Mb hitting the 100MB limit...
ls -l
total 540M
-rw-r----- 1 corentinl primarygroup 108M Mar 6 10:34 ortools-9.9.3963-cp310-cp310-win_amd64.whl
-rw-r----- 1 corentinl primarygroup 108M Mar 7 08:49 ortools-9.9.3963-cp311-cp311-win_amd64.whl
-rw-r----- 1 corentinl primarygroup 108M Mar 7 09:17 ortools-9.9.3963-cp312-cp312-win_amd64.whl
-rw-r----- 1 corentinl primarygroup 108M Mar 5 17:35 ortools-9.9.3963-cp38-cp38-win_amd64.whl
-rw-r----- 1 corentinl primarygroup 108M Mar 5 18:03 ortools-9.9.3963-cp39-cp39-win_amd64.whl
So I am requesting a increase up to 125Mb in order to be able to publish our windows .whl artifacts...
note: In parallel we are working on trying to move to a shared common lib libortools.dll like on linux/macos wheel packages for windows in order to reduce the size to ~30MB but this may need few months and we would like to release our v9.9 before...
Code of Conduct
I agree to follow the PSF Code of Conduct
The text was updated successfully, but these errors were encountered:
side note: I also request the file limit for test Pypi even if we still waiting to retrieve the owernship of the package name on test pypi (the current maintainer was a contractor for Google who left in mid 2017...)
see:
Hey @Mizux 👋
I've set the upload limit for ortools to 200 MB on PyPI and TestPyPI. Please be mindful of the frequency of releases at that size.
Have a nice weekend 🏃
Project URL
https://pypi.org/project/ortools
Does this project already exist?
New Limit
125
Update issue title
Which indexes
PyPI, TestPyPI
About the project
This is the Operations Research tools suite developed by Google since 2015 (think tensorflow but for OR)
ref: https://developers.google.com/optimization
note:
Reasons for the request
ortools
is a native python package.On unix we use a shared lib aka
libortools.so
(so macos and linux packages are ~25MB) while on windows we use/build as static library libortools.lib (to avoid mess with C++ import/export dll stuff)unfortunately ortools is composed of a dozen of module using pybind11 which each link against the underlying libortools.lib making each modules having a .pyd with ~20Mo (pybind11 wrapper + (duplicated) ortools symbols) .
For the new release v9.9 we just add a new module (
ortools.math_opt
) increasing the windows wheel packages (3.8 to 3.12) to 108Mb hitting the 100MB limit...So I am requesting a increase up to 125Mb in order to be able to publish our windows .whl artifacts...
note: In parallel we are working on trying to move to a shared common lib libortools.dll like on linux/macos wheel packages for windows in order to reduce the size to ~30MB but this may need few months and we would like to release our v9.9 before...
Code of Conduct
The text was updated successfully, but these errors were encountered: