py2apk 0.3.0__tar.gz

py2apk-0.3.0/LICENSE

@@ -0,0 +1,12 @@
+Copyright (c) 2026 Two Plasma Studios. All rights reserved.
+
+CONFIDENTIALITY AND PROPRIETARY NOTICE
+
+This software and all associated documentation files (the "Software") are the intellectual property of Two Plasma Studios. 
+
+Strictly Prohibition on Copying and Distribution:
+1. No part of this Software may be copied, reproduced, modified, reverse engineered, decompiled, disassembled, or distributed in any form or by any means, electronic or mechanical, without the prior written permission of the copyright owner.
+2. The Software is provided solely for personal running/execution via official package managers (e.g., pip). 
+3. Commercial use, reselling, or hosting the Software as a service (SaaS) is strictly prohibited.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

py2apk-0.3.0/PKG-INFO

@@ -0,0 +1,203 @@
+Metadata-Version: 2.4
+Name: py2apk
+Version: 0.3.0
+Summary: Turn a Python script into an Android APK with a GUI - no Docker, no compiling on your machine
+Author: TwoPlasmaStudios
+License-Expression: LicenseRef-Proprietary
+Project-URL: Homepage, https://github.com/TwoPlasmaStudios/py2apk
+Project-URL: Issues, https://github.com/TwoPlasmaStudios/py2apk/issues
+Keywords: android,apk,python,packaging,flask,webview,gui
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: X11 Applications
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: Microsoft :: Windows
+Classifier: Operating System :: MacOS
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Software Development :: Build Tools
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Provides-Extra: icon
+Requires-Dist: pillow; extra == "icon"
+Dynamic: license-file
+
+# py2apk
+
+[Türkçe](README.tr.md)
+
+Turn a Python script into an Android APK, from a simple desktop GUI.
+No Docker, no WSL, no compiler on your machine, and it runs on Windows, macOS and Linux.
+
+```
+pip install py2apk
+py2apk
+```
+
+Pick your `.py` file, choose an app type, press **Build APK**. That's it.
+
+## How it works
+
+py2apk is split in two parts so that you never have to compile anything:
+
+1. **The factory** (`factory.py` + a GitHub Actions workflow) runs once on GitHub.
+   It cross-compiles CPython for Android (arm64-v8a and x86_64), builds the Android
+   wheels for a set of popular libraries (Flask, NumPy, pandas, Pillow, ...), and
+   publishes everything as a GitHub Release.
+2. **The tool** (`py2apk.py`, the GUI you run) downloads those ready-made pieces,
+   scans your imports, bundles your code and the libraries it needs, writes the
+   Android manifest, and packages and signs the APK.
+
+The only things downloaded on your machine are a JDK 17 and the Android build-tools
+(if you don't already have them), kept in `~/.py2apk`.
+
+## Install
+
+From PyPI (once published):
+
+```
+pip install py2apk
+```
+
+Straight from GitHub (works today):
+
+```
+pip install git+https://github.com/TwoPlasmaStudios/pyapk.git
+```
+
+Requirements: Python 3.10+ with tkinter. The Windows and macOS installers from
+python.org include tkinter. On Debian/Ubuntu: `sudo apt install python3-tk`.
+Optional: `pip install py2apk[icon]` (Pillow) to use JPG/WebP logos and get a sharp preview.
+
+## Use it
+
+```
+py2apk                 # opens the GUI
+py2apk path/to/app.py  # opens the GUI with a file preselected
+```
+
+1. **Python file**: your entry script. Other `.py` files and packages next to it are
+   included automatically, so keep the project in its own folder.
+2. **App**: name, package name (e.g. `com.me.myapp`), version and an optional logo.
+3. **App type**: see below.
+4. **Libraries**: detected from your imports. Each one shows whether a ready-made
+   Android build exists. Add extra packages in the *Extra packages* field.
+5. Press **Build APK**. The first build downloads the JDK and Android tools (several
+   hundred MB); later builds are fast. The APK is written next to your script.
+
+Install it with `adb install MyApp-1.0.apk` or copy it to the phone and open it
+(allow installs from unknown sources). The APK is signed with a debug key, which is
+fine for testing and sideloading but not for Google Play.
+
+### App types
+
+| Type | Status | What you get |
+|---|---|---|
+| **Console** | works | `print()` output is shown on screen. For scripts, bots, calculations. No `input()`. |
+| **Web UI** | works | Run Flask/FastAPI/etc. in your script. The app opens it full screen in a WebView. |
+| **Pygame / Games** | not yet | Needs an SDL2 runtime. |
+| **Kivy** | not yet | Needs an SDL2 runtime. |
+
+Tkinter does not exist on Android. Use the **Web UI** type for graphical apps.
+
+#### Web UI example
+
+```python
+import os
+from flask import Flask
+
+app = Flask(__name__)
+
+@app.get("/")
+def index():
+    return "<h1>Hello from Android!</h1>"
+
+app.run(host="127.0.0.1", port=int(os.environ.get("PORT", 5000)), debug=False)
+```
+
+Keep `debug=False` (the reloader starts a second process, which Android won't allow) and
+listen on `127.0.0.1`. The port is set in the GUI and passed to your code as `PORT`.
+If the server fails to start, the app shows the Python traceback instead of a blank page.
+
+## Libraries
+
+The factory builds Android wheels for a fixed list of popular packages
+(see `LIBS` in `factory.py`), plus all of their dependencies. Pure-Python packages
+work as they are. Packages with C extensions only work if an Android build exists.
+
+* Packages in the Release are used first.
+* Anything else is tried from PyPI (pure-Python or Android wheels) with `pip`.
+* If nothing is found you get a warning in the log and the package is skipped.
+
+Which libraries are available changes as the factory improves: open the
+`index.json` asset of the Release (or look at the status column in the GUI).
+Some heavy packages (SciPy, scikit-learn, OpenCV, anything needing Rust or Fortran
+toolchains) are the hardest to cross-compile and may be marked as failed.
+
+## Run your own factory
+
+Fork the repository, enable Actions, give the workflow write access
+(*Settings -> Actions -> General -> Workflow permissions -> Read and write*), then run
+**Actions -> factory -> Run workflow**. When it finishes, a release tagged `cp313` appears.
+Point the tool at your fork:
+
+```
+# Windows (PowerShell)
+$env:PY2APK_REPO = "you/your-fork"
+# macOS / Linux
+export PY2APK_REPO=you/your-fork
+```
+
+Or use *Advanced -> GitHub repository* inside the GUI.
+
+## Environment variables
+
+| Variable | Meaning |
+|---|---|
+| `PY2APK_REPO` | GitHub `owner/repo` that hosts the Release (default `TwoPlasmaStudios/pyapk`) |
+| `PY2APK_HOME` | Cache folder (default `~/.py2apk`) |
+| `PY2APK_PY` | Release tag, i.e. the Python version (default `cp313`) |
+
+## Troubleshooting
+
+* **"Library index could not be fetched"**: the repository must be public and the factory
+  must have finished at least once.
+* **App crashes or shows a traceback**: run `adb logcat -s pyapk` while opening it.
+* **Import error for a native library**: that package has no Android build yet. Check its
+  status in the GUI.
+* **Build fails while downloading tools**: check your connection; downloads resume from the cache.
+
+## Limitations
+
+* Python 3.13 runtime, arm64-v8a and x86_64 only, minimum Android 7.0 (API 24).
+* No tkinter, pygame or Kivy yet.
+* Console apps have no interactive input.
+* Debug-signed APKs only.
+
+## Publishing to PyPI (maintainers)
+
+Releases are published by `.github/workflows/publish.yml` with PyPI Trusted Publishing
+(no API token needed). It only runs for tags that start with `v`, so the `cp313` release
+created by the factory never triggers it.
+
+One-time setup:
+
+1. Check that the name is free: https://pypi.org/project/py2apk/ should return 404.
+2. On pypi.org: *Your projects -> Publishing -> Add a new pending publisher* with
+   project `py2apk`, owner `TwoPlasmaStudios`, repository `pyapk`,
+   workflow `publish.yml`, environment `pypi`.
+3. On GitHub: *Settings -> Environments -> New environment* named `pypi`.
+
+Each release: bump `version` in `pyproject.toml`, then
+
+```
+git tag v0.3.0
+git push origin v0.3.0
+```
+
+Manual alternative: `pip install build twine`, `python -m build`, `twine upload dist/*`
+(use an API token, username `__token__`).
+
+## License
+
+MIT. Libraries in the Release keep their own licenses; CPython is under the PSF license.

py2apk-0.3.0/README.md

@@ -0,0 +1,179 @@
+# py2apk
+
+[Türkçe](README.tr.md)
+
+Turn a Python script into an Android APK, from a simple desktop GUI.
+No Docker, no WSL, no compiler on your machine, and it runs on Windows, macOS and Linux.
+
+```
+pip install py2apk
+py2apk
+```
+
+Pick your `.py` file, choose an app type, press **Build APK**. That's it.
+
+## How it works
+
+py2apk is split in two parts so that you never have to compile anything:
+
+1. **The factory** (`factory.py` + a GitHub Actions workflow) runs once on GitHub.
+   It cross-compiles CPython for Android (arm64-v8a and x86_64), builds the Android
+   wheels for a set of popular libraries (Flask, NumPy, pandas, Pillow, ...), and
+   publishes everything as a GitHub Release.
+2. **The tool** (`py2apk.py`, the GUI you run) downloads those ready-made pieces,
+   scans your imports, bundles your code and the libraries it needs, writes the
+   Android manifest, and packages and signs the APK.
+
+The only things downloaded on your machine are a JDK 17 and the Android build-tools
+(if you don't already have them), kept in `~/.py2apk`.
+
+## Install
+
+From PyPI (once published):
+
+```
+pip install py2apk
+```
+
+Straight from GitHub (works today):
+
+```
+pip install git+https://github.com/TwoPlasmaStudios/pyapk.git
+```
+
+Requirements: Python 3.10+ with tkinter. The Windows and macOS installers from
+python.org include tkinter. On Debian/Ubuntu: `sudo apt install python3-tk`.
+Optional: `pip install py2apk[icon]` (Pillow) to use JPG/WebP logos and get a sharp preview.
+
+## Use it
+
+```
+py2apk                 # opens the GUI
+py2apk path/to/app.py  # opens the GUI with a file preselected
+```
+
+1. **Python file**: your entry script. Other `.py` files and packages next to it are
+   included automatically, so keep the project in its own folder.
+2. **App**: name, package name (e.g. `com.me.myapp`), version and an optional logo.
+3. **App type**: see below.
+4. **Libraries**: detected from your imports. Each one shows whether a ready-made
+   Android build exists. Add extra packages in the *Extra packages* field.
+5. Press **Build APK**. The first build downloads the JDK and Android tools (several
+   hundred MB); later builds are fast. The APK is written next to your script.
+
+Install it with `adb install MyApp-1.0.apk` or copy it to the phone and open it
+(allow installs from unknown sources). The APK is signed with a debug key, which is
+fine for testing and sideloading but not for Google Play.
+
+### App types
+
+| Type | Status | What you get |
+|---|---|---|
+| **Console** | works | `print()` output is shown on screen. For scripts, bots, calculations. No `input()`. |
+| **Web UI** | works | Run Flask/FastAPI/etc. in your script. The app opens it full screen in a WebView. |
+| **Pygame / Games** | not yet | Needs an SDL2 runtime. |
+| **Kivy** | not yet | Needs an SDL2 runtime. |
+
+Tkinter does not exist on Android. Use the **Web UI** type for graphical apps.
+
+#### Web UI example
+
+```python
+import os
+from flask import Flask
+
+app = Flask(__name__)
+
+@app.get("/")
+def index():
+    return "<h1>Hello from Android!</h1>"
+
+app.run(host="127.0.0.1", port=int(os.environ.get("PORT", 5000)), debug=False)
+```
+
+Keep `debug=False` (the reloader starts a second process, which Android won't allow) and
+listen on `127.0.0.1`. The port is set in the GUI and passed to your code as `PORT`.
+If the server fails to start, the app shows the Python traceback instead of a blank page.
+
+## Libraries
+
+The factory builds Android wheels for a fixed list of popular packages
+(see `LIBS` in `factory.py`), plus all of their dependencies. Pure-Python packages
+work as they are. Packages with C extensions only work if an Android build exists.
+
+* Packages in the Release are used first.
+* Anything else is tried from PyPI (pure-Python or Android wheels) with `pip`.
+* If nothing is found you get a warning in the log and the package is skipped.
+
+Which libraries are available changes as the factory improves: open the
+`index.json` asset of the Release (or look at the status column in the GUI).
+Some heavy packages (SciPy, scikit-learn, OpenCV, anything needing Rust or Fortran
+toolchains) are the hardest to cross-compile and may be marked as failed.
+
+## Run your own factory
+
+Fork the repository, enable Actions, give the workflow write access
+(*Settings -> Actions -> General -> Workflow permissions -> Read and write*), then run
+**Actions -> factory -> Run workflow**. When it finishes, a release tagged `cp313` appears.
+Point the tool at your fork:
+
+```
+# Windows (PowerShell)
+$env:PY2APK_REPO = "you/your-fork"
+# macOS / Linux
+export PY2APK_REPO=you/your-fork
+```
+
+Or use *Advanced -> GitHub repository* inside the GUI.
+
+## Environment variables
+
+| Variable | Meaning |
+|---|---|
+| `PY2APK_REPO` | GitHub `owner/repo` that hosts the Release (default `TwoPlasmaStudios/pyapk`) |
+| `PY2APK_HOME` | Cache folder (default `~/.py2apk`) |
+| `PY2APK_PY` | Release tag, i.e. the Python version (default `cp313`) |
+
+## Troubleshooting
+
+* **"Library index could not be fetched"**: the repository must be public and the factory
+  must have finished at least once.
+* **App crashes or shows a traceback**: run `adb logcat -s pyapk` while opening it.
+* **Import error for a native library**: that package has no Android build yet. Check its
+  status in the GUI.
+* **Build fails while downloading tools**: check your connection; downloads resume from the cache.
+
+## Limitations
+
+* Python 3.13 runtime, arm64-v8a and x86_64 only, minimum Android 7.0 (API 24).
+* No tkinter, pygame or Kivy yet.
+* Console apps have no interactive input.
+* Debug-signed APKs only.
+
+## Publishing to PyPI (maintainers)
+
+Releases are published by `.github/workflows/publish.yml` with PyPI Trusted Publishing
+(no API token needed). It only runs for tags that start with `v`, so the `cp313` release
+created by the factory never triggers it.
+
+One-time setup:
+
+1. Check that the name is free: https://pypi.org/project/py2apk/ should return 404.
+2. On pypi.org: *Your projects -> Publishing -> Add a new pending publisher* with
+   project `py2apk`, owner `TwoPlasmaStudios`, repository `pyapk`,
+   workflow `publish.yml`, environment `pypi`.
+3. On GitHub: *Settings -> Environments -> New environment* named `pypi`.
+
+Each release: bump `version` in `pyproject.toml`, then
+
+```
+git tag v0.3.0
+git push origin v0.3.0
+```
+
+Manual alternative: `pip install build twine`, `python -m build`, `twine upload dist/*`
+(use an API token, username `__token__`).
+
+## License
+
+MIT. Libraries in the Release keep their own licenses; CPython is under the PSF license.

py2apk-0.3.0/py2apk.egg-info/PKG-INFO

@@ -0,0 +1,203 @@
+Metadata-Version: 2.4
+Name: py2apk
+Version: 0.3.0
+Summary: Turn a Python script into an Android APK with a GUI - no Docker, no compiling on your machine
+Author: TwoPlasmaStudios
+License-Expression: LicenseRef-Proprietary
+Project-URL: Homepage, https://github.com/TwoPlasmaStudios/py2apk
+Project-URL: Issues, https://github.com/TwoPlasmaStudios/py2apk/issues
+Keywords: android,apk,python,packaging,flask,webview,gui
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: X11 Applications
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: Microsoft :: Windows
+Classifier: Operating System :: MacOS
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Software Development :: Build Tools
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Provides-Extra: icon
+Requires-Dist: pillow; extra == "icon"
+Dynamic: license-file
+
+# py2apk
+
+[Türkçe](README.tr.md)
+
+Turn a Python script into an Android APK, from a simple desktop GUI.
+No Docker, no WSL, no compiler on your machine, and it runs on Windows, macOS and Linux.
+
+```
+pip install py2apk
+py2apk
+```
+
+Pick your `.py` file, choose an app type, press **Build APK**. That's it.
+
+## How it works
+
+py2apk is split in two parts so that you never have to compile anything:
+
+1. **The factory** (`factory.py` + a GitHub Actions workflow) runs once on GitHub.
+   It cross-compiles CPython for Android (arm64-v8a and x86_64), builds the Android
+   wheels for a set of popular libraries (Flask, NumPy, pandas, Pillow, ...), and
+   publishes everything as a GitHub Release.
+2. **The tool** (`py2apk.py`, the GUI you run) downloads those ready-made pieces,
+   scans your imports, bundles your code and the libraries it needs, writes the
+   Android manifest, and packages and signs the APK.
+
+The only things downloaded on your machine are a JDK 17 and the Android build-tools
+(if you don't already have them), kept in `~/.py2apk`.
+
+## Install
+
+From PyPI (once published):
+
+```
+pip install py2apk
+```
+
+Straight from GitHub (works today):
+
+```
+pip install git+https://github.com/TwoPlasmaStudios/pyapk.git
+```
+
+Requirements: Python 3.10+ with tkinter. The Windows and macOS installers from
+python.org include tkinter. On Debian/Ubuntu: `sudo apt install python3-tk`.
+Optional: `pip install py2apk[icon]` (Pillow) to use JPG/WebP logos and get a sharp preview.
+
+## Use it
+
+```
+py2apk                 # opens the GUI
+py2apk path/to/app.py  # opens the GUI with a file preselected
+```
+
+1. **Python file**: your entry script. Other `.py` files and packages next to it are
+   included automatically, so keep the project in its own folder.
+2. **App**: name, package name (e.g. `com.me.myapp`), version and an optional logo.
+3. **App type**: see below.
+4. **Libraries**: detected from your imports. Each one shows whether a ready-made
+   Android build exists. Add extra packages in the *Extra packages* field.
+5. Press **Build APK**. The first build downloads the JDK and Android tools (several
+   hundred MB); later builds are fast. The APK is written next to your script.
+
+Install it with `adb install MyApp-1.0.apk` or copy it to the phone and open it
+(allow installs from unknown sources). The APK is signed with a debug key, which is
+fine for testing and sideloading but not for Google Play.
+
+### App types
+
+| Type | Status | What you get |
+|---|---|---|
+| **Console** | works | `print()` output is shown on screen. For scripts, bots, calculations. No `input()`. |
+| **Web UI** | works | Run Flask/FastAPI/etc. in your script. The app opens it full screen in a WebView. |
+| **Pygame / Games** | not yet | Needs an SDL2 runtime. |
+| **Kivy** | not yet | Needs an SDL2 runtime. |
+
+Tkinter does not exist on Android. Use the **Web UI** type for graphical apps.
+
+#### Web UI example
+
+```python
+import os
+from flask import Flask
+
+app = Flask(__name__)
+
+@app.get("/")
+def index():
+    return "<h1>Hello from Android!</h1>"
+
+app.run(host="127.0.0.1", port=int(os.environ.get("PORT", 5000)), debug=False)
+```
+
+Keep `debug=False` (the reloader starts a second process, which Android won't allow) and
+listen on `127.0.0.1`. The port is set in the GUI and passed to your code as `PORT`.
+If the server fails to start, the app shows the Python traceback instead of a blank page.
+
+## Libraries
+
+The factory builds Android wheels for a fixed list of popular packages
+(see `LIBS` in `factory.py`), plus all of their dependencies. Pure-Python packages
+work as they are. Packages with C extensions only work if an Android build exists.
+
+* Packages in the Release are used first.
+* Anything else is tried from PyPI (pure-Python or Android wheels) with `pip`.
+* If nothing is found you get a warning in the log and the package is skipped.
+
+Which libraries are available changes as the factory improves: open the
+`index.json` asset of the Release (or look at the status column in the GUI).
+Some heavy packages (SciPy, scikit-learn, OpenCV, anything needing Rust or Fortran
+toolchains) are the hardest to cross-compile and may be marked as failed.
+
+## Run your own factory
+
+Fork the repository, enable Actions, give the workflow write access
+(*Settings -> Actions -> General -> Workflow permissions -> Read and write*), then run
+**Actions -> factory -> Run workflow**. When it finishes, a release tagged `cp313` appears.
+Point the tool at your fork:
+
+```
+# Windows (PowerShell)
+$env:PY2APK_REPO = "you/your-fork"
+# macOS / Linux
+export PY2APK_REPO=you/your-fork
+```
+
+Or use *Advanced -> GitHub repository* inside the GUI.
+
+## Environment variables
+
+| Variable | Meaning |
+|---|---|
+| `PY2APK_REPO` | GitHub `owner/repo` that hosts the Release (default `TwoPlasmaStudios/pyapk`) |
+| `PY2APK_HOME` | Cache folder (default `~/.py2apk`) |
+| `PY2APK_PY` | Release tag, i.e. the Python version (default `cp313`) |
+
+## Troubleshooting
+
+* **"Library index could not be fetched"**: the repository must be public and the factory
+  must have finished at least once.
+* **App crashes or shows a traceback**: run `adb logcat -s pyapk` while opening it.
+* **Import error for a native library**: that package has no Android build yet. Check its
+  status in the GUI.
+* **Build fails while downloading tools**: check your connection; downloads resume from the cache.
+
+## Limitations
+
+* Python 3.13 runtime, arm64-v8a and x86_64 only, minimum Android 7.0 (API 24).
+* No tkinter, pygame or Kivy yet.
+* Console apps have no interactive input.
+* Debug-signed APKs only.
+
+## Publishing to PyPI (maintainers)
+
+Releases are published by `.github/workflows/publish.yml` with PyPI Trusted Publishing
+(no API token needed). It only runs for tags that start with `v`, so the `cp313` release
+created by the factory never triggers it.
+
+One-time setup:
+
+1. Check that the name is free: https://pypi.org/project/py2apk/ should return 404.
+2. On pypi.org: *Your projects -> Publishing -> Add a new pending publisher* with
+   project `py2apk`, owner `TwoPlasmaStudios`, repository `pyapk`,
+   workflow `publish.yml`, environment `pypi`.
+3. On GitHub: *Settings -> Environments -> New environment* named `pypi`.
+
+Each release: bump `version` in `pyproject.toml`, then
+
+```
+git tag v0.3.0
+git push origin v0.3.0
+```
+
+Manual alternative: `pip install build twine`, `python -m build`, `twine upload dist/*`
+(use an API token, username `__token__`).
+
+## License
+
+MIT. Libraries in the Release keep their own licenses; CPython is under the PSF license.

py2apk-0.3.0/py2apk.egg-info/SOURCES.txt

@@ -0,0 +1,10 @@
+LICENSE
+README.md
+py2apk.py
+pyproject.toml
+py2apk.egg-info/PKG-INFO
+py2apk.egg-info/SOURCES.txt
+py2apk.egg-info/dependency_links.txt
+py2apk.egg-info/entry_points.txt
+py2apk.egg-info/requires.txt
+py2apk.egg-info/top_level.txt

py2apk-0.3.0/py2apk.egg-info/dependency_links.txt

@@ -0,0 +1 @@
+

py2apk-0.3.0/py2apk.egg-info/entry_points.txt

@@ -0,0 +1,2 @@
+[gui_scripts]
+py2apk = py2apk:main

py2apk-0.3.0/py2apk.egg-info/requires.txt

@@ -0,0 +1,3 @@
+
+[icon]
+pillow

py2apk-0.3.0/py2apk.egg-info/top_level.txt

@@ -0,0 +1 @@
+py2apk