Feature #11198

Port complex shell scripts into Python

Added by anonym 2016-03-08 02:10:45 . Updated 2020-04-01 09:01:34 .

Status:
Confirmed
Priority:
Normal
Assignee:
Category:
Target version:
2020
Start date:
2016-08-27
Due date:
% Done:

80%

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

https://tails.boum.org/blueprint/Port_shell_scripts_to_Python/

Starter:
Affected tool:
Deliverable for:

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: hefee, muri, segfault, intrigeri (reviewer); kurono?

This will be part of FT work.

Subtasks

Feature #11753: Port complex shell scripts shipped in /usr/local to Python Resolved

100
Feature #11754: Port complex build shell scripts to Python Confirmed

0
Bug #15370: Onion Circuits cannot be started in Tails 3.6~rc1 Resolved

100
Feature #15379: Adjust test suite to Python tails-upgrade-frontend-wrapper Resolved

100
Bug #15845: Port fillram to Python3 Resolved

100

Related issues

Related to Tails - Feature #6452: Factor out stuff into a Tails Python library Confirmed 2013-11-29
Related to Tails - Feature #6145: Factor out stuff into a shell library Confirmed 2013-11-14
Related to Tails - Feature #16103: Handle translations outside wiki/src WRT check_po: document or opt-out Resolved 2018-11-05
Blocks Tails - Feature #16209: Core work: Foundations Team Confirmed

History

#1 Updated by anonym 2016-03-08 02:14:22

  • 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 2016-03-08 02:30:04

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

#3 Updated by sajolida 2016-04-23 08:53:37

  • 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 2016-04-26 02:17:27

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

#5 Updated by anonym 2016-05-22 20:13:23

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

#6 Updated by intrigeri 2016-05-23 08:41:51

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 2016-05-31 21:14:23

  • 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 2016-08-20 13:51:51

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

#10 Updated by sajolida 2016-08-30 14:32:12

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 2016-08-31 00:50:29

> 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 2016-08-31 01:14:22

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

#13 Updated by Anonymous 2017-06-30 11:24:02

  • 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 2017-06-30 11:45:58

  • 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 Feature #11753 and Feature #11754 on the very same day as the comment you were replying to so I think we’re good.

#15 Updated by intrigeri 2017-09-28 12:00:14

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

(as per updated roadmap)

#16 Updated by Anonymous 2018-08-19 08:59:35

  • related to Feature #6145: Factor out stuff into a shell library added

#17 Updated by intrigeri 2018-09-14 08:24:35

  • Description updated
  • Assignee changed from segfault to hefee

(as per summit 2018)

#18 Updated by segfault 2018-09-14 09:26:19

  • Description updated

I still want to be part of this team

#19 Updated by intrigeri 2018-09-14 11:19:10

  • Description updated

#20 Updated by Anonymous 2018-11-13 10:32:24

  • related to Feature #16103: Handle translations outside wiki/src WRT check_po: document or opt-out added

#21 Updated by hefee 2020-02-03 16:43:48

  • Status changed from In Progress to Confirmed
  • Assignee deleted (hefee)

Hey @segfault,

we should properly have some coodination how we go on with this.

#22 Updated by intrigeri 2020-04-01 09:01:12

#23 Updated by intrigeri 2020-04-01 09:01:34

  • Target version changed from 2019 to 2020