Re: [Distutils] PEP 517: Bootstrapping setuptools

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 <xov...@gmail.

[Distutils] PEP 517: Bootstrapping setuptools

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

Re: [Distutils] PEP 517: Build frontend responsibilities

rks with appropriate fallbacks to verify setuptools support and compliance, then it's not the end of the world if the packages are still built and installed correctly. 2017-08-19 16:48 GMT-04:00 Paul Moore <p.f.mo...@gmail.com>: > On 19 August 2017 at 21:30, xoviat <xov...@gmail.com>

Re: [Distutils] PEP 517: Build frontend responsibilities

button anyone can press to make it go quickly. > > Thomas > > > > > On Fri, Aug 18, 2017, at 08:17 PM, xoviat wrote: > > At this point, I can only offer implementations as I have been attempting > to do (some of which are outdated because the PEP has changed), but

Re: [Distutils] PEP 517: Build frontend responsibilities

Excuse me, but what I meant to say is that sys.path would be adjusted after the subprocess was loaded (in my implementation I adjust sys.path and os.environ['PYTHONPATH']). 2017-08-19 16:22 GMT-04:00 xoviat <xov...@gmail.com>: > Yes, it probably is. But then again, I assumed that it wa

Re: [Distutils] PEP 517: Build frontend responsibilities

Daniel Holth <dho...@gmail.com>: > It's probably a tiny wrapper running the hook in its own subprocess. > Probably few modules loaded. > > On Sat, Aug 19, 2017, 14:31 xoviat <xov...@gmail.com> wrote: > >> Ah the joy of Python 2.7; it seems I've forgotten its perils: u

Re: [Distutils] PEP 517: Build frontend responsibilities

Ah the joy of Python 2.7; it seems I've forgotten its perils: unloading is not possible which means that we would need to come up with another solution to this problem. Perhaps setting aside a namespace for the build frontend in the subprocess? 2017-08-19 14:23 GMT-04:00 xoviat <xov...@gmail.

Re: [Distutils] PEP 517: Build frontend responsibilities

I assume that the outstanding issues mentioned are related to sys.path in the build tree. My view on that is the following: the build frontend should be responsible using any mechanism that it chooses for invoking the build backend, which must be imported with '' at the front of sys.path. This

Re: [Distutils] PEP 517: Build frontend responsibilities

At this point, I can only offer implementations as I have been attempting to do (some of which are outdated because the PEP has changed), but I cannot make anyone pay attention to or accept my pull requests and it seems I cannot accelerate the discussion here. 2017-08-18 14:08 GMT-05:00 xoviat

Re: [Distutils] PEP 517: Build frontend responsibilities

hub.com/takluyver/flit/tree/toml-config > > > On Fri, Aug 18, 2017, at 06:27 PM, Daniel Holth wrote: > > Apart from the issues, can we get some prototype implementations? > > On Fri, Aug 18, 2017, 13:24 xoviat <xov...@gmail.com> wrote: > > Thomas: > > > What are the sp

Re: [Distutils] PEP 517: Build frontend responsibilities

Thomas: What are the specific issues that need to be worked out? Regards, xoviat 2017-08-18 3:09 GMT-05:00 Thomas Kluyver <tho...@kluyver.me.uk>: > On Fri, Aug 18, 2017, at 07:09 AM, Nick Coghlan wrote: > > The other aspect I'm not clear on is whether or not b

Re: [Distutils] PEP 517: Build frontend responsibilities

I'm still not convinced, but this PEP has been WIP for too long. I think it should be marked Accepted. On Aug 17, 2017 9:51 PM, "Nick Coghlan" wrote: > On 18 August 2017 at 02:05, 12345 67890 wrote: > > After reviewing the PEP, I personally feel that it

Re: [Distutils] status check on PEP 517

Folks, Can we get these issues sorted before pip 10 so that the pip committers will accept my PR addressing the horrible easy_install behavior? Regards, xoviat ___ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman

<    1   2