This one hasn't been fixed yet. The exact issue may depend on which flavor (util.call, util.createRequest) you're running... the basic idea is that the CherryPy server is in an "initOnly" state. So, it's not really running, but it's at least partly initialized. When it first comes up in that state, there are no request and response objects. Certain parts of the code depend on *something* halfway useful being at cherrypy.request and cherrypy.response.
I *think* util.createRequest doesn't have this particular issue, because you're (not surprisingly), creating the request. Kevin On 11/16/05, Jared Kuolt <[EMAIL PROTECTED]> wrote: > > Does this issue happen because the CherryPy server is not running? The > CherryPy thread technically *does not* exist, right? > -- Kevin Dangoor Author of the Zesty News RSS newsreader email: [EMAIL PROTECTED] company: http://www.BlazingThings.com blog: http://www.BlueSkyOnMars.com
