New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pants.ini required even with --config-override #2652
Comments
Yeah - it should be named For example (I use pyenv to isolate python installed tools, but thats not really a relevant detail here):
NB: You would either need to run the command once on a machine of each platform you distribute to, or else you would need to have a repository of pre-built eggs or wheels for platform-specific libs pants uses, like pycov and psutil and use pex's |
To get the behaviour you want, you can set |
I was trying to follow https://pantsbuild.github.io/howto_develop.html to create a pex build of pants for my CI server (I don't have any custom pants extensions at the moment so maybe there should have been an easier way to do this). I found it surprising that
pants.ini
was requred even though I was explicitly instructing pants to use a different ini file.From a new directory:
After creating an empty
pants.ini
and theBUILD.tools
scale magic it worked.The text was updated successfully, but these errors were encountered: