This is fine as long as developer convenience does not suffer.
Underlying implementations can always be improved, but if we decide on a
sucky format, we'll have to live with that for a long time.
08.05.2016, 08:07, Chris Barker kirjoitti:
On Sat, May 7, 2016 at 6:04 PM, Brett Cannon <br...@python.org
<mailto:br...@python.org>> wrote:
For both options I hear "pick a new format", which suggests we
might as well do it from the get-go for clear separation of the
new stuff and just bite the bullet instead of simply postponing a
decision; it isn't like our format options are going to
significantly change between now and later in the year.
Agreed. However, in another thread, I understood you to say that ALL
we are talking about now is how to specify the build requirements. If
that's the case, then we might a well as well just go with setup.cfg.
However, I'd rather we were setting the stage for grater things -- in
which case, let's go with a new config file.
BTW, IIRC, there seemed to a consensus moving toward using a Python
API, rather than a command line API for the mythical pluggable build
systems....
In which case, we can require python, and could use python literals
for configuration. With the discussion of PyYaml, I"m thinking more
and more that something that can be parsed with only the stdlib is a
good idea.
-CHB
--
Christopher Barker, Ph.D.
Oceanographer
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
chris.bar...@noaa.gov <mailto:chris.bar...@noaa.gov>
_______________________________________________
Distutils-SIG maillist - Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig
_______________________________________________
Distutils-SIG maillist - Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig
