distutils build process fails when installing from source directly #21
Conversation
|
Hi, thank you for your contribution. Please confirm this code is submitted under the terms of the OCA (Oracle's Contribution Agreement) you have previously signed by cutting and pasting the following text as a comment: |
|
I confirm the code being submitted is offered under the terms of the OCA, On Thursday, July 7, 2016, mysql-oca-bot notifications@github.com wrote:
|
|
Hi, thank you for your contribution. Your code has been assigned to an internal queue. Please follow |
When installing from source directly without the annoying cpyint submodule that can't be checked out of course:
....
error: option --single-version-externally-managed not recognized
Rolling back uninstall of mysql-connector-python/
....
When installing with this branch, it works fine. Also when building a wheel and then installing the wheel it seems to work fine with master, but was explained below.
I read up on distutils vs setuptools a bit:
http://stackoverflow.com/questions/25337706/setuptools-vs-distutils-why-is-distutils-still-a-thing
Noticed that "Even for projects that do choose to use distutils, when pip installs such projects directly from source (rather than installing from a prebuilt wheel file), it will actually build your project using setuptools instead."
I'm not sure of all the build options as I'm not extremely familiar with distutils, but seems that using them directly is not encouraged in many cases and that setuptools adds more metadata to packages and wraps distutils. I've verified that for my simple python only installation still works and is identical as before, and built with the option --with-mysql-capi= and seemed to build just fine as well.