This is a pre-production deployment of Warehouse, however changes made here WILL affect the production instance of PyPI.
Latest Version Dependencies status unknown Test status unknown Test coverage unknown
Project Description

![Build Image](

Adaption of Flask Blueprints to form ‘Endpoints’, with a focus on the path and method of a resource.

Class based views didn’t cut it for me, so this is what I arrived at.

Go from this:

` >>> blueprint = Blueprint('users', __name__, url_prefix='/users') >>> @blueprint.route('/<string:user_id>', method=['DELETE']) `

to this:

` >>> endpoint = Endpoint('users', '/users', __name__) >>> @endpoint.delete('/<string:user_id>') `

Makes sense for my purposes, and I can still include per-route decorators, which is where classed based views fell down for me. This makes an incredible amount of sense in a HTTP API implementation where you need fine-grained control. For example, in the event that you want to implement a ‘lockdown’ of your API, you can include a specific decorator for ‘changing’ endpoints.

` >>> >>> @lockdown(severity=2) `

# Installation

` $ pip install flask-endpoint `

Or if you prefer easy-install:

` $ alias easy_install="pip install $1" $ easy_install flask-redis `

# Configuration

None (really!). Instead of running the following:

` >>> from flask import Blueprint `

just run:

` >>> from flask_endpoint import Endpoint `

and configure:

` >>> endpoint = Endpoint('users', '/users', __name__) >>> >>>'/url') >>> @endpoint.get() >>> @endpoint.get('/url') `

The package supports all of the methods available to flask (GET/POST/PUT/PATCH/DELETE/OPTIONS/HEAD).

All of the standard blueprint optional arguments will be passed through (sans url-prefix), which makes this fairly easy to adopt.

When it comes time to register them, do as you would a Blueprint:

` >>> app.register_blueprint(endpoint) `

# Contribution

  1. Check for open issues or open a fresh issue to start a discussion around a feature idea or a bug. There is a Contributor Friendly tag for issues that should be ideal for people who are not very familiar with the codebase yet.
  2. Fork [the repository]( on Github to start making your changes to the master branch (or branch off of it).
  3. Write a test which shows that the bug was fixed or that the feature works as expected.
  4. Send a pull request and bug the maintainer until it gets merged and published.
Release History

Release History


This version

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

Download Files

Download Files

TODO: Brief introduction on what you do with files - including link to relevant help section.

File Name & Checksum SHA256 Checksum Help Version File Type Upload Date
flask-endpoint-0.1.tar.gz (4.1 kB) Copy SHA256 Checksum SHA256 Source Jan 18, 2015

Supported By

WebFaction WebFaction Technical Writing Elastic Elastic Search Pingdom Pingdom Monitoring Dyn Dyn DNS HPE HPE Development Sentry Sentry Error Logging CloudAMQP CloudAMQP RabbitMQ Heroku Heroku PaaS Kabu Creative Kabu Creative UX & Design Fastly Fastly CDN DigiCert DigiCert EV Certificate Rackspace Rackspace Cloud Servers DreamHost DreamHost Log Hosting