On 22 August 2017 at 01:46, Wes Turner wrote:
> ## Justify JSONLD
> - This is a graph. If we use an existing spec for graphs as JSON (ie
> JSONLD), we win:
> - all of the tools that already exist for working with said graphs in that
> format
> - easy indexability (as RDF quads)
> - compatibi
This statement comes from something that Donald said:
> The unvendoring means that setuptools and the project code are now
competing over who gets to define what an acceptable version is for these
libraries to be installed with.
As if this isn't going to be true for any other build system, and
se
On Mon, Aug 21, 2017 at 5:17 PM, xoviat wrote:
> Of course, to be frank, the principle failure with this plan is that
> third-party tools (buildout, os packagers) will not be compliant with PEP
> 517 even after it is adopted, and will then complain about having to update
> their build systems.
>
Of course, to be frank, the principle failure with this plan is that
third-party tools (buildout, os packagers) will not be compliant with PEP
517 even after it is adopted, and will then complain about having to update
their build systems.
2017-08-21 16:05 GMT-05:00 xoviat :
> Previously, the att
Previously, the attempt to move setuptools off of vendored dependencies
failed because it was not done correctly: install_requires was set to the
vendored dependencies but not setup_requires, which would have been
required to correctly specify dependencies. However, setup_requires would
have introd
On Monday, August 21, 2017, Nick Coghlan wrote:
> On 21 August 2017 at 19:38, Paul Moore >
> wrote:
> > On 21 August 2017 at 09:54, Nick Coghlan > wrote:
> >> While I'm still generally negative on the idea of native reliance on
> >> JSON-LD, I'll note one thing that has changed since I last look
On 21 August 2017 at 19:38, Paul Moore wrote:
> On 21 August 2017 at 09:54, Nick Coghlan wrote:
>> While I'm still generally negative on the idea of native reliance on
>> JSON-LD, I'll note one thing that has changed since I last looked at
>> it: I now see some potential concrete practical benefi
New submission from Salvo Tomaselli:
I have a python thing that I'm installing in a custom path, using
setup.py install --root=/tmp/turi13 --install-purelib=custom/path
However, if the setup.py file contains a data_files field, then, unless i also
specify --install-data, the --install-purelib
On 21 August 2017 at 09:54, Nick Coghlan wrote:
> While I'm still generally negative on the idea of native reliance on
> JSON-LD, I'll note one thing that has changed since I last looked at
> it: I now see some potential concrete practical benefits to adopting
> it, rather than purely theoretical
On 21 August 2017 at 02:16, Ian Hartley wrote:
> Ronald,
>
> I was sure that was the case re: python.org installation. It's strange that
> it installed in two different locations, I really have no idea how that
> might have come about. FYI I've included a pic of the file pathways when
> you loo
On 21 August 2017 at 00:51, Wes Turner wrote:
> IIUC, the task is still to:
> Download transitive portions of a [linked data] graph as JSON[LD] (optimally
> without iteratively downloading and decompressing package archives in order
> to retrieve their platform-dependent dependency edge metadata f
11 matches
Mail list logo
