[MNT] remove poetry.lock

[fkiraly]

Deletes poetry.lock to remove the burden of maintaining it - the developer workflow of installing pytorch-forecasting[dev] is more general and less complex.

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.19%. Comparing base (6061af6) to head (1f68a8a).
Report is 2 commits behind head on master.

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #1651   +/-   ##
=======================================
  Coverage   90.19%   90.19%           
=======================================
  Files          32       32           
  Lines        4734     4734           
=======================================
  Hits         4270     4270           
  Misses        464      464           

Flag	Coverage Δ
cpu	90.19% <ø> (ø)
pytest	90.19% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[jdb78]

Think the only thing to consider is how in the future we want to detect new releases that are breaking the current tests - having a lock file really helps because dependabot creates PRs automatically, updating the lock file and it is immediately clear which updates to dependencies break the tests.

[fkiraly]

That's an interesting point! I was wondering where in the workflow the poetry.lock would be useful.

Just to clarify:

• does poetry.lock monitor each direct and indirect dependency?
• does it still lock dependencies after the CI is no longer using poetry?

updating the lock file and it is immediately clear which updates to dependencies break the tests.

In my other maintenance workflows, I just run diffs of pip list-s on the first failing CI run, and the last passing CI run. Since testing happens regularly, at least once a week by CRON, only a very small number of versions typically change, and that combined with the error message normally allows to pinpoint the culprit.

For the poetry workflow, I'm just concerned about PR spam...