Skip to content

bug: Running 'make setup' fails dependency resolution #706

@connesy

Description

@connesy

Description of the bug

Running make setup locally in a fork of the repo fails dependency resolution.

To Reproduce

# Fork and clone the repository
cd mkdostrings
make setup

Full traceback

Full traceback
$ make setup
Installing dependencies (default environment)
  × No solution found when resolving dependencies:
  ╰─▶ Because only the following versions of mkdocstrings-python-legacy are available:
          mkdocstrings-python-legacy<=0.2.1
          mkdocstrings-python-legacy==0.2.2
          mkdocstrings-python-legacy==0.2.3
          mkdocstrings-python-legacy==0.2.4
      and mkdocstrings-python-legacy>=0.2.1,<=0.2.2 depends on your project, we can conclude that mkdocstrings-python-legacy>=0.2.1,<0.2.3 depends on your project.
      And because mkdocstrings-python-legacy>=0.2.3 depends on your project, we can conclude that mkdocstrings-python-legacy>=0.2.1 depends on your project.
      And because mkdocstrings[python-legacy] depends on mkdocstrings-python-legacy>=0.2.1 and your project requires mkdocstrings[python-legacy], we can conclude that your projects's requirements are unsatisfiable.

      hint: The package `mkdocstrings-python-legacy` depends on the package `mkdocstrings` but the name is shadowed by your project. Consider changing the name of the project.
make: *** [Makefile:28: setup] Error 1

Expected behavior

Environment information

$ python -V
Python 3.12.3
$ uv -V
uv 0.4.29

Metadata

Metadata

Assignees

Labels

unconfirmedThis bug was not reproduced yet

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions