When I am adding a static view like this:
cfg = config.Configurator(...)
cfg.add_static_view(name='static', path='MyPgk:static')
# And I want to add a view for 'favicon.ico'.
cfg.add_route(name='favicon', pattern='/favicon.ico')
cfg.add_view(route_name='favicon', view='MyPgk.views.mymodule.favicon_view')
I am trying to add that favicon.ico annoying default path of /favicon.ico called by the browser if it’s undefined in the webpage. I would like to use the example at http://docs.pylonsproject.org/projects/pyramid_cookbook/en/latest/files.html and modify it to have:
def favicon_view(request, cache=dict()):
if (not cache):
_path_to_MyPkg_static = __WHAT_GOES_HERE__
_icon = open(os.path.join(_path_to_MyPkg_static, 'favicon.ico')).read()
cache['response'] = Response(content_type='image/x-icon', body=_icon)
return cache['response']
Since, I can’t really define the _here proposed in the example, how can I make it dependent to request to get the actual full path at runtime? Or do I really have to deal with:
_here = os.path.dirname(__file__)
_path_to_MyPkg_static = os.path.join(os.path.dirname(_here), 'static')
and having to be careful when I decide to refactor and put the view in another pkg or subpackage, or where-ever?
Something equivalent to request.static_path() but instead of getting the url path, to actually get a directory path:
request.static_file_path('static') -> /path/to/site-packages/MyPkg/static
Thanks,
You can use the
pkg_resourcesmodule to make paths that are relative to Python modules (and thus, independent of the module that retrieves them). For example:Just substitute
os.pathwith whatever module that is the parent of your static files.EDIT: If you need to remember that
'static'route mapped to'MyPkg:static', then the easiest way is to save it in some dictionary in the first place:and then simply retrieve the path:
If that’s impossible, though (e.g. you don’t have access to the
cfgobject), you can retrieve this path, it’s just quite painful. Here’s a sample function that uses undocumented calls (and so may change in future Pyramid versions) and ignores some additional settings (likeroute_prefixconfiguration variable):In your case, it should work like this: