Adopt lock files

[staadecker]

A lock file would prevent issues like the one fixed by #164. Read What is a lock file? and Committing your poetry.lock file for context.

In short, I would eventually like:

1. A lock file committed to the repository to make installations consistent across Pyoframe developers and CI tests.
2. An additional GitHub action that re-runs the tests periodically with the latest dependencies.

I'm waiting for pip to support lock files. PEP 751 was adopted in March; packaging should support pylock.toml imminently; so pip support for lock files should be coming soon...

If I get impatient, I might adopt Poetry or uv instead since they already support lock files.

Todo:

• Add lock file support
• Unpin dev dependencies in pyproject.toml
• Update instructions for using lock file support
• Add CI task to test library against latest versions

[aurelije]

lock file yes, poetry no

thee is no reason for using outdated poetry when uv has won the war for tool to be standard for dependency management, virtual environment, python vm installer and python tools installer. And all that using PEP standards and having performance of rust

[staadecker]

Great points. I'll avoid poetry. uv doesn't plan to adopt pylock.toml from PEP 751 (see reasons), but it might still be worth pivoting to uv on the long-term.