Trepan-Debuggers / Trepan-Debuggers/python3-trepan

Can't install with python-3.13.14

Open
#85 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
176
Forks
17
PR merge metrics
No merged PRs in 30d

Description

Description

I can't install this with pip (26.2 or 26.2.1) and python-3.13.14 (which is the default on openSUSE 16.0 right now).

How to Reproduce

> pip install trepan3k --user
Collecting trepan3k
  Using cached trepan3k-1.5.1.tar.gz (431 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... error
  error: subprocess-exited-with-error

  × Getting requirements to build wheel did not run successfully.
  │ exit code: 1
  ╰─> [20 lines of output]
      Traceback (most recent call last):
        File "/usr/lib/python3.13/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 389, in <module>
          main()
          ~~~~^^
        File "/usr/lib/python3.13/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 373, in main
          json_out["return_val"] = hook(**hook_input["kwargs"])
                                   ~~~~^^^^^^^^^^^^^^^^^^^^^^^^
        File "/usr/lib/python3.13/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 143, in get_requires_for_build_wheel
          return hook(config_settings)
        File "/home/delgado/tmp/pip-build-env-dsc9jv4h/overlay/lib/python3.13/site-packages/setuptools/build_meta.py", line 333, in get_requires_for_build_wheel
          return self._get_build_requires(config_settings, requirements=[])
                 ~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "/home/delgado/tmp/pip-build-env-dsc9jv4h/overlay/lib/python3.13/site-packages/setuptools/build_meta.py", line 301, in _get_build_requires
          self.run_setup()
          ~~~~~~~~~~~~~~^^
        File "/home/delgado/tmp/pip-build-env-dsc9jv4h/overlay/lib/python3.13/site-packages/setuptools/build_meta.py", line 317, in run_setup
          exec(code, locals())  # noqa: S102 # exec is intentional here
          ~~~~^^^^^^^^^^^^^^^^
        File "<string>", line 16, in <module>
      ModuleNotFoundError: No module named 'pkg_resources'
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.

[notice] A new release of pip is available: 26.2 -> 26.2.1
[notice] To update, run: pip install --upgrade pip
ERROR: Failed to build 'trepan3k' when getting requirements to build wheel

(Same error after upgrading pip to 26.2.1)

Expected behavior

I can install it.

Environment

> python3 --version
Python 3.13.14
> which python3
/home/delgado/git/pyenv/shims/python3
> pyenv which python3
/usr/bin/python3
# So yes, pyenv is loaded, but set to use the system python3
# Something weird here?
> pip freeze --user
defusedxml==0.7.1
odfpy==1.4.1
python-dateutil==2.9.0.post0
six==1.17.0
standard-mailcap==3.13.0
visidata @ git+https://github.com/saulpw/visidata.git@bff1aa26f9351eb2d9d745679add2d6efa170915

I'm fuzzy about the state of setuptools in newer pythons. I'm using pkg_resources in my own code as well and have to resort to use an older version of setuptools for that. But that backtrace is confusing me. It looks like it happens in pip but it does not happen with any other package. Is the exec calling funny stuff from setup.py maybe?

Maybe you have an idea what I can try to get more useful information.

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 failure with Python 3.13.14 and the shown pip command, then inspect setup.py and the project’s build metadata for the pkg_resources import path. Confirm the package builds and installs successfully in that environment, while preserving installation for supported Python versions.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
build-system
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.