On Thu, Feb 1, 2018 at 1:34 PM, Terry Reedy <tjre...@udel.edu> wrote:

> On 1/31/2018 6:15 PM, Chris Barker wrote:
> I still have no idea why there is such resistance to this [spelling
>> corrected]
>   M.-A. Lemburg already summarized his view of the specifics for this
> issue.  And see below.

Thanks for that, I know I phrased it in no-very-open-for-discussion way,
but that was what I was looking for. Frankly, I disagree with much of that,
but it's been clearly layed out, which is what is needed to make a decision.

> (I'm assuming the OP (or someone) will do all the actual work of coding
>> and updating docs....)
> At least one core developer has to *volunteer* to review, likely edit or
> request edits, merge, and *take responsibility* for the consequences of the
> PR.

Fair enough -- it would be quite reasonable to say that this (or anything)
wont get included u less a core dev decides it worth his/her time to bring
it in -- but that is different than saying it won't be brought in

> I take this to mean that normal special cases are not special enough but
> some special special cases are.  The meta meaning is that decisions are not
> mechanical and require tradeoffs, and that people will honestly disagree in
> close cases.

yup -- there seems to be much resistance, and not much support -- so I
guess we're done.



Christopher Barker, Ph.D.

Emergency Response Division
NOAA/NOS/OR&R            (206) 526-6959   voice
7600 Sand Point Way NE   (206) 526-6329   fax
Seattle, WA  98115       (206) 526-6317   main reception

Python-ideas mailing list
Code of Conduct: http://python.org/psf/codeofconduct/

Reply via email to