Flask-Via
Inspired by the Django URL configuration system, Flask-Via is designed to add similar functionality to Flask applications which have grown beyond a simple single file application.
Example
from flask import Flask
from flask.ext.via import Via
from flask.ext.via.routers.default import Functional
app = Flask(__name__)
def foo(bar=None):
return 'Foo View!'
routes = [
Functional('/foo', foo),
Functional('/foo/<bar>', foo, endpoint='foo2'),
]
via = Via()
via.init_app(app, route_module='flask_via.examples.basic')
if __name__ == "__main__":
app.run(debug=True)
Why?
Growing your application can be quite difficult when it’s not always clear where and how your routes are discovered. This can lead to a cluttered application factory method when all your routes are defined at application creation - resulting in code which is difficult to maintain, not to mention messy.
A better solution is to define your routes in a routes.py and automatically load them at application start up. This is what Flask-Via helps to do.
Third party Flask extensions don’t always follow the same conventions for adding routes to an application, so Flask-Via has been designed to be easy for developers to write their own custom routers. For an example of this, take a look at the bundled Flask-Restful Resource router.
If you do write a custom router that is useful to you, it will probably be useful to someone else so please do contribute back :)
Links
Change Log
2015.1.1
Fix: Setup to allow bdist_wheel installs
2014.05.19.2
Improved: @joonathan added kwargs passing to the Blueprint Router
Improved: init_app and added __init__
Added: Deprecation warning to Basic router
2014.05.19.1
Hotfix: Fixed issue where routes would be reregistered with an app incorrectly in the event of multiple app creations
2014.05.19
Feature: Include now supports endpoint prefixing
Feature: Blueprint router can now take a blueprint instance
Feature: Added support for VIA_ROUTES_NAME to set a common routes name
Deprecated: Basic Router in favour of the Functional router
Improved: Pluggable Router API is now cleaner
Improved: Test Suite now uses PyTest
Improved: ImproperlyConfigured now raised if routes module is not defined in either init_app or in application configuration via VIA_ROUTES_MODULE
2014.05.08
Feature: Flask Admin Router
Feature: Include url_prefix option
2014.05.06
Feature: Flask extension initialisation
Feature: Basic and Pluggable Flask Routers
Feature: Flask-Restful Router
Feature: Ability to include other routes
Feature: Ability to register blueprints
Metadata
Release files for Flask-Via 2015.1.1
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 |
|---|---|---|---|---|
| Flask-Via-2015.1.1.tar.gz | 14.9 kB | Without provenance | Details for Flask-Via-2015.1.1.tar.gz |
Release files / Flask-Via-2015.1.1.tar.gz
| Download URL | Flask-Via-2015.1.1.tar.gz |
|---|---|
| Size | 14.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8faf7e0ff093a26fba1826aaeeda30b0adaed3debe495025d7417c8a2b9552c3
|
|
BLAKE2b-256 checksum How to use checksums |
09e33731674ca2c82cf07785d073e33ba91890989427516c0f64dcd11d315080
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for Flask-Via 2015.1.1
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.