On Thu, Jul 19, 2012 at 1:50 PM, C Anthony Risinger <[email protected]> wrote: > On Thu, Jul 19, 2012 at 1:32 AM, C Anthony Risinger <[email protected]> wrote: >> On Tue, Jul 17, 2012 at 11:45 PM, Roberto De Ioris <[email protected]> wrote: >>> >>> Interpolations are managed out of config file parsers, so they must work >>> independently by it: >>> >>> { "uwsgi": { >>> "socket": "@(pippo)", >>> "print": "$(PATH)" >>> } >>> } >>> >>> works for me >> >> that's what i thought too ... and what i recall from previous readings >> into the code ... it *should* work. your example however *isn't* >> working for me: > > [...] > >> ... same exact result in 1.2.4, but here is another example: > > [...] > >> ... same setup works fine if i use INI > > [...] > >> ... am i doing something obviously wrong here? > > well i have no idea how it's working for you, but i found the traced > the problem ... > > current head does NOT define UWSGI_OPT_IMMEDIATE flag for `--json` or > `--js`! this flag IS defined for `--ini`, `--yaml`, and `--sqlite` > > maybe it was removed by mistake, not sure. > > https://github.com/unbit/uwsgi/pull/9/files
how did this ever work? i went back almost 600 commits and it looks like UWSGI_OPT_IMMEDIATE has never been defined ... unless i'm missing a different mechanism, it seems busted since the option parsing was reworked, at the least? -- C Anthony _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
