Package Request Rules

[FeodorFitsner]

Please follow the below rules when submitting a support-request for a package.

First, check if the package has already been requested - search by package name in Packages discussions-category.

If the request already exists use the vote button to tell you are interested in that package:

Post a comment in package thread if you need to add some more context.

If you can't find the request for your package, open a new discussion in the Packages category with a normalized package name as a Title. Normalized package name is a lowercase string with . and _ replaced with -, for example: pydantic-core. In addition, please provide the pypi-link to the package.

Submit requests for non-pure (native) Python packages

"Native" packages are packages that are partially written in C, C++, Rust or other language that compiles to a machine code.

Do not submit requests for pure Python packages

To verify if the package is pure Python package find the package on PyPi and navigate to Download files. If under "Built distribution" section there is wheel (.whl) ending with -py3-none-any.whl then most probably it's a pure Python package that will work "as is" on a mobile.

Do not submit requests for high-level packages

Such "large" packages depends on other packages which might be either pure or native. For example, firebase-admin is such a package.

You can use pipgrip to break-down the package to see all its dependencies.

Install pipgrip with:

pip install pipgrip

Run the tool for the package:

pipgrip firebase-admin

By analyzing the list of all dependencies you'll find that only the following packages are non-pure Packages:

• grpcio
• google-crc32c
• msgpack
• protobuf
• pycparser

Deal with requests for these packages only.