I’m working on tap-postgres and when I bump the SDK up to 0.10.0 or above, poetry doesnt seem able to resolve dependencies. It isnt throwing an error but I just ran poetry lock overnight and it’s still chugging along …`Resolving dependencies... (35778.5s)` 😅. Anyone run into this with other SDK-based taps or have any ideas or tips for helping poetry get it done?

Not sure about tap-postgres here as I haven't seen it with tap-postgres, but if I've seen this I just rm -rf the venv and rerun poetry install.

With

sdk = "^0.18.0"

in the pyproject.toml? I only noticed this problem when I tried to make poetry use sdk versions above 0.10.0

yes

visch@DESKTOP-9BDPA9T:~/git/tap-postgres$ poetry update
Updating dependencies
Resolving dependencies... (8.6s)

Writing lock file

Package operations: 6 installs, 22 updates, 2 removals

  • Removing ciso8601 (2.2.0)
  • Removing pipelinewise-singer-python (1.2.0)
  • Installing zipp (3.11.0)
  • Installing appdirs (1.4.4)
  • Updating attrs (22.1.0 -> 22.2.0)
  • Updating charset-normalizer (2.1.1 -> 3.0.1)
  • Updating filelock (3.8.2 -> 3.9.0)
  • Installing importlib-resources (5.10.2)
  • Installing pkgutil-resolve-name (1.3.10)
  • Updating platformdirs (2.6.0 -> 2.6.2)
  • Updating pyrsistent (0.19.2 -> 0.19.3)
  • Updating setuptools (65.6.3 -> 66.1.1)
  • Updating urllib3 (1.26.13 -> 1.26.14)
  • Updating backoff (1.8.0 -> 2.2.1)
  • Updating cryptography (37.0.4 -> 39.0.0)
  • Installing fs (2.4.16)
  • Updating iniconfig (1.1.1 -> 2.0.0)
  • Updating jsonschema (3.2.0 -> 4.17.3)
  • Updating packaging (22.0 -> 23.0)
  • Updating pathspec (0.10.3 -> 0.11.0)
  • Updating python-dotenv (0.20.0 -> 0.21.1)
  • Updating pytz (2020.5 -> 2022.7.1)
  • Installing pyyaml (6.0)
  • Updating requests (2.28.1 -> 2.28.2)
  • Updating simplejson (3.11.1 -> 3.18.1)
  • Updating sqlalchemy (1.4.45 -> 1.4.46)
  • Updating isort (5.11.1 -> 5.11.4)
  • Updating pydocstyle (6.1.1 -> 6.3.0)
  • Updating singer-sdk (0.7.0 -> 0.18.0)
  • Updating types-requests (2.28.11.5 -> 2.28.11.8)
visch@DESKTOP-9BDPA9T:~/git/tap-postgres$ poetry install
Installing dependencies from lock file

No dependencies to install or update

Installing the current project: tap-postgres (0.0.1)
visch@DESKTOP-9BDPA9T:~/git/tap-postgres$ cat pyro
cat: pyro: No such file or directory
visch@DESKTOP-9BDPA9T:~/git/tap-postgres$ cat pyproject.toml
[tool.poetry]
name = "tap-postgres"
version = "0.0.1"
description = "`tap-postgres` is a Singer tap for Postgres, built with the Meltano SDK for Singer Taps."
authors = ["AutoIDM"]
keywords = [
    "ELT",
    "Postgres",
]
license = "Apache 2.0"

[tool.poetry.dependencies]
python = "<3.11,>=3.7.1"
requests = "^2.25.1"
singer-sdk = "^0.18.0"
psycopg2-binary = "2.9.3"

[tool.poetry.dev-dependencies]
pytest = "^6.2.5"
tox = "^3.24.4"
flake8 = "^3.9.2"
black = "^21.9b0"
pydocstyle = "^6.1.1"
mypy = "^0.910"
types-requests = "^2.26.1"
isort = "^5.10.1"
faker = "^15.3.4"

[tool.isort]
profile = "black"
multi_line_output = 3 # Vertical Hanging Indent
src_paths = "tap_postgres"

[build-system]
requires = ["poetry-core>=1.0.8"]
build-backend = "poetry.core.masonry.api"

[tool.poetry.scripts]
# CLI declaration
tap-postgres = 'tap_postgres.tap:TapPostgres.cli'

Dang, I wonder what I was doing wrong. venv dump didnt work, now trying again after clearing poetry’s cache as well. Thank you though, this solves it ofc!

interesting, I haven't had the cache issue bit I guess it makes sense if there's something up in the cache!