FlightPY | A Modern Python Web Framework
FlightPY is heavily inspired by the Express framework. Python is one of my favorite languages, and it deserves to have some updated tooling for web developers.
Why Another Framework
Isn't Flask or Django enough? Probably. But the thing I've found with using those frameworks is that they seem to be on either end of the web development spectrum as far as Python is concerned.
FlightPY will sit somewhere in between Flask and Django. Where Flask is basically BYOE (bring your own everything) and Django is all Batteries included (and you need to know how everything works the Django way), FlightPY will attempt to provide the modularity neccessary for lightweight Python apps (via awesome middlewares), while still providing enough out of the box to get stuff done quickly.
A Modern Approach
A lot of the python frameworks were developed at a time when the web was a very different place. Some of the best features of Python may not have even existed yet. Also, some frameworks were designed and are still maintaining Python2 legacy code that has reached EOL. FlightPY is designed for Python3+ and never plans to support Python2. This allows clear focus to be on the features of the framework and not maintaining legacy code.
A Modular Middleware Approach
There are some very opinionated frameworks out there, like Django. For every opinion it has, it increases the steepness of the learning curve for that framework, along with the amount of time to actually build anything.
On the flip side of that, frameworks like Flask are very unopinionated, but they leave it up to you to decide if or what you want to use for almost every part of your project. While its minimialisitic (yay!), I've often found myself in the same situation of try to make a decision that I wish the framework would've already made for me.
There is a delicate balance to which opinions are important enough to have to provide some level of common functionality, while also not increasing the learning curve of the system as a whole.
That is where the FlightPY middlewares come into play. The core framework is very small. Its actually smaller than Flask. The rest of the functionality comes from middlewares. If you don't import them, they won't bloat your project.
Metadata
Release files for flightpy 0.0.0.post4
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 |
|---|---|---|---|---|
| flightpy-0.0.0.post4.tar.gz | 3.9 kB | Without provenance | Details for flightpy-0.0.0.post4.tar.gz |
Release files / flightpy-0.0.0.post4.tar.gz
| Download URL | flightpy-0.0.0.post4.tar.gz |
|---|---|
| Size | 3.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3b40fd0f6523672deb8b7f05934ba6c14981f9ed3043078a14c952dc384be2bc
|
|
BLAKE2b-256 checksum How to use checksums |
3ff9c3f7d0d683297c72c3f84718cce10c8f7c31e3e7bea0e9a15b2009b55f2f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.48.0 CPython/3.8.3
|
Security for flightpy 0.0.0.post4
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.