On 06.01.2014 22:34, Larry Hastings wrote:
p.s.
For what it's worth, the documentation for match() dodges this problem by
outright lying. It claims
that the prototype for the function is:
match(string[, pos[, endpos]])
which is a lie. pattern_match() parses its arguments by
FWIW, this would probably be better on python-dev, but maybe you wanted to cut
down on potential noise and churn?
On Jan 06, 2014, at 01:34 PM, Larry Hastings wrote:
The thing is, I feel like this is borderline between bug fix and new feature.
But without adding this, we would make a lot of the
On 01/06/2014 02:10 PM, M.-A. Lemburg wrote:
Looks like a documentation bug to me. Several functions were changed
to be keyword aware some years ago and the docs you quoted still list
the old positional format.
Your intuition was spot on. Revision 0a97f5dde3a7, by the effbot, Tue
Oct 03
On 01/06/2014 02:21 PM, Barry Warsaw wrote:
On Jan 06, 2014, at 01:34 PM, Larry Hastings wrote:
The thing is, I feel like this is borderline between bug fix and new feature.
But without adding this, we would make a lot of the Argument Clinic
conversions pretty messy. So I want to check it in.
On 7 Jan 2014 07:34, Ethan Furman et...@stoneleaf.us wrote:
On 01/06/2014 02:21 PM, Barry Warsaw wrote:
On Jan 06, 2014, at 01:34 PM, Larry Hastings wrote:
The thing is, I feel like this is borderline between bug fix and new
feature.
But without adding this, we would make a lot of the
On 1/6/2014 5:21 PM, Barry Warsaw wrote:
FWIW, this would probably be better on python-dev, but maybe you wanted to cut
down on potential noise and churn?
Better here, I think.
On Jan 06, 2014, at 01:34 PM, Larry Hastings wrote:
The thing is, I feel like this is borderline between bug fix