[Distutils] Comments on PEP 426
ncoghlan at gmail.com
Fri Aug 30 14:50:23 CEST 2013
On 30 August 2013 22:26, Paul Moore <p.f.moore at gmail.com> wrote:
> On 30 August 2013 12:54, Oscar Benjamin <oscar.j.benjamin at gmail.com> wrote:
>> setup.py that would satisfy those commands. It could be as easy as:
>> if sys.argv == 'bdist_wheel':
>> sys.exit(subprocess.call(['bentomaker', 'build_wheel'])
>> or whatever.
> OK, inspiration moment for me. It had never occurred to me that a project
> could do something like that, and now I see it explained, I understand the
> various discussions about standardising command line APIs much better.
If you look at bento's setup.py it's even simpler:
from bento.distutils.monkey_patch import setup
>> I tried deleting the mentioned file but just got the same error
>> message again. Is that a bento/pip/setuptools bug? I notice that the
>> bento docs don't mention pip on the installation page:
> I've never yet got bento working for me. I have assumed that some aspect of
> Windows, Python 3.x, pip or oddities of my setup are not supported yet, and
> have simply left it as "not for prime time yet" (based on the 0.1.1 version
> number) in my mind. So it's always remained as the "obvious example of an
> alternative build system" while still being theoretical.
Could just be a Windows incompatibility - *nix will let another
process open the same file quite happily.
> I'd love to see something concrete though, as these debates tend to get
> remarkably abstract at times :-)
d2to1 is actually my "go to" example of an alternate build system that
people are already using. A setup.py style shim for a setup.cfg based
project. Although d2to1 may just embed the metadata directly in
setup.py - I haven't actually looked into it in detail.
Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
More information about the Distutils-SIG