Plone still depends on the "future" (python2&3) python egg

1

Following https://community.plone.org/t/example-of-two-clients-and-a-zeo-server-with-a-pip-installation-of-plone-6/15518 I've found we still install the pypi package future (https://pypi.org/project/future/) which is a compatibility package when you want to use both python2 and python3.

https://dist.plone.org/release/6.0.0b3/constraints.txt
future==0.18.2

Latest version is from October 31 2019 and the last python version compatible is 3.7. It seems to be used in Plone: https://github.com/search?q=org%3Aplone+__future__&type=code

2

__future__ is a built-in module in Python, not related to the future package.

It looks like future is only used in diazo

3

I've created a PR which removes dependency on future in diazo: Replace future with six by petschki · Pull Request #85 · plone/diazo · GitHub ... inspecting the dependencies with plone.versioncheck there are Products.BTreeFolder2 and repoze.xmliter which also depend on future but don't use it in the code anymore. I think it would be fine to remove this dependency there.

1 Like