[python-committers] And Now for Something Completely Different
brett at python.org
Tue Jul 24 12:12:44 EDT 2018
On Tue, 24 Jul 2018 at 07:46 Nick Coghlan <ncoghlan at gmail.com> wrote:
> On 21 July 2018 at 04:30, Donald Stufft <donald at stufft.io> wrote:
> > On Jul 19, 2018, at 7:47 PM, Victor Stinner <vstinner at redhat.com> wrote:
> > It seems that the main question for a new governance is how to take a
> > decision on PEPs (accept or reject them with some variants like
> > Deferred). I read that core developers are unable to make a decision
> > themselves (fail to reach a consensus) and that letting core
> > developers decide would make Python "inconsistent" (as if only a
> > single BDFL is able to keep Python consistent). I also read that the
> > BDFL is required to make unpopular decisions to enhance Python.
> > I think the core difference behind all of the proposals, when you get
> > to
> > brass tacks, will be the vision for where the langauge goes. There are
> > independently good ideas that maybe should not be accepted, because they
> > compromise the vision for the worse, or ideas that seem poor on the tin
> > that
> > once they get added they mesh well with the overall language.
> > The further you scale up the number of people directly deciding the
> > direction
> > of the language, the more likely you will find inconsistency. No two
> > have
> > the same design sense, and so if you ask two people you're likely to get
> > least two answers.
> One of the things that puzzles me about the "Who will set the
> direction of the language if Guido doesn't do it?" concern is that
> from my perspective, this is something that Guido mostly *didn't* do
> (and I'm OK with that). Python has never had a clear road map in the
> 15+ years I've been part of the core development community - it's just
> had assorted projects that different individuals have driven to
> varying levels of completion based on the strength of their
> convictions about the topic, and the time they've had available to
> devote to driving it (along with a few "definitely not" issues written
> down in the form of rejected PEPs).
> The projects that Guido has been directly involved in driving have
> been more ambitious in scope than most other folks would be prepared
> to pursue (e.g. Py3k, asyncio, type hinting), but there have been
> significant changes he accepted that were originated by others (such
> as f-strings and assignment expressions), as well as significant
> topics where he largely delegated decision making to others (such as
> Unicode handling, project dependency management, the import system,
> and scientific computing).
> If I were to write an article like
> today, the specific topics I'd mention would be different, but the
> overall tone would be similar.
So I think if you replaced "direction" with "tone" in your opening phrase
then that would encompass what a lot of people are worried about. It isn't
necessarily about a roadmap (which we obviously have never had written down
;) , but Guido did set a tone for the language overall which he kept in his
head and worked towards through thought and instinct.
But Guido has done directional things like saying the removal of the GIL
would be acceptable if single-threaded performance was kept, even
potentially at the cost of a bit of the C API. So while we have never laid
out explicit plans for the next 1, 5, or 10 years, I think there has been
guidance and an implicit direction of where the language should be headed.
> And I think that's inevitable in an environment driven primarily by
> volunteer and sponsored development: the time to pursue particular
> activities has to come from somewhere, and that's either going to be
> the intrinsic motivations of individuals donating their own time, or
> else the extrinsic motivation of folks pursuing paid problem solving
> on behalf of an organisation.
> Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
> python-committers mailing list
> python-committers at python.org
> Code of Conduct: https://www.python.org/psf/codeofconduct/
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the python-committers