Skip to main content

A web micro-framework

Project description

Fresco, a web micro-framework for Python

  • Simple, powerful URL routing, request and response objects.
  • Lightweight and open to integration: you pick the templating and database libraries you want.
  • WSGI compliant: easy integration with your choice of web server, apps and middleware.

A minimal fresco web application:

from fresco import FrescoApp, GET, Response

def helloworld():
    return Response(["<h1>Hello World!</h1>"])

app = FrescoApp()
app.route('/', GET, helloworld)

Read the fresco documentation or visit the bitbucket repo for more info.

Changelog

0.7.3 (released 2016-11-01)

  • Bugfix: fixed an issue where the route cache was not correctly resetting exception information, causing spurious routing exceptions to be raised.

0.7.2 (released 2016-09-27)

  • Bugfix: multipart form data parsing has been made RFC compliant with respect to quoted-strings and backslash escaped characters.
  • The spelling of ‘process_response_handers’ has been corrected to ‘process_response_handlers’.

0.7.1 (released 2016-04-10)

  • Bugfix: the return value of the start_response callable passed to middleware layers when using FrescoApp.requestcontext now correctly returns a callable.

0.7.0 (released 2016-02-25)

  • fresco.static.serve_file no longer adds a default charset header to text files.
  • fresco.static.serve_file may take arbitrary keyword args, which are passed to the Response constructor.
  • Bugfix: date formatting in Set-Cookie headers is now RFC conformant
  • Exceptions are no longer logged if any process_exception handler returns a value.
  • Bugfix: a WSGI app mounted via route_wsgi is now passed a value for SCRIPT_NAME that corresponds to its mount point, rather than that of the application.

0.6.2 (released 2016-01-21)

  • Bugfix: a process_exception handler returning an exc_info tuple was not causing the exception to be reraised if other process_exception handlers were registered after it.

0.6.1 (released 2016-01-03)

  • Error handling: add a mechanism for process_exception handlers to reraise the original exception.

0.6.0 (released 2015-10-14)

  • Performance: RouteCollection caches route lookups for faster routing
  • Bugfix: ResponseExceptions raised during route traversal are now correctly handled
  • Views may be specified as strings when constructing routes (eg Route('/', GET, 'myapp.views.homepage').
  • Route.decorate and Route.filter may now only take a single decorator/filter function. Any additional args will be passed to the filter function (eg Route(...).filter(render, 'index.html') will now result in the render function being called with an initial positional argument of 'index.html', followed by the return value of the view function)
  • Route.decorate and Route.filter may also be used as function decorators.
  • Added fresco.subrequests to help embedding the output of one view within another.

0.5.7 (released 2015-09-11)

  • RouteCollection now implements the MutableSequence abc.
  • Bugfix: parsing multipart/form-data request bodies containg 8-bit headers no longer raises an exception

0.5.6 (released 2015-08-11)

  • Cache route lookups that result in RouteNotFound exceptions. This provides a significant speedup for applications composed of multiple RouteCollections.

0.5.5

  • User supplied data is no longer reflected in error messages raised from fresco.routeargs.RequestArg. This fixes a potential XSS vulnerability affecting versions starting from 0.5.0.

0.5.4

  • Response.set_cookie sets the cookie path to ‘/’ by default
  • Added Response.delete_cookie method
  • process_http_error_response and process_exception handlers are now called for errors raised in middleware layers.

0.5.3

  • Added FrescoApp.insert_middleware and FrescoApp.remove_middleware methods.
  • Middleware may now be added or removed after the app has already started serving requests without raising an exception.
  • Using process_http_error_response handlers to customize non-500 responses (eg a custom 404 error page) no longer causes fresco to switch to handling exceptions internally. However installing a custom 500 error handler or a process_exception handler will still switch Fresco to handling exceptions.

0.5.2

  • Bugfix: Response.buffered no longer sets an incorrect Content-Length header when the content contains non-ascii characters.

0.5.1

  • The information available in route traversal has been extended. RouteTraversal objects now contain traversal_args and traversal_kwargs fields storing the args/kwargs extracted from the path during traversal. The collections_traversed field has been extended with a route field showing the route that was selected from the collection at each stage of traversal.

  • RouteTraversal objects now have replace and build_path methods that may be used to generate modified path traversals and construct a path:

    >>> from fresco import FrescoApp
    >>> app = FrescoApp()
    >>> @route('/<lang:str>/index.html', GET, homepage, name='home')
    ... def homepage(lang):
    ...     return Response({'fr': 'Bonjour!', 'en': 'Hello!'}[lang])
    ...
    >>> traversal = next(app.get_routes('/fr/index.html'))
    >>> en_traversal = traversal.replace('home', {'lang': 'en'})
    >>> en_traversal.build_path()
    '/en/index.html'
    
  • Bugfix: no longer raises an exception when logging is enabled and the view callable does not have a ‘__name__’ attribute

0.5.0

  • The signature of ResponseException has changed.

    If a single argument is passed it is used as the response body. For example raise BadRequest('<h1>Oops!</h1>') will generate a response with the payload <h1>Oops!</h1>. Other keyword arguments are passed to the response object allowing arbitrary headers to be set in error response (eg raise BadRequest(x_error='unspecified error')).

    A side effect of this is that error messages raised from the functions in fresco.routeargs are now reflected in the response body.

    Note that the Redirect, RedirectTemporary, RedirectPermanent and MethodNotAllowed exceptions retain their existing behaviour.

  • fresco.decorators.json_response may now be called without arguments, eg:

    @json_response
    def my_view():
      return {'key': 'value'}
    
  • A new Response.json method has been added to facilitate creating JSON encoded responses without the use of a decorator.

  • fresco.routeargs.JSONPayload has been added

  • Application logging has been made more helpful

0.4.1

  • The Secure attribute of fresco.cookies.Cookie no longer takes a value. Thanks to Andrew Nelis for the patch.
  • Response.redirect and fresco.exceptions.Redirect can now take a view as their first argument, which will be resolved with urlfor (eg return Response.redirect(views.edit_widget, id=42))

0.4.0

  • Request.cookies now maps names to values (not cookie objects), simplifying cookie handling and bringing us in line with how most other frameworks treat cookies. This change breaks backwards compatibility.
  • The maxage and http_only arguments to Cookie.__init__ and Response.add_cookie have been renamed to max_age and httponly respectively, reflecting the spelling used in the Set-Cookie header (‘Max-Age’ and ‘HttpOnly’). This change breaks backwards compatibility.
  • Changed FrescoApp’s constructor to have the same signature as RouteCollection. You can get the old behavior by using the views and path keyword arguments. This change breaks backwards compatibility.
  • Removed blinker dependency and associated signals. These were never documented and the application hooks added in this version provide a more flexible replacement. This change breaks backwards compatibility.
  • Removed the deprecated url method added to view functions This change breaks backwards compatibility.

0.3.14

  • Added request.is_secure property.
  • Added filters keyword argument to Route.
  • Calling Response() with no arguments now creates a 204 No Content response.
  • Calling Response('some string') no longer causes the string to be output byte-by-byte.
  • Added Response.add_vary method.
  • Response cookies have had the Version attribute removed, bringing them in line with RFC6265.
  • Added hooks to FrescoApp: process_request, process_response, process_view, process_exception, process_http_error_response, and finish_request.
  • Deprecated blinker signals in FrescoApp. FrescoApp.route_matched, FrescoApp.view_finished and FrescoApp.before_response should be replaced by the equivalent appliation hooks (process_request, process_view and process_response respectively).

0.3.13

  • Bugfix for FrescoApp.requestcontext_put and FrescoApp.requestcontext_patch which were raising a TypeError

0.3.12

  • Added FrescoApp.requestcontext_post, FrescoApp.requestcontext_put, FrescoApp.requestcontext_patch and FrescoApp.requestcontext_delete, to simplify direct testing of view functions.
  • Added a flag to disable middleware processing in requestcontext, eg FrescoApp.requestcontext(middleware=False). For middleware heavy stacks this may be used to speed up testing of individual views.

0.3.11

  • Added request.body and request.body_bytes properties
  • Added a request.get_json method to access JSON request payloads
  • Deprecated view_function.url()
  • Added RouteCollection.remove and RouteCollection.replace methods, making it easier to extend and modify RouteCollections.

0.3.10

  • Invalid character data in the request body no longer causes an exception.

0.3.9

  • fresco.decorators.extract_* methods are now deprecated in favour of the functions in fresco.routeargs
  • Fixed an error in RouteArg when using a conversion function and a value is not supplied
  • Added fresco.decorators.json_response
  • Added support for python 3.4 and dropped support for python 3.2

0.3.8

  • A new routearg function allows RouteArgs to be constructed dynamically
  • Renamed Route.decorate to Route.wrap
  • Added Route.filter to pipe the output of the view through a custom filter function

0.3.7

  • Bugfix for RouteArg when using a default value
  • Bugfix for urlfor when using positional arguments.
  • Added decorate method for Route objects.
  • Added fresco.routing.register_converter class decorator for simpler registration of routing pattern converters.
  • Added fresco.util.common.object_or_404.
  • Bugfix: fresco.util.urls.make_query no longer sorts key value pairs into alphabetical order, but preserves the original ordering.
  • fresco.static.serve_static_file now checks for certain malformed requests and returns an HTTP bad request status

0.3.6

  • Improved startup time for apps with lots of middleware

  • fresco.context no longer copies values from the parent when setting up a new request context. This makes it easier for libraries using fresco.context to cache resources per-request.

  • Bugfix for FrescoApp.requestcontext, which was creating duplicate context frames.

  • FrescoApp.view_finished signal now passes the request object to subscribers

  • Route objects can now take a tuple of positional args to pass to views:

    Route(POST, '/contact', args=('anne@example.com',))
    
  • The route class used by RouteCollection is now configurable, allowing apps to define custom routing classes.

  • fresco.routearg.RouteKwarg has been renamed to RouteArg and now works for positional arguments via Route(..., args=...)

  • Request.make_url now accepts two new optional arguments, query_add and query_replace. This facilitates building urls based on the current query string with selected values added or replaced.

  • Bugfix: improperly encoded paths now cause a 400 bad response to be returned rather than raising UnicodeDecodeError

0.3.5

  • FrescoApp.requestcontext() now invokes all registered middleware. This can be useful for testing views that rely on middleware to set environ keys or provide other services
  • RouteArg classes have been expanded and are now in a separate module, fresco.routeargs

0.3.4

  • Bugfix: Request.form was not handling unicode data in GET requests correctly
  • fresco.core.request_class has been moved to FrescoApp.request_class
  • Route arguments can take default arguments for url generation
  • Added tox for testing: fresco is now tested and works with Python 2.6, 2.7, 3.2 and 3.3

0.3.3

  • Bugfix: Request.make_url was double quoting URLs in some circumstances

0.3.2

  • Improved handling for ResponseExceptions raised during route traversal

0.3.1

  • Bugfix: routing arguments were being incorrectly converted to bytestrings in python2
  • Bugfix: urlfor works correctly with dynamic routes

0.3.0

Note that upgrading to this version will require changes to your application

  • View functions are no longer passed a request object as a positional argument
  • The syntax used to reference views by name has changed from urlfor('mymodule:view') to urlfor('mymodule.view').
  • Routing: named routes are now supported, eg Route('/', GET, myview, name='homepage'). These can later be accessed by eg urlfor('homepage'). The old route tagging facility has been removed.
  • Routing: Support for delegating paths to other routeable objects
  • fresco.exceptions.NotFoundFinal has been replaced by NotFound(final=True)
  • Experimental Python 3 support

0.2.4

  • Bugfix: setting the logger property on a FrescoApp no longer causes errors

0.2.3

  • FrescoApp objects now have an options dictionary for application level settings
  • Added serve_static_file function
  • Added support for signals with blinker
  • urlfor now requires fully qualified module names if called with a string argument

0.2.2

  • Bug: URL generation broken when HTTP_HOST does not contain port number

0.2.1

  • Bugfixes for beaker session support and broken URL generation when ‘X-Forwarded-SSL: off’ header supplied

0.2.0

  • Removed dependency on Pesto

0.1 (unreleased)

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Filename, size & hash SHA256 hash help File type Python version Upload date
fresco-0.7.3.tar.gz (110.4 kB) Copy SHA256 hash SHA256 Source None

Supported by

Elastic Elastic Search Pingdom Pingdom Monitoring Google Google BigQuery Sentry Sentry Error logging AWS AWS Cloud computing DataDog DataDog Monitoring Fastly Fastly CDN SignalFx SignalFx Supporter DigiCert DigiCert EV certificate StatusPage StatusPage Status page