This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author lemburg
Recipients barry, ethan.furman, lemburg, petr.viktorin, rhettinger, serhiy.storchaka, skrah
Date 2015-05-14.12:05:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <55548F6A.5040307@egenix.com>
In-reply-to <1431602974.51.0.061179480634.issue23699@psf.upfronthosting.co.za>
Content
On 14.05.2015 13:29, Petr Viktorin wrote:
> 
> Marc-Andre, Barry, you expressed interest in the macro on the mailing list; do you still think it's a good idea?

Yes.

The fact that the macro can save us more than a hundred lines
of code in Python itself is proof enough that it's useful to have.

Only once concept to learn, fewer bugs, one place to apply change
(should they become necessary), etc. etc.

This is a standard case of refactoring to simplify code and also
a standard case where we use macros in Python.
History
Date User Action Args
2015-05-14 12:05:06lemburgsetrecipients: + lemburg, barry, rhettinger, petr.viktorin, skrah, ethan.furman, serhiy.storchaka
2015-05-14 12:05:06lemburglinkissue23699 messages
2015-05-14 12:05:06lemburgcreate