Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

setuptools 52.0.0 breaks buildout 2.13.3 installs #543

Closed
icemac opened this issue Feb 1, 2021 · 7 comments
Closed

setuptools 52.0.0 breaks buildout 2.13.3 installs #543

icemac opened this issue Feb 1, 2021 · 7 comments
Labels

Comments

@icemac
Copy link

icemac commented Feb 1, 2021

In pypa/setuptools@2885ca2 setuptools.command.easy_install.main was removed.
It seems to be needed for a successful installation using buildout 2.13.3, so CI of various packages breaks, e. g.

@icemac icemac added the bug label Feb 1, 2021
@icemac
Copy link
Author

icemac commented Feb 1, 2021

It seems that setuptools 52.0.0 dropped easy_install in favor of using pip. (See pypa/setuptools#2544)
Installing wheels does not seem to have this problem, so only packages without a wheel (like zc.recipe.egg) seem to be affected.

@icemac icemac changed the title setuptools 52.0.0 breaks buildout installs setuptools 52.0.0 breaks buildout 2.13.3 installs Feb 1, 2021
@icemac
Copy link
Author

icemac commented Feb 1, 2021

Maybe it's time to deprecate zc.buildout 2.x and get version 3 final. What is still open to call a next release of version 3 a final one?

@icemac
Copy link
Author

icemac commented Feb 1, 2021

cc @gotcha

@jugmac00
Copy link
Member

Maybe it's time to deprecate zc.buildout 2.x and get version 3 final. What is still open to call a next release of version 3 a final one?

Given the dropped support of easy_install, pushing a version 3 release is the only way forward - imho.

@jugmac00
Copy link
Member

jugmac00 commented Mar 2, 2021

Fixed by #549

@jugmac00 jugmac00 closed this as completed Mar 2, 2021
@icemac
Copy link
Author

icemac commented Mar 3, 2021

Hm, should we create a new release now or is there something else to do on the 2.x branch?

@jugmac00
Copy link
Member

jugmac00 commented Mar 3, 2021

Hm, should we create a new release now or is there something else to do on the 2.x branch?

Yes, please! see #551

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants