Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
S slapos.core
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Labels
    • Labels
  • Merge requests 26
    • Merge requests 26
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • nexedi
  • slapos.core
  • Merge requests
  • !266

Merged
Created Nov 16, 2020 by Jérome Perrin@jeromeOwner

Ignore user site packages when running buildout

  • Overview 4
  • Commits 3
  • Pipelines 1
  • Changes 2

I had a Theia instance where I installed buildout with pip install -e --user /path/to/checkout and later deleted that /path/to/checkout and this made it impossible to run instance buildout, failing with import error when importing zc.buildout in buildout script.

This is because python load user site packages by default. I believe we don't want this, a broken user site package should not prevent slapos from running buildout.

These changes are about running buildout with PYTHONNOUSERSITE set, so that python ignores user site packages when running buildout.

references:

  • https://docs.python.org/3/using/cmdline.html#envvar-PYTHONNOUSERSITE
  • https://docs.python.org/3/library/site.html#site.ENABLE_USER_SITE
Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Source branch: fix/user-site-packages
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7