-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
File Limit Request: ortools - 125 MB (windows wheel packages) #3714
Comments
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...) |
Hey @Mizux 👋 |
@cmaureir Many thanks ! Usually we do, at most, 3 to 4 release a year. |
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: