{"push_id":755660245,"size":2,"distinct_size":2,"ref":"refs/heads/swig-setup","head":"9e5962a83032cf3ad5f7c5cc93d77a1acd2a6e24","before":"9b3c59adc71e0f5ebf9a681f114fee351b027b2f","commits":[{"sha":"4dc84de7a204f06e0151963919d9731faf76c138","author":{"email":"10ae63b69ae5ab71b07f9e64004a0207f53fea34@vermaat.name","name":"Martijn Vermaat"},"message":"Fix setup.py to always run SWIG before copying generated files\n\nWe had some weird issues where running `python setup.py install` did not\ncorrectly install the SWIG generated file. Apparently some steps where\nnot done in the correct order.\n\nInstalling with `python setup.py develop`, or `pip install .`, or with\npip directly from PyPI would work fined, as would running the regular\n`python setup.py install` twice.\n\nA similar issue was filed for WND-CHARM [1] and on Python distutils [2].\nWe implement the workaround provided in [3].\n\n[1] https://github.com/wnd-charm/wnd-charm/issues/3\n[2] http://bugs.python.org/issue7562\n[3] http://stackoverflow.com/questions/12491328/python-distutils-not-include-the-swig-generated-module","distinct":true,"url":"https://api.github.com/repos/mutalyzer/description-extractor/commits/4dc84de7a204f06e0151963919d9731faf76c138"},{"sha":"9e5962a83032cf3ad5f7c5cc93d77a1acd2a6e24","author":{"email":"10ae63b69ae5ab71b07f9e64004a0207f53fea34@vermaat.name","name":"Martijn Vermaat"},"message":"Use regular python setup.py install on Travis CI\n\nUse `python setup.py install` instead of `pip install .` on Travis CI\nso that it will catch the SWIG setup error we fixed in [1].\n\n[1] https://github.com/mutalyzer/description-extractor/commit/3cb4333bcf02776f855569907ec381acc1907abc","distinct":true,"url":"https://api.github.com/repos/mutalyzer/description-extractor/commits/9e5962a83032cf3ad5f7c5cc93d77a1acd2a6e24"}]}