Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Following the SDK Dev Guide to create a target leads to a poetry version solving failure #1344

Closed
BraedonLeonard opened this issue Jan 24, 2023 · 3 comments
Labels

Comments

@BraedonLeonard
Copy link

Singer SDK Version

0.18.0

Python Version

3.9

Bug scope

Other

Operating System

Linux Mint

Description

By following the Meltano SDK Dev Guide (https://sdk.meltano.com/en/latest/), I ran into an issue where the generated python project for my target would not let me poetry install due to a version solving error. I started by running the following:

# Install pipx if you haven't already
pip3 install pipx
pipx ensurepath
# Restart your terminal here, if needed, to get the updated PATH
pipx install cookiecutter
pipx install poetry

I then generated a target using the following:

cookiecutter https://github.com/meltano/sdk --directory="cookiecutter/target-template"

Finally, I followed the generated README's instructions to use poetry install:

poetry install

Which gave me the following error:

Updating dependencies
Resolving dependencies... (2.7s)

Because no versions of tox match >4.1.3,<4.2.0 || >4.2.0,<4.2.1 || >4.2.1,<4.2.2 || >4.2.2,<4.2.3 || >4.2.3,<4.2.4 || >4.2.4,<4.2.5 || >4.2.5,<4.2.6 || >4.2.6,<4.2.7 || >4.2.7,<4.2.8 || >4.2.8,<4.3.0 || >4.3.0,<4.3.1 || >4.3.1,<4.3.2 || >4.3.2,<4.3.3 || >4.3.3,<4.3.4 || >4.3.4,<4.3.5 || >4.3.5,<5.0.0
 and tox (4.1.3) depends on importlib-metadata (>=5.2), tox (>=4.1.3,<4.2.0 || >4.2.0,<4.2.1 || >4.2.1,<4.2.2 || >4.2.2,<4.2.3 || >4.2.3,<4.2.4 || >4.2.4,<4.2.5 || >4.2.5,<4.2.6 || >4.2.6,<4.2.7 || >4.2.7,<4.2.8 || >4.2.8,<4.3.0 || >4.3.0,<4.3.1 || >4.3.1,<4.3.2 || >4.3.2,<4.3.3 || >4.3.3,<4.3.4 || >4.3.4,<4.3.5 || >4.3.5,<5.0.0) requires importlib-metadata (>=5.2).
And because tox (4.2.0) depends on importlib-metadata (>=5.2), tox (>=4.1.3,<4.2.1 || >4.2.1,<4.2.2 || >4.2.2,<4.2.3 || >4.2.3,<4.2.4 || >4.2.4,<4.2.5 || >4.2.5,<4.2.6 || >4.2.6,<4.2.7 || >4.2.7,<4.2.8 || >4.2.8,<4.3.0 || >4.3.0,<4.3.1 || >4.3.1,<4.3.2 || >4.3.2,<4.3.3 || >4.3.3,<4.3.4 || >4.3.4,<4.3.5 || >4.3.5,<5.0.0) requires importlib-metadata (>=5.2).
And because tox (4.2.1) depends on importlib-metadata (>=5.2)
 and tox (4.2.2) depends on importlib-metadata (>=5.2), tox (>=4.1.3,<4.2.3 || >4.2.3,<4.2.4 || >4.2.4,<4.2.5 || >4.2.5,<4.2.6 || >4.2.6,<4.2.7 || >4.2.7,<4.2.8 || >4.2.8,<4.3.0 || >4.3.0,<4.3.1 || >4.3.1,<4.3.2 || >4.3.2,<4.3.3 || >4.3.3,<4.3.4 || >4.3.4,<4.3.5 || >4.3.5,<5.0.0) requires importlib-metadata (>=5.2).
And because tox (4.2.3) depends on importlib-metadata (>=5.2)
 and tox (4.2.4) depends on importlib-metadata (>=5.2), tox (>=4.1.3,<4.2.5 || >4.2.5,<4.2.6 || >4.2.6,<4.2.7 || >4.2.7,<4.2.8 || >4.2.8,<4.3.0 || >4.3.0,<4.3.1 || >4.3.1,<4.3.2 || >4.3.2,<4.3.3 || >4.3.3,<4.3.4 || >4.3.4,<4.3.5 || >4.3.5,<5.0.0) requires importlib-metadata (>=5.2).
And because tox (4.2.5) depends on importlib-metadata (>=5.2)
 and tox (4.2.6) depends on importlib-metadata (>=5.2), tox (>=4.1.3,<4.2.7 || >4.2.7,<4.2.8 || >4.2.8,<4.3.0 || >4.3.0,<4.3.1 || >4.3.1,<4.3.2 || >4.3.2,<4.3.3 || >4.3.3,<4.3.4 || >4.3.4,<4.3.5 || >4.3.5,<5.0.0) requires importlib-metadata (>=5.2).
And because tox (4.2.7) depends on importlib-metadata (>=6)
 and tox (4.2.8) depends on importlib-metadata (>=6), tox (>=4.1.3,<4.3.0 || >4.3.0,<4.3.1 || >4.3.1,<4.3.2 || >4.3.2,<4.3.3 || >4.3.3,<4.3.4 || >4.3.4,<4.3.5 || >4.3.5,<5.0.0) requires importlib-metadata (>=5.2).
And because tox (4.3.0) depends on importlib-metadata (>=6)
 and tox (4.3.1) depends on importlib-metadata (>=6), tox (>=4.1.3,<4.3.2 || >4.3.2,<4.3.3 || >4.3.3,<4.3.4 || >4.3.4,<4.3.5 || >4.3.5,<5.0.0) requires importlib-metadata (>=5.2).
And because tox (4.3.2) depends on importlib-metadata (>=6)
 and tox (4.3.3) depends on importlib-metadata (>=6), tox (>=4.1.3,<4.3.4 || >4.3.4,<4.3.5 || >4.3.5,<5.0.0) requires importlib-metadata (>=5.2).
And because tox (4.3.4) depends on importlib-metadata (>=6)
 and tox (4.3.5) depends on importlib-metadata (>=6), tox (>=4.1.3,<5.0.0) requires importlib-metadata (>=5.2).
Because no versions of singer-sdk match >0.18.0,<0.19.0
 and singer-sdk (0.18.0) depends on importlib-metadata (<5.0.0), singer-sdk (>=0.18.0,<0.19.0) requires importlib-metadata (<5.0.0).
Thus, singer-sdk (>=0.18.0,<0.19.0) is incompatible with tox (>=4.1.3,<5.0.0).
So, because target-kxi-sp depends on both singer-sdk (^0.18.0) and tox (^4.1.3), version solving failed.

Code

No response

@BraedonLeonard BraedonLeonard added kind/Bug Something isn't working valuestream/SDK labels Jan 24, 2023
@WillDaSilva WillDaSilva self-assigned this Jan 24, 2023
@edgarrmondragon
Copy link
Collaborator

Duplicate of #1311

@edgarrmondragon edgarrmondragon marked this as a duplicate of #1311 Jan 24, 2023
@WillDaSilva WillDaSilva removed their assignment Jan 24, 2023
@stale
Copy link

stale bot commented Jul 18, 2023

This has been marked as stale because it is unassigned, and has not had recent activity. It will be closed after 21 days if no further activity occurs. If this should never go stale, please add the evergreen label, or request that it be added.

@stale stale bot added the stale label Jul 18, 2023
@edgarrmondragon
Copy link
Collaborator

Duplicate of #1311

@edgarrmondragon edgarrmondragon closed this as not planned Won't fix, can't repro, duplicate, stale Jul 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants