durusmail: quixote-users: Illegal Python Names cookbook recipe
Illegal Python Names cookbook recipe
2004-04-05
2004-04-05
2004-04-05
Bug fixes (was: Illegal Python Names cookbook recipe)
2004-04-07
2004-04-07
Bug fixes (was: Illegal Python Names cookbookrecipe)
2004-04-07
Patches for .7a3
2004-04-07
Re: Patches for .7a3
2004-04-08
StaticFile is broken (Quixote-0.7a3, scgi-1.2a2, Apache/1.3.27, FreeBSD 4.7)
2004-04-08
Re: Patches for .7a3
2004-04-21
2004-04-21
2004-04-06
2004-04-06
2004-04-06
2004-04-06
2004-04-06
2004-04-06
2004-04-06
2004-04-07
2004-04-07
2004-04-07
2004-04-07
2004-04-07
2004-04-07
2004-04-07
Re: Illegal Python Names cookbook recipe
2004-04-07
2004-04-07
2004-04-07
2004-04-07
2004-04-07
2004-04-07
2004-04-07
2004-04-07
2004-04-07
2004-04-07
2004-04-07
2004-04-07
2004-04-08
2004-04-07
2004-04-07
2004-04-07
2004-04-06
2004-04-05
2004-04-05
2004-04-05
Re: R: [Quixote-users] Illegal Python Names cookbook recipe
2004-04-06
Illegal Python Names cookbook recipe
John Belmonte
2004-04-06
Neil Schemenauer wrote:
> Here's a patch that implements the string to string mapping idea.
> If no one objects, it will be in the next Quixote release.

I guess I have two minor objections.  One is that _q_exports was once
simply a list of Python identifiers to be published, but now is
something more convoluted and error-prone.  For example, staring at the
following, it is not inherently obvious that the first tuple item is in
URL space, while the second is in identifier space.

   _q_exports = ["foo", "bar", ("my_name", "your_name"), "baz"]

My other objection is that the extension assumes a one-to-one mapping
from URL to identifier space, and so is adding complexity without
solving the problem generally.

I'd prefer that the mechanics of Quixote remain simple.  It's easy
enough to build the mapping function on top of what already exists.

Regards,
-John


--
http:// if  ile.org/


reply