Which python version is the tool best compatible with?

Open
#5 2 comments 1 reaction 0 assignees View on GitHub

A pull request for this has already been merged.

  • #6 by @pombredanne — merged

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python, ubuntu

Research direction

Start by reproducing the reported failures on Ubuntu 18 with the Python versions listed, using ./configure --dev and tracecode -h. Inspect the setup path and dependency handling, including the missing pip, importlib.resources, and apt_pkg modules. Done means the supported Python version and a clean installation path are established and documented.

Written by the indexing model from the issue text.

Description

bug

Hi,

I'm testing the tool on Ubuntu 18.
With python 3.6 I had the following issue from ./configure --dev:

ModuleNotFoundError: No module named 'importlib.resources'

I updated to 3.10 and ./configure --dev worked well.

Then I tried to pip3 install apt_pkg as tracecode -h was failing with ModuleNotFoundError: No module named 'apt_pkg' and got the following:

AttributeError: module 'collections' has no attribute 'MutableMapping'

which is a result of updating collections.MutableMapping to collections.abc.MutableMapping in 3.10.

Then I downgraded to 3.9 and couldn't run again ./configure --dev, as for

ModuleNotFoundError: No module named 'pip'

which I'm not sure how to fix in tracecode's setup.

pip3 install apt_pkg failed for all 3.9, 3.8 and 3.7 with:

Could not find a version that satisfies the requirement apt_pkg (from versions: )
No matching distribution found for apt_pkg

How can I clean up the whole installation and start from scratch and which python version should I use?

Thanks :)

Dominant language
Python
Stars
25
Forks
8
PR merge metrics
No merged PRs in 30d

Getting set up

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.

More from aboutcode-org/tracecode-toolkit-strace

All issues in aboutcode-org/tracecode-toolkit-strace

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.