Installation Problem - error: could not create 'build': File exists

[rorynormaness]

Hello there.

I have made a python 3.7 environment, and then I have also installed Bazel as instructed via Homebrew.

I have then cloned the repository onto the machine - so far so good.

When I then try to install the package with this command:

python3 -m pip install ./trimmed_match

It begins installing dependencies (numpy etc.) just fine, and then when we get to this block, things go south:

Building wheels for collected packages: trimmed-match
  Building wheel for trimmed-match (setup.py) ... error
  error: subprocess-exited-with-error
  
  × python setup.py bdist_wheel did not run successfully.
  │ exit code: 1
  ╰─> [5 lines of output]
      running bdist_wheel
      running build
      running build_py
      creating build
      error: could not create 'build': File exists
      [end of output]
  
  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for trimmed-match
  Running setup.py clean for trimmed-match
Failed to build trimmed-match
Installing collected packages: pytz, typing_extensions, six, pyparsing, pillow, packaging, numpy, MarkupSafe, fonttools, cycler, absl-py, scipy, python-dateutil, kiwisolver, jinja2, pandas, matplotlib, seaborn, trimmed-match
  Running setup.py install for trimmed-match ... error
  error: subprocess-exited-with-error
  
  × Running setup.py install for trimmed-match did not run successfully.
  │ exit code: 1
  ╰─> [7 lines of output]
      running install
      /Users/xx.xx/anaconda3/envs/xx/lib/python3.7/site-packages/setuptools/command/install.py:37: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
        setuptools.SetuptoolsDeprecationWarning,
      running build
      running build_py
      creating build
      error: could not create 'build': File exists
      [end of output]
  
  note: This error originates from a subprocess, and is likely not a problem with pip.
error: legacy-install-failure

× Encountered error while trying to install package.
╰─> trimmed-match

Please help!

[derek-sellar]

Did you ever get an answer to this? I'm having the same issue.

[rorynormaness]

I think it was just not possible to install on mac :( Never managed to solve it *Rory Norman * EMEA Analytics Business Director - DSM & SMB, *Media Futures Group* UK House • 180 Oxford Street • London • W1D 1NN

…

On Wed, Dec 4, 2024 at 3:04 PM Derek ***@***.***> wrote: External: Did you ever get an answer to this? I'm having the same issue. — Reply to this email directly, view it on GitHub <https://urldefense.com/v3/__https://github.com/google/trimmed_match/issues/5*issuecomment-2517690598__;Iw!!MOA0!ZxgpwxCvNrQRMgYUy7vGdYKwIQuE2m4Ehp3zskIJnZrVXtVrza7aZLWKoTN6IeYVyVdCwcng2eLCCKosGajvGXQHLfoXFgA$>, or unsubscribe <https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AMQINPYA6C573BWPQIOWRO32D4KVTAVCNFSM6AAAAABTAMAI3GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJXGY4TANJZHA__;!!MOA0!ZxgpwxCvNrQRMgYUy7vGdYKwIQuE2m4Ehp3zskIJnZrVXtVrza7aZLWKoTN6IeYVyVdCwcng2eLCCKosGajvGXQHufVAOpw$> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- Privileged/Confidential Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such person), you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email. Please advise immediately if you or your employer does not consent to email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of Group M Worldwide LLC and/or other members of the GroupM group of companies shall be understood as neither given nor endorsed by it. GroupM is the global media investment management arm of WPP. For more information on our business ethical standards and Corporate Responsibility policies please refer to WPP's website at http://www.wpp.com/WPP/About/ <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.wpp.com_WPP_About_&d=DwMFaQ&c=N-xPqDyeLJg5V3gLll2thA&r=aMkvY63z6j7EsF4XIb9BQM9Vg_NPq0Tyq_c4qEjSGuI&m=KGmvFRgWqLXTGN-0TqwJrXtnIjxRssANR2E_1vsPHZg&s=CtJil6FZbGrYDvuuovO87MZKGQbQYXhR41-kweAs1C0&e=>

[derek-sellar]

I'm on a windows and can't get it working either tbh.
I think the issue must be with the Bazel install and the estimator_ext file being a C++ file but I've yet to be able to sort it either.

If I figure it out I'll post here. :)

[jth0]

@rorynormaness I encountered the same and was able to determine that it's due to the default macos filesystem being case-insensitive. I don't know anything about bazel, but the way it's configured it needs to create a directory build but it's colliding with the file BUILD.

We previously hit errors along the way where this package wouldn't build correctly with bazel versions beyond 6.1.2. I'm getting this set on a multi-user system / where users don't have root, so we're now using bazelisk to manage bazel versions. Thus, added a file to specify the bazel version automatically and within the user's context/environment. I also hit a compile issue that was due to the use of a feature in C++ introduced in C++ 14, but my system was using C++ 11.

From within your trimmed_match directory,

mv BUILD BUILD.bazel
echo 6.1.2 > .bazelversion

Then edit setup.py to insert '--cxxopt=-std=c++14' as shown here:

bazel_argv = [
        'bazel', 'build', ext.bazel_target + '.so',
        '--symlink_prefix=' + os.path.join(self.build_temp, 'bazel-'),
        '--compilation_mode=' + ('dbg' if self.debug else 'opt'),
        '--cxxopt=-std=c++14'
    ]

I've been using uv for all of this, so you can do this with your local edits described above:

uv init your-project-name --python ">=3.12, <3.13" #we're not using 3.13 for much yet...
cd your-project-name
uv pip install ../trimmed_match

Or clone the repo into your own org, check in your edits, and test them out before merging them into your local repo's main branch:

gh repo fork google/trimmed_match --org "my-org-name" --clone=true
cd trimmed_match
git checkout -b add-macos-support
# make the changes described above
git add BUILD.bazel .bazelversion setup.py
git commit -m "make it mac"
git push
cd ..
uv init your-project-name --python ">=3.12, <3.13" #we're not using 3.13 for much yet...
cd your-project-name
uv add "trimmed_match @ git+https://github.com/my-org-name/trimmed_match -b add-macos-support"

And you should be good to run your stuff importing trimmed_match. If that all works for you like it did for me, you merge that branch and then when you use the uv add command, omit the -b add-macos-support part.