microsoft / microsoft/Graphormer

python setup.py build_ext --inplace bug

Open
#166 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
2.5k
Forks
374
PR merge metrics
No merged PRs in 30d

Description

python setup.py build_ext --inplace
fatal: not a git repository (or any of the parent directories): .git
/home/xxx/.conda/envs/graphormer/lib/python3.9/site-packages/setuptools/init.py:84: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated.
!!

    ********************************************************************************
    Requirements should be satisfied by a PEP 517 installer.
    If you are using pip, you can try `pip install --use-pep517`.
    ********************************************************************************

!!
dist.fetch_build_eggs(dist.setup_requires)
running build_ext
/home/xxx/.conda/envs/graphormer/lib/python3.9/site-packages/torch/utils/cpp_extension.py:370: UserWarning: Attempted to use ninja as the BuildExtension backend but we could not find ninja.. Falling back to using the slow distutils backend.
warnings.warn(msg.format('we could not find ninja.'))
skipping 'fairseq/data/data_utils_fast.cpp' Cython extension (up-to-date)
skipping 'fairseq/data/token_block_utils_fast.cpp' Cython extension (up-to-date)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the reported python setup.py build_ext --inplace command from the repository and inspect setup.py, along with the mentioned fairseq/data/data_utils_fast.cpp and fairseq/data/token_block_utils_fast.cpp extensions. Check whether the command actually fails after the warnings and skipped extensions; the issue needs a defined successful build result before completion can be verified.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, pytorch
Domain
build-system
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.