- 04 Dec, 2019 34 commits
-
-
Kazuhiko Shiozaki authored
-
Jérome Perrin authored
When buildout encounter an error, program exists with error code 1, this should also be the case when exiting from a debugger session when running with -D option. /reviewed-on !17
-
Jérome Perrin authored
When a recipe is developed in a git working copy, .git administrative database folder should be ignored, like we did with CVS and svn. /reviewed-on !14
-
Yusei Tahara authored
_install_and_load is slow, using cache saves time when there are many sections.
-
Julien Muchembled authored
Contrary to bash, dash filters out environment variables containing '-' characters.
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
Now specified patches are automatically applied on required eggs as well.
-
Vincent Pelletier authored
Useful when recipes generate non-string values to be reused by other recipes.
-
Rafael Monnerat authored
While invoke setup.py certain eggs (like scikit-learn) launch cetain custom builds (for cython) using subprocess and sys.executable. This commit aims to preserve the sys.path over the runs, even if an egg is using subprocess with the same python to build a component of the egg.
-
Rafael Monnerat authored
This commit is part of fixup the "Add setup-eggs option in zc.recipe.egg:develop."
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
Add referred parts' hash strings in __buildout_signature__, that invokes rebuild of a part when one of its (recursive) dependencies are modified. Also remove duplicates and sort entries in __buildout_signature__.
-
Julien Muchembled authored
-
Kazuhiko Shiozaki authored
-
Julien Muchembled authored
Also, updating a part does not put it anymore at the end of the list of installed parts, that was making .installed.cfg too big.
-
Kazuhiko Shiozaki authored
In SlapOS, bootstrap is called each time software release is invoked and we do not want to delete develop-eggs directory. This reverts commit 55d76b34.
-
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
Even though such configuration is wrong...
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
-
Kirill Smelkov authored
Currently only zc.recipe.egg:custom supports setting environment variables, and zc.recipe.egg:develop does not. My motivation for allowing setting environment in :develop is wendelin.core https://lab.nexedi.cn/nexedi/slapos/blob/b5faab3b/component/wendelin.core/buildout.cfg There we have [wendelin.core] part which installs released egg from pypi, and [wendelin.core-dev] part which installs wendelin.core from its latest git version via zc.recipe.egg:develop . The problem is, wendelin.core for setup.py to work, needs git available, and with slapos we usually don't have git available on base system, so we build it by our own and do something like [wendelin.core-dev] recipe = zc.recipe.egg:develop environment = wendelin.core-dev-env [wendelin.core-dev-env] # wendelin.core-dev needs git to build PATH = ${git:location}/bin:%(PATH)s and the problem is environment does not currently work for zc.recipe.egg:develop, and thus git is not found -> build fails. ~~~~ In order to support environment in :develop, we just move environment setting/restoring bits from Custom to Base, and provide Base.install() which uses this bits. Custom & Develop .install() becomes ._install() which gets hooked into Base.install() . I've tested the patch only manually, because currently automated tests are broken in a lot of places for slapos.buildout and zc.recipe.egg . /cc @kazuhiko, @Tyagov
-
Kazuhiko Shiozaki authored
- Support on the fly patches in zc.recipe.egg by ``EGGNAME-patches``, ``EGGNAME-patch-options``, ``EGGNAME-patch-binary`` (or ``patch-binary``) and ``EGGNAME-patch-revision`` options. - Support on the fly patches in zc.recipe.egg:custom by ``patches``, ``patch-options``, ``patch-binary`` and ``patch-revision`` options. (options ``EGGNAME-*`` are also supported as well).
-
Kazuhiko Shiozaki authored
-
Łukasz Nowak authored
In order to have as canonical as possible paths, chomp ../ from filenames and recalculate base.
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
-
Kazuhiko Shiozaki authored
--setuptools-version and --buildout-version options in bootstrap script still have the priority.
-
Julien Muchembled authored
One big issue in commit e129e187 is that the initial value of buildout_and_setuptools_path can cause buildout to use a lot of CPU at startup. The following change would help: def buildout_and_setuptools_path(): r = [get_python_lib(standard_lib=1)] for d in pkg_resources.working_set: d = d.location if d not in r: r.append(d) return r[1:] buildout_and_setuptools_path = buildout_and_setuptools_path() but initializing buildout_and_setuptools_dists also takes time to compute, and it's only used for bootstrap. Because the commit is not required anymore since setuptools 36, it's easier for us to revert partially, so we can keep applying our patches.
-
- 26 Nov, 2019 3 commits
-
-
Jason Madden authored
(cherry picked from commit 18964211252e158f52c52152799cd4fcd34521ba)
-
https://pypi.org/Michael Howitz authored
(cherry picked from commit 73b1377c27d9b4c490792cbdcfc2a2e88d83d3d1)
-
David Beitey authored
PyPI redirects HTTP to HTTPS by default now so using HTTPS directly avoids the potential for that redirect being modified in flight, helping prevent MITM attacks. Fixes #114. (cherry picked from commit fac9979f516fe1b080258f9b367401a8cc1832e8)
-
- 31 Jan, 2017 3 commits
-
-
Jim Fulton authored
[ci skip]
-
Jim Fulton authored
Fixes #326
-
Jim Fulton authored
Mainly to disable it when just trying to get distributions for buildout and setuptools.
-