[prev in list] [next in list] [prev in thread] [next in thread] 

List:       python-web-sig
Subject:    [Web-SIG] Standardising containment.
From:       pje () telecommunity ! com (Phillip J !  Eby)
Date:       2004-09-07 21:11:17
Message-ID: 5.1.1.6.0.20040907150800.028698c0 () mail ! telecommunity ! com
[Download RAW message or body]

At 12:45 PM 9/7/04 +0200, Paul Boddie wrote:

>P.S. Although __file__ is supposedly Pythonic, it's quite possible that
>the
>resources associated with an application don't always reside in an
>easily
>discoverable location relative to the application's modules - ie. they
>get
>installed in some opaquely-named directory which might vary with the
>framework being used, even it is located relative to those modules in
>the
>filesystem. Perhaps an explicit resource path (or context path) needs
>defining somewhere.

Note that existing frameworks and applications already have lots of ways to 
handle this.  For example, applications like Roundup, MoinMoin, and 
Pyblosxom either have prescribed layouts or use configuration files that 
indicate where things are.

Thus, this is an area where adding a facility to WSGI is just creating 
"choice N+1" instead of actually reducing unnecessary choice.

[prev in list] [next in list] [prev in thread] [next in thread]