envoyproxy/envoy

Figure out a good strategy for managing python version/s

Open

#16,001 opened on Apr 15, 2021

View on GitHub
 (4 comments) (0 reactions) (1 assignee)C++ (5,373 forks)batch import
area/buildhelp wanted

Repository metrics

Stars
 (27,997 stars)
PR merge metrics
 (Avg merge 8d) (378 merged PRs in 30d)

Description

description

some parts of tooling/ci require python3.8 and more generally recent python 3.x versions have syntax incompatibility

for those reasons the envoy-build-image sets python3.8 as the default interpreter

some OS dont have support for this out of the box so we could do with a good strategy for handling this

a couple of ideas in this respect are:

  • use a python_runtime bazel rule to pull in the required py version
  • explicitly set python3.8 in the shebang lines so devs can keep lower versions without having to update-alternatives or similar
  • use a venv runtime (i think this is the least prefered option for various reasons)

Contributor guide

Research direction
Evaluate the proposed strategies (bazel rule, shebang lines, venv) and determine the best approach for managing Python versions across different operating systems.
Tech stack
python
Domain
devops
Issue type
Research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Python
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30