Drop pkg_resources usage

[gforcada]

See plone/Products.CMFPlone#4126

❓ do we really want to keep testing with python 3.8 and still being compatible with python 2? 😅

[datakurre]

@gforcada I have time to clean this up tomorrow.

It's time to drop Python 2 support.

Also check support for the latest Robot Framework versions.

Since this is one of my pet projects, I'll also look into "latest" weird way to run matrix tests with Nix. Packaging to use pyproject. Possibly uv, etc...

[datakurre]

@gforcada What is the oldest Robot Framework version Plone still needs?

[gforcada]

@datakurre for Plone 6.0 it is pinned to 6.0.2

[datakurre]

Thanks. Didn't get this ready yet, but soonish https://github.com/collective/robotsuite/actions/runs/13662862819/job/38197785795

Learned that uv supports conflicting optional dependency groups in pyproject.toml, which allows locking multiple tested versions in a single lock file.

[datakurre]

@gforcada I released 3.0.0rc1, but I have not tested it with buildout.coredev myself. Please, report, if there are issues caused by dropping setuptools and switching to pyproject.toml. And if it works, I make final release.

I must be pushed to have a Robot Framework talk at PloneConf. There has been lot of development in tooling, and also syntax has nice additions (and should have more before the conf).

https://pypi.org/project/robotsuite/3.0.0rc1/

[gforcada]

@datakurre thanks! 💯

From the top of my head, I remember (@mauritsvanrees ?) that said that a distribution without a setup.py at all is a no go for zc.buildout. So if you removed it completely, we might have a bit of problem there...

But let's create a PR on buildout.coredev to actually check it 👍🏾

[gforcada]

@datakurre a talk would be great indeed!

@MrTango was looking for help/ways to integrate plain playwright python tests directly into our test suite... not sure if that's something you can help with as well 😄

[mauritsvanrees]

AFAIK, having everything in pyproject.toml is fine for Buildout as long as you only install actual releases. But if you need an editable install (so a checkout with mr.developer), then Buildout currently always calls setup.py, so this file is then still required. But I see it is still there, though almost empty, so it is fine. :-)

[datakurre]

I left dummy setup.py into repo for tests with buildout and it also included in sdist. Wheels have never included setup.py I believe. Just report the issues and I’ll fix.

…

Maurits van Rees ***@***.***> kirjoitti 7.3.2025 kello 1.13:  mauritsvanrees left a comment (collective/robotsuite#30) AFAIK, having everything in pyproject.toml is fine for Buildout as long as you only install actual releases. But if you need an editable install (so a checkout with mr.developer), then Buildout currently always calls setup.py, so this file is then still required. But I see it is still there, though almost empty, so it is fine. :-) — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.