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 temporary environment, uses pip to install build dependencies, and builds a wheel or an sdist. I hope that some frontend tools will be able to use these interfaces directly, but I also intend it as a reference consumer which backend authors can use to test their implementation. As such, I'd like to propose moving the project into the control of the Python Packagaing Authority - i.e. transferring the Github repo and giving other people upload rights on PyPI. In other news, Flit 0.12 is out, providing a PEP 517 backend. Though come to think of it, I may have forgotten to use the tar pax format. Thomas
On 12 November 2017 at 18:59, Thomas Kluyver <thomas@kluyver.me.uk> 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 a subprocess. - 'pep517.envbuild' is a higher-level interface which creates a temporary environment, uses pip to install build dependencies, and builds a wheel or an sdist.
Nice :-)
I hope that some frontend tools will be able to use these interfaces directly,
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 that could result in starting an arbitrarily large number of processes on the user's machine (this is one of the issues that has stalled the current work on PEP 517 for pip). On the other hand, other frontends depending on pip (indirectly, via pep517.envbuild) might seem a bit odd.
but I also intend it as a reference consumer which backend authors can use to test their implementation. As such, I'd like to propose moving the project into the control of the Python Packagaing Authority - i.e. transferring the Github repo and giving other people upload rights on PyPI.
+1 to that suggestion. Paul
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 that could result in starting an arbitrarily large number of processes on the user's machine (this is one of the issues that has stalled the current work on PEP 517 for pip). On the other hand, other frontends depending on pip (indirectly, via pep517.envbuild) might seem a bit odd.
I would guess that pip could use the lower-level interface directly, but it might want to control how dependencies are found and installed. The higher level part is based on code already in pip (pip._internal.wheel.BuildEnvironment), so hopefully integrating it shouldn't be too much work. I've also just added another module to test the hooks for a project and point out any problems. It's used like this: python3 -m pep517.check path/to/source Thomas
On 13 November 2017 at 04:59, Thomas Kluyver <thomas@kluyver.me.uk> 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 a subprocess. - 'pep517.envbuild' is a higher-level interface which creates a temporary environment, uses pip to install build dependencies, and builds a wheel or an sdist.
I hope that some frontend tools will be able to use these interfaces directly, but I also intend it as a reference consumer which backend authors can use to test their implementation. As such, I'd like to propose moving the project into the control of the Python Packagaing Authority - i.e. transferring the Github repo and giving other people upload rights on PyPI.
+1 from me, too.
In other news, Flit 0.12 is out, providing a PEP 517 backend
Cool! Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
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. Otherwise, we can do it manually by creating a new repo and removing the old one. Thanks, Thomas
On 16 November 2017 at 21:22, Thomas Kluyver <thomas@kluyver.me.uk> 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 permission to create repos in the PyPA org, I can use Github's transfer feature. Otherwise, we can do it manually by creating a new repo and removing the old one.
Paul and Donald can accept transfer requests. Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
On Thu, Nov 16, 2017, at 12:46 PM, Nick Coghlan wrote:
On 16 November 2017 at 21:22, Thomas Kluyver <thomas@kluyver.me.uk> 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 permission to create repos in the PyPA org, I can use Github's transfer>> feature. Otherwise, we can do it manually by creating a new repo and>> removing the old one.
Paul and Donald can accept transfer requests.
It appears that you can't make transfer requests to an organisation. Paul, Donald, if you're happy to accept it I could make a transfer request to one of your individual accounts, and you'd then transfer it again to pypa. Or maybe I've missed something about how to do it. Thomas
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 <thomas@kluyver.me.uk> wrote:
On Thu, Nov 16, 2017, at 12:46 PM, Nick Coghlan wrote:
On 16 November 2017 at 21:22, Thomas Kluyver <thomas@kluyver.me.uk> 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 permission to create repos in the PyPA org, I can use Github's transfer feature. Otherwise, we can do it manually by creating a new repo and removing the old one.
Paul and Donald can accept transfer requests.
It appears that you can't make transfer requests to an organisation. Paul, Donald, if you're happy to accept it I could make a transfer request to one of your individual accounts, and you'd then transfer it again to pypa. Or maybe I've missed something about how to do it.
Thomas
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
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 <thomas@kluyver.me.uk> wrote:
On Thu, Nov 16, 2017, at 12:46 PM, Nick Coghlan wrote:
On 16 November 2017 at 21:22, Thomas Kluyver <thomas@kluyver.me.uk> 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 permission to create repos in the PyPA org, I can use Github's transfer feature. Otherwise, we can do it manually by creating a new repo and removing the old one.
Paul and Donald can accept transfer requests.
It appears that you can't make transfer requests to an organisation. Paul, Donald, if you're happy to accept it I could make a transfer request to one of your individual accounts, and you'd then transfer it again to pypa. Or maybe I've missed something about how to do it.
Thomas
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
On 16 November 2017 at 15:04, Thomas Kluyver <thomas@kluyver.me.uk> wrote:
We have now done this, and you can see the new repo here:
I've set up a PEP 517 Committers group under the PyPA organisation. At the moment only Thomas and I are members - if anyone else wants to be added, just let me know. Paul
participants (3)
-
Nick Coghlan -
Paul Moore -
Thomas Kluyver