Hy fork
Go to file
Nicolas Dandrimont 387bc0d9f2 Split eval in two steps to allow eval'ing statements
We compile the evaluated operand, separating the body (statements)
from the expression. We then eval() those separately, and return
the evaluated expression.
2013-05-05 20:42:48 +02:00
bin update readme 2013-04-27 20:52:37 -04:00
docs Merge branch 'master' into pr/125 2013-04-21 10:58:08 -04:00
eg Re-indent Hy code using hy-mode 2013-04-28 16:31:31 +02:00
hy Split eval in two steps to allow eval'ing statements 2013-05-05 20:42:48 +02:00
maintainer-scripts Adding in the mant thinger. 2013-04-15 08:37:25 -04:00
tests Add a test for subscript assignment 2013-05-05 20:42:48 +02:00
.gitignore adding build to gitignore 2013-03-06 19:51:10 -05:00
.travis.yml Run setup.py install before running tests 2013-04-20 22:39:58 +02:00
AUTHORS Adding @egenhombre to AUTHORS 2013-04-21 10:53:34 -04:00
LICENSE Removing my name from the license. 2013-04-05 20:04:36 -04:00
Makefile removing site target 2013-04-12 23:46:28 -04:00
NEWS fixing the bits 2013-04-14 22:19:33 -04:00
README.md update readme 2013-04-27 20:52:37 -04:00
requirements-dev.txt Syntax highlight blocks as clj 2013-04-01 12:55:16 -04:00
requirements.txt Adding back Python 2.6. 2013-03-13 20:02:16 -04:00
setup.cfg Adding in some basic bits in 2013-03-02 20:58:58 -05:00
setup.py Forgot these. 2013-03-27 22:19:57 -04:00
TODO note to self, changelog 2013-04-03 20:39:00 -04:00
tox.ini Add flake8 in tox 2013-04-06 21:16:28 +02:00

Hy

Lisp and Python should love each other. Let's make it happen.

Build Status

Hylarious Hacks

Django + Lisp

Python sh fun

Hy IRC bot

OK, so, why?

Well. Python is awesome. So awesome, that we have so many tools to alter the languge in a core way, but we never use them.

Why?

Well, I wrote Hy to help people realize one thing about Python:

It's really goddamn awesome.

Oh, and lisps are neat.

Project