File tree Expand file tree Collapse file tree 1 file changed +21
-0
lines changed Expand file tree Collapse file tree 1 file changed +21
-0
lines changed Original file line number Diff line number Diff line change @@ -150,3 +150,24 @@ $ git log --follow Lib/compiler | grep ^Author | sed -e 's/<.*>//' | sort | uniq
150
150
1 Author: Barry Warsaw
151
151
1 Author: Amaury Forgeot d'Arc
152
152
```
153
+
154
+ Related Projects
155
+ ----------------
156
+
157
+ Aka "why I took Python2's compiler package and spent all this effort on it
158
+ instead of using something else".
159
+
160
+ * [ PyPy] ( https://bitbucket.org/pypy/pypy ) is the obvious direction of thought.
161
+ PyPy is a very advanced and big project. Somewhere in there a small hadron
162
+ collider may be lurking. But what if you want a simple Python compiler
163
+ without a hadron collider? You may be out of luck to extract it, or at
164
+ least I was.
165
+ * [ YaPyPy] ( https://github.com/Xython/YAPyPy ) - looks absolutely great, but
166
+ its docs miss to explain how to actually run it. I mean, that small part
167
+ of docs (README) which is written in English. There're more docs in Chinese,
168
+ but unfortunately, I can't read it.
169
+ * [ tailbiter] ( https://github.com/darius/tailbiter ) is a great project
170
+ showing how to develop a Python bytecode compiler from scratch, and is
171
+ highly recommended for that purpose. But I wanted to get a "production
172
+ ready" (read: behaving the same way as CPython's) compiler in reasonable
173
+ time with reasonable effort, not write one from scratch.
You can’t perform that action at this time.
0 commit comments