| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |\
| |
| | |
Workaround for narrow Python build
|
| | |
| |
| |
| | |
More info: http://stackoverflow.com/questions/7105874/valueerror-unichr-arg-not-in-range0x10000-narrow-python-build-please-hel
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
| |
|
|
| |
I don't remember why I ever thought all that sorting was necessary.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Interpolation is now understood by the parser! It works for
barewords, quoted strings, and both forms of URL.
- Escaped characters are now understood and translated by the parser as
well!
- Rendering strings to CSS attempts to escape them correctly, regardless
of how they were put together.
- The block locator (at least the Python version) is now a little more
aware of CSS escaping.
Unfortunately there are some problems with the C module in this commit,
which I will be promptly fixing.
Conflicts:
scss/blockast.py
|
| |
|
|
| |
http://meyerweb.com/eric/thoughts/2014/06/19/rebeccapurple/
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
As part of this, I also got to (had to) remove the inlining of line
numbers into the source code delimited by NULs; instead, the scanner and
its pending blocks now just track the current line number.
Works on both 2 and 3, too.
|
| |
|
|
|
|
|
|
|
| |
This was happening on py3 anyway, so might as well try to be
Unicode-clean everywhere.
The CSS charset detection is not actually implemented yet.
Also, speedups are now totally broken on py2. Please hold.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Now matches Sass semantics much more closely, and understands
intermediate units in expressions like "1px * 1px / 1px".
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
CSS types now know whether they're expected to be rendered compressed or
not, and so can choose the most appropriate representation.
Colors in particular now try each of several possible renderings and
choose the shortest. (short_colors is still a separate setting, though
compress implies it.)
This removes the need for a full-document regex to shuffle colors
around, solving several problems related to color names that aren't
actually colors. It also kills off several regexes and dicts and brings
us closer to Ruby parity.
|
| | |
|
| |
|
|
|
|
|
|
| |
Variables, functions, and mixins are now all stored within a single
Namespace object, which can easily spin off child namespaces.
Calculator methods no longer need to accept a rule at all, making it
possible to parse and evaluate expressions in a vacuum.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
This was an optimization to short-circuit evaluating any expressions
that don't appear to contain Sass syntax, but it was wrong: the
particular case I ran across was `foo, bar` not being parsed as a list!
Removing it added only 3% to the test suite runtime. We can see about
resurrecting the idea later, after the suite actually passes. :)
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
- FunctionRegistry is now FunctionLibrary, which sounds more like a
thing and less like I had no idea what to call it.
- Built-in functions are all added to the library decorator-style.
- Built-in functions have been split into several smaller modules.
- The stuff in parseutil turns out not to be related to parsing, so it's
been broken apart too.
|
| | |
|
| | |
|
| | |
|
| |
|
