# Is there a duck-typing way to know we can't compile extensions?

Issue #80 resolved
Zooko O'Whielacronx
created an issue

Is there a duck-typing way to know we can't compile extensions?

Yes! You try to build the extension and if it fails then you automatically fall back to using your pure-Python alternative. This way install will also succeed on a system without a C compiler, for example.

The example code that I crib from whenever I'm going to use this hack is simplejson:


Comments (17)

  1. Ned Batchelder repo owner

    I'm experimenting with this code:

        del setup_args['ext_modules']

    It works, but might be a bit over-zealous in catching exceptions. The simplejson code catches BuildFailed, but I find on Windows that when I can't install the extension, it fails with ValueError:

      File "c:\python26\Lib\distutils\msvc9compiler.py", line 458, in compile
      File "c:\python26\Lib\distutils\msvc9compiler.py", line 368, in initialize
        vc_env = query_vcvarsall(VERSION, plat_spec)
      File "c:\python26\Lib\distutils\msvc9compiler.py", line 284, in query_vcvarsall
        raise ValueError(str(list(result.keys())))
    ValueError: [u'path']
  2. Ned Batchelder repo owner

    Domen, thanks for the extra information. I'm afraid I've never used zc.buildout, can you provide very detailed instructions on how to reproduce this? You mention zc.buildout doesn't pass "install" to setup.py, how can that be right? Maybe I don't understand what this is all meant to accomplish. I don't see how the sqlalchemy code gets around not having a verb passed to it.

  3. Ned Batchelder repo owner

    I would accept a pull request, provided I could understand it, and it supported Py2.3 - Py3.3, and worked on Windows, Linux, and Mac. This part of the setup.py doesn't have automated tests, but some guidance on how to make sure it keeps working would be good too.

  4. Log in to comment