Hy fork
4bea6dc59e
Previously, Hy scripts that raised a subclass of IOError would be caught by code intended to deal with IOErrors raised when Hy couldn't import the script itself, resulting in either a misleading "Can't open file" error message, or a misleading TypeError traceback from not being able to format the "Can't open file" message (for IOErrors for which the errno attribute was None). This commit (a straightforward implementation of the idea proposed by @slimetree in #714) introduces a new HyIOError class, raises that when `import_file_to_hst` can't open the file path, and catches it in the `cmdline_handler`. This is believed to fix #513, #714, and #727. |
||
|---|---|---|
| bin | ||
| docs | ||
| eg | ||
| hy | ||
| scripts | ||
| tests | ||
| .coveragerc | ||
| .dockerignore | ||
| .gitignore | ||
| .mailmap | ||
| .travis.yml | ||
| AUTHORS | ||
| CONTRIBUTING.rst | ||
| Dockerfile | ||
| LICENSE | ||
| make.bat | ||
| Makefile | ||
| NEWS | ||
| README.md | ||
| requirements-dev.txt | ||
| requirements-travis.txt | ||
| setup.cfg | ||
| setup.py | ||
| tox.ini | ||
Hy
Lisp and Python should love each other. Let's make it happen. Try it.
Hylarious Hacks
OK, so, why?
Well. Python is awesome. So awesome, that we have so many tools to alter the language 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 awesome.
Oh, and lisps are neat.
(fan art from the one and only doctormo)
Project
- Code: https://github.com/hylang/hy
- Docs: http://hylang.org/
- Quickstart: http://hylang.org/en/latest/quickstart.html
- Bug reports: We have no bugs! Your bugs are your own! (https://github.com/hylang/hy/issues)
- License: MIT (Expat)