plone / buildout.coredev

Plone Core Development Buildout
http://docs.plone.org/develop/coredev/docs/
74 stars 75 forks source link

Don't use egg caching in GA on Windows #773

Closed wesleybl closed 2 years ago

wesleybl commented 2 years ago

buildout 2 fails on Windows when it has cache of eggs.

Fixes #772

wesleybl commented 2 years ago

By the way, can we use buildout 3 in Plone 5.2?

jensens commented 2 years ago

Strange. But, well, Windows.

mauritsvanrees commented 2 years ago

By the way, can we use buildout 3 in Plone 5.2?

For me, this would be too big a change. It switches from easy_install (well, an internal, hacked-up copy) to pip, which fixes some problems and causes new ones. Also, it is in release candidate status, not final.

Locally: sure, go ahead and use buildout 3, especially on Python 3. Also, if buildout 3 helps for GitHub Actions in a package, I would be happy to use it. But coredev 5.2 and the versions/requirements on dist.plone.org should remain on buildout 2.

Lately, I thought of adding a directory like 52-py3-dev or 52-py3-experimental to dist.plone.org. It would extend the standard Plone 5.2 versions, but have a few updated pins for packages that are meant for Plone 6, but are known to work on 5.2 on Python 3. For example newer plone.restapi and plone.namedfile. An updated zc.buildout and setuptools could be added there. But this may be more for people who know what they are doing, and they may not need such a list of updated versions. :-)