Godefroid Chapelle
Godefroid Chapelle
Done ! https://pypi.org/project/zc.buildout/3.0.0/
I do not understand your question. You will need to provide more context.
I do not use Windows. My guess is that ``buildout.exe`` is the result of the installation by ``pip`` because of the entry point found at https://github.com/buildout/buildout/blob/b5fc31fd63497dc536594ae8e1304f7a7345fd9e/setup.py#L28
On the top of my head, I do think that `buildout` explores the current `eggs-directory` via `pkg_resources` to discover which eggs are already available. (I will need to check that...
AFAIK, those warnings can be ignored. I plan to hide them in next release.
The main reason this bites me is that I use egg cache. I see two ways of improving the situation: 1) emit warnings when using a variant 2) avoid storing...
In buildout 3, version selection when unpinned is still done by code from `setuptools`. That code should be replaced by code that uses `pip` version selection. Hopefully done later
I think so. However, I am not sure that I could wrap my head around the many cases that needed to be tested.
Thanks for the kind words. Are you having those problems on a M1 ? Or classic Intel CPU ?
This sounds like an issue in `setuptools` that got solved in 46.3.0 : https://github.com/pypa/setuptools/pull/2108/ What is the version of `setuptools` that you use ?