Deploy an online tool

未关闭
  • 哪里不对？
#18 5 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

@alisianoi 已经在做这个了。

开始于 2017年6月15日。

评估

这个 Issue 还没有评估数据。

描述

This issue will capture progress on making license-expression and boolean.py into online tools.

Transpiling tools that did not quite work:

  1. RapydScript https://github.com/atsepkov/RapydScript
    Lacks support for importing things (like, import __future__), its list of importable modules is here

  2. Batavia https://github.com/pybee/batavia
    The idea here is to compile python to its bytecode and then run it in a javascript vm. Because python bytecode changes from version to version, batavia currently supports 3.4.4 and possibly 3.5.x (their docs state many things). My problem was compiling those pythons on Archlinux and when I finally did a) their test suite did not quite pass and b) it chocked on import __future__.

  3. PyPyJS https://github.com/pypyjs/pypyjs
    The whole thing is complicated and I failed to make it work. Main demotivator: the website offers python 2.7.9 and there is a github issue that indicates python 3 support is stalling.

Transpiling tools that look promising:

  1. Transcrypt https://github.com/qquick/Transcrypt and http://transcrypt.org
    This is currently the only candidate that has a distinct transpiling step (you actually see the .js files as a result) that could be made to work. However, there are problems which are summarized on SO.

  2. Brython https://github.com/brython-dev/brython
    The most laid-back approach: just works, delivers results but sometimes the resulting boolean expressions come out wrong (runtime error).

Transpiling tools that look promising but not yet tried:

  1. Skulpt http://www.skulpt.org/
    It looks similar to Brython, which is why untried.

  2. flexx https://github.com/zoofIO/flexx

  3. https://github.com/alehander42/pseudo-python

  4. https://github.com/alehander42/pseudo

主要语言
Python
星标
74
派生
38
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

aboutcode-org/license-expression 的其他 Issue

查看 aboutcode-org/license-expression 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。