RetroSearch Browse

Thu Jul 9 16:35:01 CEST 2015 · https://mail.python.org/pipermail/python-dev/2015-July/140709.html

On Thu, Jul 9, 2015 at 7:41 AM, Guido van Rossum <guido at python.org> wrote:

> On Wed, Jul 8, 2015 at 10:19 PM, Serhiy Storchaka <storchaka at gmail.com>
> wrote:
>>
>> On 08.07.15 01:45, Raymond Hettinger wrote:
>>>
>>> P.S.  I don't think python-dev post was necessary or helpful (and I still
>>> haven't had a chance to read the whole thread).  It would have been
>>> sufficient to assign the tracker entry back to me.
>>
>>
>> Well, I'll open new issue and assign it to you for every your commit that
>> looks questionable to me.
>
>
> That sounds like a fine solution, and a good conclusion of the thread.

I don't have a very strong opinion on the solution, but should the dev guide
be updated to clarify the feelings expressed about the mailing lists in this
thread?  My interpretation of the dev guide always left me with the feeling
that following python-dev was expected for Python core devs:

  * https://docs.python.org/devguide/communication.html#communication

  * https://docs.python.org/devguide/coredev.html#mailing-lists

-- Meador

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2015-July/140709.html below:

[Python-Dev] cpython: Tighten-up code in the set iterator to use an entry pointer rather than