@gotcha has put enormous efforts in the development of the upcoming version 3, which is now using pip.install under its hood instead of setuptools.easy_install.
While @icemac today released a new version 2.13.4 which pins setuptools, as the latter has removed support for easy_install, it is quite possible that this is the final version of the 2.13 line.
So, please take a couple of minutes and test your application with the pre-release of buildout version 3 and report any issues to our issue tracker.
Do you use batou for union.cms? I have some problems on my dev machine to get batou / especially batou scm to work with the latest buildout pre-release, but this maybe be entirely a local problem.
It is great to hear that you all had success with 3.0.0b2. And thanks for the thanks
On our way to a final release, it would be great if you could contact people outside the Plone community that you know still use zc.buildout to ask them to also test the latest beta.
I already spoke to some of them, but the more we people we find the less chances that bugs like the one @jensens found in 3.0.0b1 remain unseen.
The main source of issues I am afraid of is valid eggs built with conventions I did not think of. Most of our Plone packages follow common patterns. This is why I hope that with more diverse sources of packages, the chances of detecting patterns I missed are greater.
Just updated my coredev 6 buildout and ran into this error
No .dist-info directory after successful pip install of /var/folders/q9/g4v63j9s0h122t997shqn3n80000gn/T/tmpl_j44joyget_dist/Pillow-6.2.2.tar.gz
While:
Installing instance.
Getting distribution for 'Pillow==6.2.2'.
Can't remember the header files being a problem so far although brew on installing Zlib says
zlib is keg-only, which means it was not symlinked into /usr/local,
because macOS already provides this software and installing another version in
parallel can cause all kinds of trouble.
I could do an pip install Pillow==6.2.2 without a problem and looking at the traceback buildout seems to get that binary as well .../tmpbfflftx3get_dist/Pillow-6.2.2.tar.gz?
Not sure what I should make of No .dist-info directory after successful pip install of /var/folders/q9/g4v63j9s0h122t997shqn3n80000gn/T/tmpbfflftx3get_dist/Pillow-6.2.2.tar.gz
When I run the buildout below on my Mac, it fetches a wheel rather than a .tgz. Would be worth to debug why you get a .tgz on your machine
[buildout]
parts=pil
[pil]
recipe=zc.recipe.egg
eggs=Pillow
[versions]
Pillow=6.2.2
Can you check the content of what has been installed by buildout when installing Pillow tgz ?
buildout 3.0 relies on metadata found in dist-info directories. There might be other directories that needs to be searched.
We should move this discussion to buildout issues on github. @agitator Can you file what you have found ?
Does anyone know if it will be possible to use Buildout 3 together with a private Pypi server (e.g. devpi + Basic Auth + .pypirc)? In my local tests with Buildout 3, that didn't seem to be possible. With Buildout 2 this worked like a charm.