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
Kendall Clark
2004-04-07
On Tue, Apr 06, 2004 at 07:18:39PM -0500, Martin Maney wrote:
> On Tue, Apr 06, 2004 at 05:27:41PM -0500, Jason E. Sibre wrote:
> > I still prefer something a bit more explicit than the tuplized 'mapping'.
>
> +1 with bells on.

I agreed with Neil that the embedded tuple was better than my first
proposal, an embedded dictionary. Neither seemed more magical or
implicit than the other to me.

That being said, we could make it really explicit, thus:

_q_exports = ["foo", "bar",
              {"external":"foo.bar", "internal": "foo_bar"} ]

The merit of this version -- setting aside its verbosity -- is that it
should help us discriminate between worries about implicitness and
worries motivated by something else.

Kendall
--
This sucks more than anything that has ever sucked before. -- Butthead


reply