tokenizers

[paul-upfeat]

https://pypi.org/project/tokenizers/

im going to have to apologize, as im working on mobile applications that uses different py packages that all have dependencies and it would seem that i would probably end up requesting quite a lot of packages being added...

from the docs https://flet.dev/docs/reference/binary-packages-android-ios this seems to be the suggestion to request for packages/versions to be added for now. https://pypi.flet.dev/ itself looks like it contains a very limited number of packages and i dont want to come across as making a lot of demands.

so my question is, is this the preferred way of doing this? the docs mention a mobile forge project that can be used to create your own but im not sure if this is something that would be simple to do for someone thats not super fluent in python. is the recommendation to request tens/hundreds of packages?

[FeodorFitsner]

The "big idea" is that at some point the maintainers of 3rd-party Python packages (aka community) will start building wheels for iOS and Android themselves and uploading them to PyPI. iOS and Android support have been just added into Python 3.13. PyPI.org does not support iOS and Android tags yet, and we don't know when community will start making iOS/Android wheels as it's kind of specialized task.

So, we have to build mobile wheels for now. https://github.com/flet-dev/mobile-forge is the tool for that. Unfortunately, there is no simple recipe for authoring "recipe" to build the wheel. Sometimes, the native C/C++ code is trivial and setup logic is standard and adding a recipe for such package is just adding meta.yaml, e.g. https://github.com/flet-dev/mobile-forge/blob/python3.12/recipes/websockets/meta.yaml. In 40% of cases you need to "patch" package sources to make it build for iOS/Android and these patches can be really scary like this one: https://github.com/flet-dev/mobile-forge/blob/python3.12/recipes/opencv-python/patches/mobile.patch

To make recipes you need to be willing to dig into Python setup logic (venv, wheel, pyproject.toml, setup.py, etc.) as well as deal with C/C++/Rust compilation and linking quirks.

You can give Mobile Forge a try and I promise to write some instructions on how to use it. In the meantime, yes, request the packages you miss. See, for successful packaging we probably need 20% of packages covering the needs of 80% of developers :) Before submitting hundreds of requests though please ask here if it makes sense or it will look like a spam :)

[FeodorFitsner]

Btw, tokenizers package is now available for both iOS and Android.

Look at tokenizers recipe: https://github.com/flet-dev/mobile-forge/blob/python3.12/recipes/tokenizers/meta.yaml

It's written in Rust and uses Maturin for building. Worked for iOS and Android like a breeze.
I'm pretty sure any other Rust/Maturin package will take minutes to build for mobile.

[paul-upfeat]

Thanks for the clarification, thats starting to make a lot more sense. For my use case, I'm trying flet to develop applications that can be built for multiple platforms. MacOS and windows was relatively straightforward but I was indeed a little confused for the mobile side.

For context, I'm creating an application using the latest smolagents and litellm packages. These packages have various dependencies and of course I'm running into issues building, which brought up the question in my mind of how I'm supposed to approach this since I could see myself requesting various packages, but also various versions of packages depending on what packages I was using to build an app.

I didn't want to spam which is why im asking about it - is the recommendation in this case to attempt building the mobile wheels first, if its simple, to keep the requests low?

Very much appreciate your work and help!

[paul-upfeat]

ive attempted to create my own wheel (https://pypi.org/project/rpds-py/) as i was getting this error:

           VERBOSE: The conflict is caused by:                                                                                                                                                                                            
               jsonschema 4.23.0 depends on rpds-py>=0.7.1                                                                                                                                                                                
               jsonschema 4.22.0 depends on rpds-py>=0.7.1   

i created the wheel with mobile-forge navigating the instructions (the instructions werent exact so im not sure i did it all correctly). ended up with three files:

rpds_py-0.23.0-cp312-cp312-ios_13_0_arm64_iphoneos.whl
rpds_py-0.23.0-cp312-cp312-ios_13_0_arm64_iphonesimulator.whl
rpds_py-0.23.0-cp312-cp312-ios_13_0_x86_64_iphonesimulator.whl

added this to pyproject.toml per the instructions:

requires = [
    "--find-links", "/Users/admin/Documents/workspace/ai/mobile-forge/dist",
    "rpds-py",
]

tried to flet build again but got the same error. im doing something wrong but not sure where - im guessing that might not be the correct way of telling it to look for the package i made. any ideas?

[FeodorFitsner]

Run build with -v option for more details.

[paul-upfeat]

i run it with flet build --clear-cache -vv ipa

if i add this to my dependencies in pyproject.toml

dependencies = [
"rpds-py @ file:///Users/admin/Documents/workspace/ai/mobile-forge/dist/rpds_py-0.23.0-cp312-cp312-ios_13_0_arm64_iphoneos.whl",
]

it seems to pass it (but now im creating a wheel for a different package that needs to be built)

requires = [
    "--find-links", "/Users/admin/Documents/workspace/ai/mobile-forge/dist",
    "rpds-py",
]

doesnt seem to do anything but maybe im doing something wrong?

[FeodorFitsner]

'requires' is unknown section I guess.

[paul-upfeat]

ive tried building two wheels using the same setup

jiter @ file:///Users/admin/Documents/workspace/ai/mobile-forge/dist/jiter-0.8.2-cp312-cp312-ios_13_0_arm64_iphoneos.whl 
rpds-py @  file:///Users/admin/Documents/workspace/ai/mobile-forge/dist/rpds_py-0.23.0-cp312-cp312-ios_13_0_arm64_iphoneos.whl

both built successfully like:

Repacking wheel as /Users/admin/Documents/workspace/ai/mobile-forge/dist/jiter-0.8.2-cp312-cp312-ios_13_0_x86_64_iphonesimulator.whl...OK

Successful builds for:
 * jiter (default version) (ios_13_0_arm64_iphoneos)
 * jiter (default version) (ios_13_0_arm64_iphonesimulator)
 * jiter (default version) (ios_13_0_x86_64_iphonesimulator)

and added direct dependencies for flet build but im getting an error for jiter for some reason

           Installing  with pip command to /Users/admin/Documents/workspace/ai/resumeagent/flet_app/build/site-packages/iphoneos.arm64                                                                                                    
           Downloading Python distributive from https://github.com/indygreg/python-build-standalone/releases/download/20240909/cpython-3.12.6+20240909-x86_64-apple-darwin-install_only_stripped.tar.gz to a build directory              
[18:04:04] Extracting Python distributive                                                                                                                                                                                                 
[18:04:42] Cleanup installed packages                                                                                                                                                                                                     
[18:04:43] Configured iOS/iphonesimulator.arm64 platform with sitecustomize.py                                                                                                                                                            
           Installing  with pip command to /Users/admin/Documents/workspace/ai/resumeagent/flet_app/build/site-packages/iphonesimulator.arm64                                                                                             
           ERROR: jiter-0.8.2-cp312-cp312-ios_13_0_arm64_iphoneos.whl is not a supported wheel on this platform.    

ive tried all three versions with no success, any ideas? can i request jiter? https://pypi.org/project/jiter

thanks!

[FeodorFitsner]

You can publish your packages to Gemfury: https://fury.co/l/pypi-server - it's free for public packages.

Hey, and don't forget to do PR(s) to Flet's mobile forge repo when you're done! ;)

[paul-upfeat]

I wasn't able to get this working on my iphone simulator. I tried various things, eventually updating to flet 0.27.1 and signing with a iOS development cert/profile. I built the app with flet build ipa which created an .ipa file. I extracted this file and then tried to run it with xcrun to my simulator which gave me this error:

An error was encountered processing the command (domain=FBSOpenApplicationServiceErrorDomain, code=1):
Simulator device failed to launch com.upfeat.resumeagent.
The request was denied by service delegate (SBMainWorkspace).
Underlying error (domain=FBSOpenApplicationServiceErrorDomain, code=1):
        The request to open "com.upfeat.resumeagent" failed.
        The request was denied by service delegate (SBMainWorkspace).

This error happens when I don't sign it as well.

However I was able to install it on my physical device with developer mode on. I suspect maybe its because I'm supposed to build it for the simulator architecture? (but I couldnt find where to specify that in the options)

I am now trying to build these for android to test that out instead but I couldn't find any documentation on it anywhere. The mobile-forge repo has instructions sort of for IOS on where to compile python for it (https://github.com/beeware/Python-Apple-support) but I'm not sure what im supposed to use for android. I see there is an archived https://github.com/beeware/Python-Android-support which says to use https://github.com/chaquo/chaquopy but google search shows theres several similar tools. The setup script says to set MOBILE_FORGE_ANDROID_SUPPORT_PATH so I suspect theres a specific tool thats being used. Could you point me in the right direction?

[FeodorFitsner]

flet build ipa creates binaries for iOS ARM64 architecture, i.e. real device. We will implement an ability to run on simulators in the next 0.28 release.

For now, you can use this trick.

Start iOS Simulator.

While being in app's directory (and presumably you have flutter in your PATH, if you don't then use the one installed by flet build: ~/flutter/3.27.4/bin/flutter):

export SERIOUS_PYTHON_SITE_PACKAGES=$(pwd)/build/site-packages
cd build/flutter
flutter run

Choose simulator as a run target.

[FeodorFitsner]

Re: mobile-forge. Original https://github.com/beeware/mobile-forge does not support Android, our fork does.
Our fork depends on Python build by https://github.com/flet-dev/python-build (https://github.com/flet-dev/python-build/releases/tag/v3.12)

[paul-upfeat]

thanks a lot! I will try this out