Classic confinement request: python-compiler

Title: Classic confinement request: python-compiler

  • name: python-compiler
  • description: pycompile is an ahead-of-time compiler that translates a supported subset of Python into C, invokes the system C compiler, and emits a single standalone native executable. No interpreter is required at run time. Installing this snap provides two equivalent commands, pycompile and python-compiler.
  • snapcraft: https://github.com/ramackersjp/pycompile/blob/main/snap/snapcraft.yaml
  • upstream: https://github.com/ramackersjp/pycompile
  • upstream-relation: Creator
  • supported-category: compilers
  • reasoning: pycompile is itself a compiler: at run time it generates C code from the user’s Python input, invokes the system C compiler (cc) on arbitrary user-specified source and output paths, and links the result into a native executable. Under strict confinement the snap cannot execute the host C toolchain (cc, the linker, libc and system headers) on files outside the snap’s runtime, and the generated output binary must be written to and executed from the user’s working directory. No snapd interface provides access to an arbitrary host C toolchain or allows compiling and linking against the host’s libc, so the required behaviour cannot be achieved with strict confinement. I understand that strict confinement is generally preferred over classic. I’ve tried the existing interfaces to make the snap to work under strict confinement.

I understand that strict confinement is generally preferred over classic.

I’ve tried the existing interfaces to make the snap to work under strict confinement.

This request has been added to the queue for review by the @reviewers team.

Hi @jpramackers

Technical reason on why python-compiler should need classic are understood but please note that classic confinement is a sensitive matter and it is reserved for mature, well-known applications published by mature, well-known entities. As of today, I believe that python-compiler doesn’t meet this criteria because of the following reasons:

  • The project seems to be very fresh, according to the upstream repository

  • The projects seems to have little/none community around according to upstream repository (contributors, issues, PRs, etc.)

  • I could not find evidences that the project has a strong enough user base currently

Considering all these factors, I think python-compiler should not get classic confinement as of now.

Sorry for the inconvenience.