Message 68409 - Python tracker

➜

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	mark
Recipients	akuchling, amaury.forgeotdarc, jimjjewett, mark, pitrou, rsc, timehorse
Date	2008-06-19.14:15:50
SpamBayes Score	0.08445452
Marked as misclassified	No
Message-id	<200806191515.45882.mark@qtrac.eu>
In-reply-to	<1213876892.22.0.67555623534.issue2636@psf.upfronthosting.co.za>

Content
[snip] It seems to me that both using a special prefix or adding an option are adding a lot of baggage and will increase the learning curve. The nice thing about (3) (even without slicing) is that it seems a v. natural extension. But (2) seems magical (i.e., Perl-like rather than Pythonic) which I really don't like. BTW I just noticed this: '<_sre.SRE_Pattern object at 0x9ded020>' >>> "{0!r}".format(rx) '<_sre.SRE_Pattern object at 0x9ded020>' >>> "{0!s}".format(rx) '<_sre.SRE_Pattern object at 0x9ded020>' >>> "{0!a}".format(rx) That's fair enough, but maybe for !s the output should be rx.pattern?

[snip]

It seems to me that both using a special prefix or adding an option are
adding a lot of baggage and will increase the learning curve.

The nice thing about (3) (even without slicing) is that it seems a v.
natural extension. But (2) seems magical (i.e., Perl-like rather than
Pythonic) which I really don't like.

BTW I just noticed this:

'<_sre.SRE_Pattern object at 0x9ded020>'
>>> "{0!r}".format(rx)
'<_sre.SRE_Pattern object at 0x9ded020>'
>>> "{0!s}".format(rx)
'<_sre.SRE_Pattern object at 0x9ded020>'
>>> "{0!a}".format(rx)

That's fair enough, but maybe for !s the output should be rx.pattern?

History
Date	User	Action	Args
2008-06-19 14:15:55	mark	set	spambayes_score: 0.0844545 -> 0.08445452 recipients: + mark, akuchling, jimjjewett, amaury.forgeotdarc, pitrou, rsc, timehorse
2008-06-19 14:15:53	mark	link	issue2636 messages
2008-06-19 14:15:51	mark	create