Page MenuHomePhabricator

Create Execution Environment for Python
Closed, ResolvedPublic

Related Objects

StatusSubtypeAssignedTask
OpenNone
ResolvedNone
ResolvedNone
ResolvedNone
OpenNone
StalledNone
Resolvedcmassaro
OpenNone
OpenNone
OpenNone
OpenNone
OpenNone
DuplicateNone
OpenNone
ResolvedNone
Resolvedcmassaro
Resolvedcmassaro
Resolvedcmassaro
Resolvedcmassaro

Event Timeline

Change 687858 had a related patch set uploaded (by Jforrester; author: Cory Massaro):

[mediawiki/services/function-evaluator@master] Python executor (WIP)

https://gerrit.wikimedia.org/r/687858

Change 687858 had a related patch set uploaded (by Cory Massaro; author: Cory Massaro):

[mediawiki/services/function-evaluator@master] Python executor (WIP)

https://gerrit.wikimedia.org/r/687858

Change 687858 merged by jenkins-bot:

[mediawiki/services/function-evaluator@master] Python3 executor

https://gerrit.wikimedia.org/r/687858

How many of the TODOs do we want to implement before calling this Resolved? None? Some?

Conditioning on requested language will happen automatically with the forthcoming JS patch.

Validation within the executor itself is big enough to be its own task (which I have made).

The others are either optimizations/redesign suggestions or kinda minor, so I feel we can resolve this one.