the mega typo fix commit
Wow! much typos! such fix!
This commit is contained in:
parent
6d095b452c
commit
4f74652c73
@ -29,7 +29,7 @@ Pull requests are great! We love them, here is a quick guide:
|
||||
continue describing the commit in detail
|
||||
|
||||
|
||||
- Finally add yourself to the AUTHORS file (as a seperate commit), you
|
||||
- Finally add yourself to the AUTHORS file (as a separate commit), you
|
||||
deserve it :)
|
||||
|
||||
- All incoming changes need to be acked by 2 different members of
|
||||
|
12
NEWS
12
NEWS
@ -60,7 +60,7 @@ Changes from 0.9.12
|
||||
* "clean" target added to Makefile
|
||||
* hy2py supports a bunch of commandline options to show AST, source etc.
|
||||
* Sub-object mangling: every identifier is split along the dots & mangled
|
||||
seperately
|
||||
separately
|
||||
|
||||
[ Bug Fixes ]
|
||||
* Empty MacroExpansions work as expected
|
||||
@ -88,7 +88,7 @@ Changes from Hy 0.9.11
|
||||
what exactly was added.
|
||||
|
||||
The biggest feature, Reader Macros, landed later
|
||||
in the cycle, but were big enough to warrent a release on it's
|
||||
in the cycle, but were big enough to warrant a release on its
|
||||
own. A huge thanks goes to Foxboron for implementing them
|
||||
and a massive hug goes out to olasd for providing ongoing
|
||||
reviews during the development.
|
||||
@ -267,7 +267,7 @@ Changes from Hy 0.9.6
|
||||
|
||||
* UTF-8 encoded hy symbols are now hy_... rather than __hy_..., it's
|
||||
silly to prefex them as such. (PT)
|
||||
* `j' is no longer always intepreted as a complex number; we use it much
|
||||
* `j' is no longer always interpreted as a complex number; we use it much
|
||||
more as a symbol. (ND)
|
||||
* (decorate-with) has been moved to (with-decorate) (JD)
|
||||
* New (unless) macro (JD)
|
||||
@ -286,7 +286,7 @@ Changes from Hy 0.9.6
|
||||
and jd for making this happen. This solves just an insane number
|
||||
of bugs. (ND, PT, JD)
|
||||
* Eval no longer sucks with statements (ND)
|
||||
* New magic binary flags / mis fixes with the hy intepreter
|
||||
* New magic binary flags / mis fixes with the hy interpreter
|
||||
(WKG + @eigenhombre)
|
||||
|
||||
|
||||
@ -311,7 +311,7 @@ Changes from Hy 0.9.5
|
||||
=============== WARNING: WARNING: READ ME: READ ME: ===================
|
||||
From here on out, we will only support "future division" as part of hy.
|
||||
This is actually quite a pain for us, but it's going to be quite an
|
||||
amazing feautre.
|
||||
amazing feature.
|
||||
|
||||
This also normalizes behavior from Py 2 --> Py 3.
|
||||
|
||||
@ -346,7 +346,7 @@ Changes from Hy 0.9.4
|
||||
|
||||
* Statements in the `fn' path early will not return anymore. (PT)
|
||||
* Added "not" as the inline "not" operator. It's advised to still
|
||||
use "not-in" or "is-not" rather then nesting. (JD)
|
||||
use "not-in" or "is-not" rather than nesting. (JD)
|
||||
* `let' macro added (PT)
|
||||
* Added "~" as the "invert" operator. (JD)
|
||||
* `catch' now accepts a new format: (JD)
|
||||
|
@ -25,7 +25,7 @@ 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.
|
||||
language in a *core* way, but we never use them.
|
||||
|
||||
Why?
|
||||
|
||||
|
@ -1144,7 +1144,7 @@ Example usage
|
||||
; Throw an IOError("foobar")
|
||||
|
||||
|
||||
`throw` can acccept a single argument (an `Exception` class or instance), or
|
||||
`throw` can accept a single argument (an `Exception` class or instance), or
|
||||
no arguments to re-raise the last Exception.
|
||||
|
||||
|
||||
@ -1238,7 +1238,7 @@ while
|
||||
`while` form is used to execute a single or more blocks as long as a condition
|
||||
is being met.
|
||||
|
||||
The following example will output "hello world!" on screen indefinetely:
|
||||
The following example will output "hello world!" on screen indefinitely:
|
||||
|
||||
.. code-block:: clj
|
||||
|
||||
|
@ -387,7 +387,7 @@ for a more complete description.) ``nif`` is an example, something like a numeri
|
||||
where based on the expression, one of the 3 forms is called depending on if the
|
||||
expression is positive, zero or negative.
|
||||
|
||||
A first pass might be someting like:
|
||||
A first pass might be something like:
|
||||
|
||||
.. code-block:: hy
|
||||
|
||||
|
@ -70,4 +70,4 @@ and expression is passed to the correct function.
|
||||
.. warning::
|
||||
Because of a limitation in Hy's lexer and parser, reader macros can't
|
||||
redefine defined syntax such as ``()[]{}``. This will most likely be
|
||||
adressed in the future.
|
||||
addressed in the future.
|
||||
|
@ -500,7 +500,7 @@ Let's take the classic:
|
||||
|
||||
(loop (print (eval (read))))
|
||||
|
||||
Rather then write it like that, we can write it as follows:
|
||||
Rather than write it like that, we can write it as follows:
|
||||
|
||||
.. code-block:: clj
|
||||
|
||||
|
@ -1,6 +1,6 @@
|
||||
#!/usr/bin/env hy
|
||||
;; Copyright (c) Paul R. Tagliamonte <paultag@debian.org>, 2013 under the terms
|
||||
;; of the Expat license, a copy of which you have should have recieved with
|
||||
;; of the Expat license, a copy of which you should have received with
|
||||
;; the source.
|
||||
|
||||
(import sys)
|
||||
|
@ -1855,7 +1855,7 @@ class HyASTCompiler(object):
|
||||
ret, args, defaults, stararg, kwargs = self._parse_lambda_list(arglist)
|
||||
|
||||
if PY34:
|
||||
# Python 3.4+ requres that args are an ast.arg object, rather
|
||||
# Python 3.4+ requires that args are an ast.arg object, rather
|
||||
# than an ast.Name or bare string.
|
||||
args = [ast.arg(arg=ast_str(x),
|
||||
annotation=None, # Fix me!
|
||||
|
Loading…
Reference in New Issue
Block a user