<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
pip doesn't yet support pyproject.toml does it?<br>
<br>
<div class="moz-cite-prefix">23.07.2016, 17:43, Daniel Holth
kirjoitti:<br>
</div>
<blockquote
cite="mid:CAG8k2+7vp949LSXpLBGzEytG59KatpM1-0uonKQhKYeyAOytug@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>Here is my attempt. The SConstruct (like a Makefile) builds
the extension. The .toml file gives the static metadata. No
need to put the two in the same file.</div>
<div><br>
</div>
<a moz-do-not-send="true"
href="https://bitbucket.org/dholth/cryptacular/src/tip/SConstruct">https://bitbucket.org/dholth/cryptacular/src/tip/SConstruct</a><br>
<div><br>
</div>
<div><a moz-do-not-send="true"
href="https://bitbucket.org/dholth/cryptacular/src/tip/pyproject.toml">https://bitbucket.org/dholth/cryptacular/src/tip/pyproject.toml</a><br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr">On Sat, Jul 23, 2016 at 10:11 AM Alex Grönholm
<<a moz-do-not-send="true"
href="mailto:alex.gronholm@nextday.fi">alex.gronholm@nextday.fi</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">23.07.2016,
17:04, Thomas Kluyver kirjoitti:<br>
> On Sat, Jul 23, 2016, at 02:32 PM, Alex Grönholm wrote:<br>
>> I'm -1 on this because requirements.txt is not really
the standard way<br>
>> to list dependencies.<br>
>> In the Python world, setup.py is the equivalent of
Node's package.json.<br>
>> But as it is<br>
>> Python code, it cannot so easily be programmatically
modified.<br>
> Packaging based on declarative metadata:<br>
> <a moz-do-not-send="true"
href="http://flit.readthedocs.io/en/latest/"
rel="noreferrer" target="_blank">http://flit.readthedocs.io/en/latest/</a><br>
> </blowing_own_trumpet><br>
><br>
> We have a bit of a divide. Specifying dependencies in
setup.py (or<br>
> flit.ini, or upcoming pyproject.toml) is the standard for
library and<br>
> tool packages that are intended to be published on PyPI
and installed<br>
> with pip. requirements.txt is generally used for
applications which will<br>
> be distributed or deployed by other means.<br>
><br>
> As I understand it, in the Javascript world package.json
is used in both<br>
> cases. Is that something Python should try to emulate? Is
it hard to<br>
> achieve given the limitations of setup.py that you
pointed out?<br>
This topic has been beaten to death. There is no way to cram
the<br>
complexities of C extension compilation setup into purely
declarative<br>
metadata. Distutils2 tried and failed. Just look at the
setup.py files<br>
of some popular projects and imagine all that logic expressed
in<br>
declarative metadata.<br>
> Thomas<br>
> _______________________________________________<br>
> Distutils-SIG maillist - <a moz-do-not-send="true"
href="mailto:Distutils-SIG@python.org" target="_blank">Distutils-SIG@python.org</a><br>
> <a moz-do-not-send="true"
href="https://mail.python.org/mailman/listinfo/distutils-sig"
rel="noreferrer" target="_blank">https://mail.python.org/mailman/listinfo/distutils-sig</a><br>
<br>
_______________________________________________<br>
Distutils-SIG maillist - <a moz-do-not-send="true"
href="mailto:Distutils-SIG@python.org" target="_blank">Distutils-SIG@python.org</a><br>
<a moz-do-not-send="true"
href="https://mail.python.org/mailman/listinfo/distutils-sig"
rel="noreferrer" target="_blank">https://mail.python.org/mailman/listinfo/distutils-sig</a><br>
</blockquote>
</div>
</blockquote>
<br>
</body>
</html>