Any way to customize the lc0 build parameters?

Any way to customize the lc0 build parameters?

I haven't tested it yet, but according to the docs, this could be achieved via pip install . --config-settings setup-args="option=value".

An example of how this PR can be useful for other Python packages (that can depend on the package lczero-bindings, even if it's not on PyPi (yet?)) can be found here.

Putting lczero-bindings @ git+https://github.com/LeelaChessZero/lc0.git in a requirements file or equivalent would do the trick. I hope this goes into master, so that I don't have to depend on my fork each time :).

@ddobbelaere which prerequisites does one need for this to work? Because I get this when running pip install --user git+https://github.com/LeelaChessZero/lc0.git.

backends.cc:643:1: warning: missing initializer for member ‘_typeobject::tp_                                                                                                                                                                                                cache’ [-Wmissing-field-initializers]
backends.cc:643:1: warning: missing initializer for member ‘_typeobject::tp_                                                                                                                                                                                                subclasses’ [-Wmissing-field-initializers]
backends.cc:643:1: warning: missing initializer for member ‘_typeobject::tp_                                                                                                                                                                                                weaklist’ [-Wmissing-field-initializers]
backends.cc:643:1: warning: missing initializer for member ‘_typeobject::tp_                                                                                                                                                                                                del’ [-Wmissing-field-initializers]
backends.cc:643:1: warning: missing initializer for member ‘_typeobject::tp_                                                                                                                                                                                                version_tag’ [-Wmissing-field-initializers]
backends.cc:643:1: warning: missing initializer for member ‘_typeobject::tp_                                                                                                                                                                                                finalize’ [-Wmissing-field-initializers]
backends.cc:643:1: warning: missing initializer for member ‘_typeobject::tp_                                                                                                                                                                                                vectorcall’ [-Wmissing-field-initializers]
[164/231] Linking target encoder_test
ninja: build stopped: subcommand failed.
----------------------------------------

WARNING: Discarding git+https://github.com/LeelaChessZero/lc0.git. Command error ed out with exit status 1: /usr/local/bin/python3.9 /usr/local/lib/python3.9/sit e-packages/pip/_vendor/pep517/in_process/_in_process.py prepare_metadata_for_bui ld_wheel /tmp/tmp4iilmeq8 Check the logs for full command output.

ERROR: Command errored out with exit status 1: /usr/local/bin/python3.9 /usr/loc al/lib/python3.9/site-packages/pip/_vendor/pep517/in_process/_in_process.py prep are_metadata_for_build_wheel /tmp/tmp4iilmeq8 Check the logs for full command ou tput.

@hwuebben You should have a recent C++ compiler installed to build lc0 from sources. It might be a good idea to verify if that works first. Apart from that, looking at the full logs as indicated by pip is another way to proceed.

Hi guys. I have a trouble building python bindings using the following command:
pip install --user .
It fails on metadata generation step producing a huge amount of C++ warnings (I guess) and the end of the output is the following:

Can you please assist with it?

To my previous comment. I think I found the root cause of this:

The issue is with the C++ 14 standard is not supporting constructions used in the source code. I change it using Visual Studio (in backend project properties) but it doesn't make any difference, there is the same error.

What should I change to make it work?

I'm having some trouble understanding how this works. I followed the instructions to the best of my knowledge.
(on Mac, Ventura)
When running "pip install --user ." , it just throws an error of invalid syntax.
I tried "pip install --user git+https://github.com/LeelaChessZero/lc0.git", and it seemed to download, but I already had the files?

When I run "pip show lczero-bindings", I get the same output you did, with the long GNU license.
However, trying to run "import lczero.backends" in python just leads to "ModuleNotFoundError: No module named 'lczero'".
Is there something I am missing?

@LilacPeregrine I don't really know (not a Mac user either). Here are some suggestions:

• Does it work in a virtual environment?

python -m venv venv
source venv/bin/activate
python -m pip install git+https://github.com/LeelaChessZero/lc0.git
python -c "import lczero.backends" # Should work
deactivate

• Is your user installation folder of pip added to the search path of python?

Good luck. Maybe the lc0 Discord is also a better place to discuss these things further.

@ddobbelaere
You appear to be correct. I have an issue with multiple python versions due to mac setup (at least initially). When installing lc0, it also appears to have somehow changed the python path for the terminal?

However, it works now, if I run it through python3.11 "name of file.py"
Thank you!

I'm experiencing the same issue as @ukrainec45