PyFlet CLI
PyFlet CLI is a command-line interface tool designed to facilitate the creation and management of Flet web projects. It automates the setup process and provides essential commands for project initialization and user management.
Installation
To install PyFlet CLI, use the following command:
pip install pyflet
Usage
Run the CLI using:
pyflet [COMMAND] [OPTIONS]
Commands
1. Create a Flet Web Project
pyflet create-flet-web <project_name>
Creates a new Flet web project using a predefined template.
2. Initialize a Project
pyflet init-project --reload <true/false> --project_path <path> --platform <web/android/ios>
--reload: Automatically reload the project on changes (default:true).--project_path: Path to the main Python file (default:main.py).--platform: Target platform (default:web).
3. Create a Superuser
pyflet createsuperuser
Prompts the user to enter credentials and creates a superuser in the database.
4. Get Support
pyflet support
Displays support information and the author's YouTube channel.
Configuration
Database Management
This CLI interacts with SQLite databases using the manage_sql library. The superuser creation command inserts data into the users table.
Cloning Project Templates
The CLI clones project templates from the repository:
https://github.com/webtechmoz/pyflet-models.git
It copies template files to the new project directory while replacing placeholders.
Logging
The CLI provides informative logs in different levels:
info: General information (blue)success: Successful operations (green)warning: Potential issues (yellow)error: Errors encountered (red)
Contributing
Feel free to contribute to this project by submitting issues or pull requests on GitHub.
License
This project is licensed under the MIT License.
Author
Created by DevPythonMZ.
📢 Subscribe to the YouTube channel: @devpythonMZ
Metadata
Release files for pyflet 0.3.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pyflet-0.3.2.tar.gz | 5.4 kB | Without provenance | Details for pyflet-0.3.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pyflet-0.3.2-py3-none-any.whl | Python 3 | none | any | Details for pyflet-0.3.2-py3-none-any.whl |
Total release size: 11.3 kB
Release files / pyflet-0.3.2.tar.gz
| Download URL | pyflet-0.3.2.tar.gz |
|---|---|
| Size | 5.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
402bc21768f2a213216fe2161457da32fa12010422457b40723bbf8f593eaaf1
|
|
BLAKE2b-256 checksum How to use checksums |
653e4e0d588d3102f9e734f32d51604b3d796a74bdaf30860fb9c11997e7cd7a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.5
|
Release files / pyflet-0.3.2-py3-none-any.whl
| Download URL | pyflet-0.3.2-py3-none-any.whl |
|---|---|
| Size | 5.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
21694a7b4371ddd6ef99518ef38b7e34bfb76994fd010165b25e8fa5d7d00ccb
|
|
BLAKE2b-256 checksum How to use checksums |
d9e920c82d36802872b784d2a2cf519c90184f562c5ed26dd9ff8664dd39cf35
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.5
|
Security for pyflet 0.3.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.