Installing Plone with just pip (without buildout)

[datakurre (Asko Soukka)]

@tkimnguyen

My first question coming to this is why do you think buildout is bad that it needs to be avoided?

I didn't say it's bad (well, it is pretty slow nowadays). Personally, I'm investigating buildoutless build for building containers (either with Docker or with Nix), and it would help also me if there were official requirements.txts maintained

@tkimnguyen

On the other hand, it reminds me of easy_install. I assume there is a reason why we stopped adding add-ons via easy_install. Does your new method avoid those gotchas?

I skipped that era When I did Plone for the first time there was only Products. When I came back, there was already buildout. Yet, I'd guess it would be related to version pins.

@thet

Still, buildout has it’s advantages.

Agreed. mr.developer is definitely more flexible way to manage multiple developed packages than just installing packages in develop mode into virtualenv. Also there is no yet alternatives for creating Plone configuration with buildout (not to mention all the other recipes). (Well, I have now a zope.conf-generator for Nix, but that one is not compatible with this thread

@thet

Does installing via pip mean that no C-optimized but only the Python fallback code is used? (e.g. AccessControl, Acquisition, etc)

That depends on the availability of wheels for those packages. If there is properly build wheel available, that should include optimizations.