Of all the pieces of Paste I'd like to split off into its own package,
I think static file serving is at the top. Half of the time I make
packages rely on Paste lately it's because I need to serve a few
static files. Maybe that would be a better direction for (pseudo-)
inclusion?
On Tue, Jun 30, 2009 at 7:36 PM, Chris McDonough<chrism@???> wrote:
>
> For various reasons, we needed a StaticURLParser variant that used the "global"
> pkg_resources API (pkg_resources.resource_stream, pkg_resources.resource_string,
> etc) as opposed to calling methods on a distribution object like
> paste.urlparser.PkgResourcesURLParser does. This means it's limited to
> obtaining resources from within a package, rather than a distribution like
> PkgResourceURLParser can do, but it can also use the __loader__ "adapter"
> indirection provided by pkg_resources to use a different "provider" as necessary
>
> Here is the implementation:
>
> http://svn.repoze.org/repoze.bfg/trunk/repoze/bfg/static.py
>
> It has full test coverage and all that jazz. I'd be willing to do the work to
> put it into Paste if folks wanted it; if not, no big thing.
>
> - C
>
> >
>
--
Ian Bicking | http://blog.ianbicking.org | http://topplabs.org/civichacker
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Paste Users" group.
To post to this group, send email to paste-users@???
To unsubscribe from this group, send email to paste-users+unsubscribe@???
For more options, visit this group at
http://groups.google.com/group/paste-users?hl=en
-~----------~----~----~----~------~----~------~--~---
