<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Thu, Oct 22, 2015 at 8:47 AM, Thomas Güttler <span dir="ltr"><<a href="mailto:guettliml@thomas-guettler.de" target="_blank">guettliml@thomas-guettler.de</a>></span> wrote:<br><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">> I have a dream: For packaging and building package provides only **data**. Data is condition-less: No single "if", "def" or method call. Just data: json or yaml ...<br>
><br>
> Even for complex packages.<br></span></blockquote><div><br></div><div>It's a nice dream -- but I think there is more or less a consensus on this list that you really can't do everything completely declaratively. I know I would find it very frustrating to have to hard-code everything up front.</div><div><br></div><div>But we do have a bad situtation now where you can't know the metadata until you've run setup.py -- not good.</div><div><br></div><div>Maybe we need to add a configure step:</div><div><br></div><div>a configure_package.py that would return the full set of metadata -- or maybe a dict that could be passed right on to:</div><div><br></div><div> setup(**configuration)</div><div><br></div><div>In the simple cases, this would simply return a static dict, but it would be a hook where people could do whatever they need.</div><div><br></div><div>Perhaps sdists would have had the configure step already run -- not sure about that one off the bat, but it would be kind of like distributing a source tarball with autotools already run.</div><div><br></div><div>I think this may be a bit where the sdist conversation was going (at least on one side-track...): you might have sdists that are customized to the platform:</div><div><br></div><div>"this sdist is for numpy running on Windows with OpenBLAS"</div><div><br></div><div>that sort of thing.</div><div><br></div><div>I THINK, once you'd broken it down to that level, you could have static configuration.</div><div><br></div><div>-Chris</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
> This data gets processed by setuptools. I don't see a need for more than one library doing this. Plugins are nice and can solve edge cases.<br>
><br>
><br>
</span>> setuptools is one bloated piece of code that contains too much features. I'd prefer more lean and mean package.<br>
<br>
Yes, your are rigth. I'd like a lean and mean package, too.<br>
<div class="HOEnZb"><div class="h5"><br>
Regards,<br>
Thomas Güttler<br>
<br>
<br>
<br>
--<br>
<a href="http://www.thomas-guettler.de/" rel="noreferrer" target="_blank">http://www.thomas-guettler.de/</a><br>
_______________________________________________<br>
Distutils-SIG maillist - <a href="mailto:Distutils-SIG@python.org">Distutils-SIG@python.org</a><br>
<a href="https://mail.python.org/mailman/listinfo/distutils-sig" rel="noreferrer" target="_blank">https://mail.python.org/mailman/listinfo/distutils-sig</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><br>Christopher Barker, Ph.D.<br>Oceanographer<br><br>Emergency Response Division<br>NOAA/NOS/OR&R (206) 526-6959 voice<br>7600 Sand Point Way NE (206) 526-6329 fax<br>Seattle, WA 98115 (206) 526-6317 main reception<br><br><a href="mailto:Chris.Barker@noaa.gov" target="_blank">Chris.Barker@noaa.gov</a></div>
</div></div>