labnsa.blogg.se

Using it causes the Python interpreter to crash if the DLL was actually used. This is usually not a big issue.ĭon’t use -march=native gcc flag. The Python interpreter will crash on exit if XGBoost was used. But in fact this setup is usable if you know how to deal with it. This presents some difficulties because MSVC uses Microsoft runtime and MinGW-w64 uses own runtime, and the runtimes have different incompatible memory allocators. So you may want to build XGBoost with GCC own your own risk. Running software with telemetry may be against the policy of your organization. Visual Studio contains telemetry, as documented in Microsoft Visual Studio Licensing Terms. Microsoft provides a freeware “Community” edition, but its licensing terms impose restrictions as to where and how it can be used. VS is proprietary and commercial software.

However, you may not be able to use Visual Studio, for following reasons: Usually Python binary modules are built with the same compiler the interpreter is built with. Windows versions of Python are built with Microsoft Visual Studio. If xgboost cannot compile, then it means that you don't have a compatible compiler to build it.Python setup.py install -use-system-libxgboostīuilding Python Package for Windows with MinGW-w64 (Advanced)  Otherwise, you could try this code directly in Rodeo: import pip

After which, it should work fine with Rodeo. You could follow this link to install xgboost in Anaconda. Anaconda has a lot of useful packages pre-installed that don't come along with the pre-installed libraries that the Terminal uses. Since you stated that Rodeo is installed alongside with Anaconda, I'd go with option 2.

However, it is not installed in the package site that Rodeo uses. When you installed xgboost with git, you used the Terminal which is configured to use Python 2.7.10 (probably pre-installed with the OS). Rodeo and Mac Terminal use different versions of Python and obviously different PYTHONPATH with their own set of libraries.