[Python-Dev] @decorators, the PEP and the "options" out there?
Mark 'Kamikaze' Hughes
kamikaze at kuoi.asui.uidaho.edu
Mon Aug 9 03:11:00 CEST 2004
More information about the Python-Dev mailing list
Mon Aug 9 03:11:00 CEST 2004
- Previous message: [Python-Dev] @decorators, the PEP and the "options" out there?
- Next message: [Python-Dev] @decorators, the PEP and the "options" out there?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Mon, Aug 09, 2004 at 12:01:47PM +1200 in <200408090001.i7901lsx005666 at cosc353.cosc.canterbury.ac.nz>, Greg Ewing <greg at cosc.canterbury.ac.nz> spake: >IxokaI <ixokai at gmail.com>: >> '"define methy1 at staticmethod" is wrong, but "at >> staticmethod define methy2" is right. >Pardon? They *both* sound like utter nonsense to me. >That's the other main objection I have to '@'. I just >can't help pronouncing it in my head as "at". Try pronouncing it as "attribute" (n.) or "attribute" (v.). Either one makes sense in context. -- <a href="http://kuoi.asui.uidaho.edu/~kamikaze/"> Mark Hughes </a> "Doing the impossible makes us mighty." -Captain Malcolm Reynolds, Firefly
- Previous message: [Python-Dev] @decorators, the PEP and the "options" out there?
- Next message: [Python-Dev] @decorators, the PEP and the "options" out there?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list