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
Please consider finding a way to publish the Python bindings as a package on PyPI. While this is a little inconvenient, it’s pretty important for prospective Python users.
Obviously, being able to pip install is useful for all users, but a PyPI presence is important for Linux distribution packaging, too. In Fedora Linux, we have a “PyPI parity” policy that is designed to prevent conflicts between distribution Python package names and PyPI names.
In the case of libpoly, the Python API can’t be packaged in Fedora at all because its name, polypy, conflicts with a different package already on PyPI. (The PyPI parity rule is relatively new, and there is currently a python3-libpoly package in Fedora, but it will likely need to be removed.)
While pip users benefit from pre-built binary wheels, from the Fedora Linux perspective, even a viable source-only Python release on PyPI would solve the problem.
The text was updated successfully, but these errors were encountered:
Please consider finding a way to publish the Python bindings as a package on PyPI. While this is a little inconvenient, it’s pretty important for prospective Python users.
Obviously, being able to
pip install
is useful for all users, but a PyPI presence is important for Linux distribution packaging, too. In Fedora Linux, we have a “PyPI parity” policy that is designed to prevent conflicts between distribution Python package names and PyPI names.In the case of
libpoly
, the Python API can’t be packaged in Fedora at all because its name,polypy
, conflicts with a different package already on PyPI. (The PyPI parity rule is relatively new, and there is currently apython3-libpoly
package in Fedora, but it will likely need to be removed.)While pip users benefit from pre-built binary wheels, from the Fedora Linux perspective, even a viable source-only Python release on PyPI would solve the problem.
The text was updated successfully, but these errors were encountered: