[Web-SIG] San Francisco PYLONS PROJECT MINICONF #0 -- April 29th

2011-04-14 Thread whit
Apologies for the crossposting. Free half day conference in SF, still open speaking slots (all topics considered). Please excuse the roughness of our web presence. - Sign up at http://www.meetup.com/sfbay-pylons-proj/events/17306893/ - Read info and post suggestions and talk submissions at

Re: [Web-SIG] A Python Web Application Package and Format

2011-04-14 Thread Alice Bevan–McGregor
On 2011-04-14 08:53:55 -0700, Randy Syring said: Just wondering if Windows/IIS is being kept in mind as this discussion is going on. I am having a hard time conceptualizing the things being discussed, so can't really tell myself. I'm trying pretty hard to ensure that non-compatible OS featur

Re: [Web-SIG] A Python Web Application Package and Format

2011-04-14 Thread Ian Bicking
I think there's a general concept we should have, which I'll call a "script" -- but basically it's a script to run (__main__-style), a callable to call (module:name), or a URL to fetch internally. I want to keep this distinct from anything long-running, which is a much more complex deal. I think

Re: [Web-SIG] A Python Web Application Package and Format

2011-04-14 Thread Ian Bicking
On Thu, Apr 14, 2011 at 2:53 AM, Graham Dumpleton < graham.dumple...@gmail.com> wrote: > On 14 April 2011 16:57, Alice Bevan–McGregor wrote: > >> 3. Define how to get the WSGI app. This is WSGI specific, but (1) is > >> *not* WSGI specific (it's only Python specific, and would apply well to > >>

Re: [Web-SIG] A Python Web Application Package and Format

2011-04-14 Thread Randy Syring
On 04/14/2011 11:45 AM, Eric Larson wrote: ...regarding apache/nginx config if necessary, but basing that on the expectation there is a single script is a better approach than presuming a config can provide enough information to eventually create some script that apache/nginx/etc. might need t

Re: [Web-SIG] A Python Web Application Package and Format

2011-04-14 Thread Eric Larson
Hi, On Apr 14, 2011, at 4:02 AM, Graham Dumpleton wrote: > On 14 April 2011 18:22, Alice Bevan–McGregor wrote: >> Howdy! >> >> I suspect you're thinking a little too low-level. > > Exactly, I am trying to walk before running. Things always fall down > here because people try and take too lar

Re: [Web-SIG] A Python Web Application Package and Format

2011-04-14 Thread Graham Dumpleton
On 14 April 2011 18:22, Alice Bevan–McGregor wrote: > Howdy! > > I suspect you're thinking a little too low-level. Exactly, I am trying to walk before running. Things always fall down here because people try and take too large a leap rather than an incremental approach, solving one small problem

Re: [Web-SIG] A Python Web Application Package and Format

2011-04-14 Thread Alice Bevan–McGregor
Howdy! I suspect you're thinking a little too low-level. On 2011-04-14 00:53:09 -0700, Graham Dumpleton said: On 14 April 2011 16:57, Alice Bevan–McGregor wrote: 3. Define how to get the WSGI app.  This is WSGI specific, but (1) is *not* WSGI specific (it's only Python specific, and would ap

Re: [Web-SIG] A Python Web Application Package and Format

2011-04-14 Thread Roberto De Ioris
Il giorno 14/apr/2011, alle ore 09.53, Graham Dumpleton ha scritto: > On 14 April 2011 16:57, Alice Bevan–McGregor wrote: >>> 3. Define how to get the WSGI app. This is WSGI specific, but (1) is >>> *not* WSGI specific (it's only Python specific, and would apply well to >>> other platforms) >>

Re: [Web-SIG] A Python Web Application Package and Format

2011-04-14 Thread Graham Dumpleton
On 14 April 2011 16:57, Alice Bevan–McGregor wrote: >> 3. Define how to get the WSGI app.  This is WSGI specific, but (1) is >> *not* WSGI specific (it's only Python specific, and would apply well to >> other platforms) > > I could imagine there would be multiple "application types": > > :: WSGI a