Project

General

Profile

Feature #11198

Port complex shell scripts into Python

Added by anonym over 1 year ago. Updated 23 days ago.

Status:
In Progress
Priority:
Elevated
Assignee:
Category:
-
Target version:
Start date:
08/27/2016
Due date:
% Done:

10%

QA Check:
Feature Branch:
feature/11198-python-scripting
Type of work:
Code

Description

Shell scripts are deceptively easy to quickly prototype proof-of-concepts with, but generally result in things with subtle bugs and high maintenance burden. A "real" language, like Python, is not plagued by these kinds of issues.

Make sure to read the blueprint!

team: segfault, kurono


Subtasks

Feature #11753: Port complex shell scripts shipped in /usr/local to PythonIn Progresssegfault

Feature #11754: Port complex build shell scripts to PythonConfirmedkurono


Related issues

Related to Tails - Feature #6452: Factor out stuff into a Tails Python library Confirmed 11/29/2013

Associated revisions

Revision 133eb2b2 (diff)
Added by anonym over 1 year ago

Install the tailslib python library.

This library contains useful stuff for our effort of converting shell
scripts into python.

Refs: #11198

Revision 96d26192 (diff)
Added by anonym over 1 year ago

Install python3-sh.

This library provides nice shell-like facilities, and an easy
interface to calling commandline tools, and so will be highly useful
in our effort to convert shell scripts into python.

Refs: #11198

Revision f34a85b5 (diff)
Added by anonym over 1 year ago

Convert 19-install-tor-browser-AppArmor-profile into python.

An example conversion of one of our shell scripts into python.

Refs: #11198

History

#1 Updated by anonym over 1 year ago

  • Feature Branch changed from https://tails.boum.org/blueprint/Port_shell_scripts_to_Python/ to feature/11198-python-scripting
  • Blueprint set to https://tails.boum.org/blueprint/Port_shell_scripts_to_Python/

#2 Updated by anonym over 1 year ago

  • Related to Feature #6452: Factor out stuff into a Tails Python library added

#3 Updated by sajolida over 1 year ago

  • Assignee set to anonym
  • Target version set to Tails_2.3

We got a pull request from GoodCrypto one month ago but it got no answer so far, so I'm tracking it here for anonym.

https://mailman.boum.org/pipermail/tails-dev/2016-March/010540.html

#4 Updated by intrigeri over 1 year ago

  • Target version changed from Tails_2.3 to Tails_2.4

#5 Updated by anonym over 1 year ago

  • Target version changed from Tails_2.4 to Tails_2.5

#6 Updated by intrigeri over 1 year ago

I'm not sure this qualifies for a point-release with no RC, so perhaps 2.6 would be a more suitable target?

#7 Updated by intrigeri over 1 year ago

  • Status changed from Confirmed to In Progress
  • Priority changed from Normal to Elevated
  • Target version changed from Tails_2.5 to Tails_2.6
  • % Done changed from 0 to 10
  • QA Check set to Ready for QA

I won't take this into a point-release (2.5), so postponing. Still, the initial pull request was sent 2 months ago, so it would be nice to start providing feedback without waiting 3 more months (2.6), so this has a chance to actually go into 2.6 :) Hence, raising priority.

#9 Updated by Dr_Whax about 1 year ago

  • Description updated (diff)
  • Target version changed from Tails_2.6 to 2017

#10 Updated by sajolida about 1 year ago

This is Ready for QA and has been waiting for 4 months now, so I think it still deserves to be on anonym's radar for 2.6 (and not only on the roadmap for 2017).

#11 Updated by intrigeri about 1 year ago

This is Ready for QA and has been waiting for 4 months now, so I think it still deserves to be on anonym's radar for 2.6 (and not only on the roadmap for 2017).

I'll file a subtask about the part that's ready for QA, so we can differentiate between the bigger goal (2017) and the smaller bits (2.6).

#12 Updated by intrigeri about 1 year ago

  • Assignee changed from anonym to sycamoreone
  • QA Check deleted (Ready for QA)

#13 Updated by u 4 months ago

  • Assignee changed from sycamoreone to intrigeri
  • QA Check set to Info Needed

intrigeri wrote:

This is Ready for QA and has been waiting for 4 months now, so I think it still deserves to be on anonym's radar for 2.6 (and not only on the roadmap for 2017).

I'll file a subtask about the part that's ready for QA, so we can differentiate between the bigger goal (2017) and the smaller bits (2.6).

@intrigeri, I can't see this subtask anywhere. May you please add it?

#14 Updated by intrigeri 4 months ago

  • Assignee changed from intrigeri to sycamoreone
  • QA Check deleted (Info Needed)

u wrote:

@intrigeri, I can't see this subtask anywhere. May you please add it?

I've created #11753 and #11754 on the very same day as the comment you were replying to so I think we're good.

#15 Updated by intrigeri 23 days ago

  • Description updated (diff)
  • Assignee changed from sycamoreone to segfault
  • Target version changed from 2017 to 2019

(as per updated roadmap)

Also available in: Atom PDF