On Sun, 30 Sep 2018 at 13:26, Chris Jerdonek <chris.jerdo...@gmail.com> wrote:
> It can be challenging to get stuff like
> this working if the tools you're using make too many directory or
> workflow assumptions. However, a very powerful or flexible tool (e.g.
> Git), or a collection of several tools that each does one thing well,
> can often work well in unanticipated situations. (However, neither of
> those options strikes me as being friendly to beginners, which might
> be the primary thing you're trying to solve -- I'm not sure.)
My attention span is collapsing to nothing right now, so I'll just
comment on this one small point:
The question of one unified tool vs a toolkit of capabilities (whether
mini-tools like Unix commands, or subcommands of a big tool like git)
is an important one. Like you say the toolkit approach is
fundamentally more flexible, but not beginner-friendly.
Personally, I think that the toolkit approach (standards, interop, low
level support) is where distutils-sig and PyPA works best. Higher
level unifications ("one tool to rule them all") have historically
been much less successful. I'm not sure PyPA should be defining best
practices like workflows, or promoting tools tied to particular
workflows. But I'm open to persuasion - if something sufficiently
flexible (i.e., that satisfies *my* needs, on a selfish level ;-))
gains wide community support, then I'm fine with that.
Paul
--
Distutils-SIG mailing list -- distutils-sig@python.org
To unsubscribe send an email to distutils-sig-le...@python.org
https://mail.python.org/mm3/mailman3/lists/distutils-sig.python.org/
Message archived at
https://mail.python.org/mm3/archives/list/distutils-sig@python.org/message/KQQWCWHTNVREUGP4QPF6AZUBFDLLY3BQ/
