On 16 November 2017 at 15:04, Thomas Kluyver wrote:
> We have now done this, and you can see the new repo here:
>
> https://github.com/pypa/pep517
I've set up a PEP 517 Committers group under the PyPA organisation. At
the moment only Thomas and I are members - if anyone
We have now done this, and you can see the new repo here:
https://github.com/pypa/pep517
On Thu, Nov 16, 2017, at 01:31 PM, Paul Moore wrote:
> I'm happy to (not sure what needs to be done, but I'm sure I can
> muddle it through ;-))
> Paul
>
> On 16 November 2017 at 13:16, Thomas Kluyver
I'm happy to (not sure what needs to be done, but I'm sure I can
muddle it through ;-))
Paul
On 16 November 2017 at 13:16, Thomas Kluyver wrote:
> On Thu, Nov 16, 2017, at 12:46 PM, Nick Coghlan wrote:
>
> On 16 November 2017 at 21:22, Thomas Kluyver
On Thu, Nov 16, 2017, at 12:46 PM, Nick Coghlan wrote:
> On 16 November 2017 at 21:22, Thomas Kluyver
> wrote:>> On Sun, Nov 12, 2017, at 10:51 PM, Nick
> Coghlan wrote:
>> > +1 from me, too.
>>
>> Whose further agreement should we get for this? And - if there is
>>
On 16 November 2017 at 21:22, Thomas Kluyver wrote:
> On Sun, Nov 12, 2017, at 10:51 PM, Nick Coghlan wrote:
> > +1 from me, too.
>
> Whose further agreement should we get for this? And - if there is
> agreement - how do we do the transfer? If someone briefly gives me
>
On Sun, Nov 12, 2017, at 10:51 PM, Nick Coghlan wrote:
> +1 from me, too.
Whose further agreement should we get for this? And - if there is
agreement - how do we do the transfer? If someone briefly gives me
permission to create repos in the PyPA org, I can use Github's transfer
feature.
On 13 November 2017 at 04:59, Thomas Kluyver wrote:
> I have found a bit more time to work on my PEP 517 consumer API:
>
> https://github.com/takluyver/pep517
>
> It provides two main interfaces:
> - 'pep517.wrappers' is a lower-level interface to call the backend hooks
> in
On Sun, Nov 12, 2017, at 07:21 PM, Paul Moore wrote:
> Is it (in your opinion) something that pip might be able to use? The
> biggest potential hurdle, I would imagine, is that if pep517.envbuild
> uses pip to install dependencies, and pip uses pep517.envbuild,
> there's a risk of a recursive loop
On 12 November 2017 at 18:59, Thomas Kluyver wrote:
> I have found a bit more time to work on my PEP 517 consumer API:
>
> https://github.com/takluyver/pep517
>
> It provides two main interfaces:
> - 'pep517.wrappers' is a lower-level interface to call the backend hooks
> in
I have found a bit more time to work on my PEP 517 consumer API:
https://github.com/takluyver/pep517
It provides two main interfaces:
- 'pep517.wrappers' is a lower-level interface to call the backend hooks
in a subprocess.
- 'pep517.envbuild' is a higher-level interface which creates a
10 matches
Mail list logo