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 r.david.murray
Recipients BreamoreBoy, collinwinter, hwundram, r.david.murray, rhettinger, terry.reedy
Date 2010-09-23.01:04:30
SpamBayes Score 2.6791206e-06
Marked as misclassified No
Message-id <1285203873.96.0.523776364576.issue1491804@psf.upfronthosting.co.za>
In-reply-to
Content
In fact, I find the proposed syntax *less* obvious than the slice syntax, for sorted.  IOW, I'd be -1 on adding these to sorted.  The potentially useful case is between

    l[a:b] = sorted(l[a:b})

vs

    l.sort(start=a, stop=b)

where the interesting bit is that the sort takes place in place (no memory copy).

I still find the slice syntax clearer :), and it's not clear that the savings of the memory copy for a few programs that use it is worth the added complexity for all other programs.  So I concur with Raymond's rejection.
History
Date User Action Args
2010-09-23 01:04:34r.david.murraysetrecipients: + r.david.murray, collinwinter, rhettinger, terry.reedy, hwundram, BreamoreBoy
2010-09-23 01:04:33r.david.murraysetmessageid: <1285203873.96.0.523776364576.issue1491804@psf.upfronthosting.co.za>
2010-09-23 01:04:32r.david.murraylinkissue1491804 messages
2010-09-23 01:04:31r.david.murraycreate