Do not fail on unsupported manifests

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

Nobody has claimed this yet.

Assessment

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

Research direction

Start at the API entry point that performs dynamic dependency resolution and reproduce the reported case with an unsupported setup.cfg or pyproject.toml manifest. Trace how unsupported manifests are handled; done means the API no longer fails when given these manifests or other manifests that are unsupported for dynamic dependency resolution.

Written by the indexing model from the issue text.

Description

We should not fail like this: https://github.com/nexB/scancode.io/issues/1313 when we get an unsupported manifest like a setup.cfg or a pyproject.toml or other which are not supported for dynamic dependency resolution, while calling from the API.

Dominant language
Python
Stars
23
Forks
29
Avg merge
1h 7m
Merged PRs (30d)
2

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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/python-inspector

All issues in aboutcode-org/python-inspector

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.