Cssutils

Latest version: v2.11.1

Safety actively analyzes 682404 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 20 of 21

0.9a1

- new tokenizer, complete rewrite
* parses strings and comments
* parses unicode escape sequences (see following)
* emits CSS tokens according to spec (update: not all yet (ESCAPE)!)

- renamed module "comment" to "csscomment" and class "Comment" to "CSSComment"
- configurable Serializer instead of pprint
- reimplemented CSSMediaRule


0.8.x
-----

0.8a6

- bugfixes in valuevalidator regarding values of "background-position", thanks to Tim Gerla!

0.8a5

- bugfix in css.Comment: if constructor was called with empty or no cssText an exception was raised, reported by Tim Gerla!
- prepared inline comments run through epydoc and generated API docs

0.8a4

- csscapture.py
* does download linked, inline and imported stylesheets now
* renamed csscapture.Capture to csscapture.CSSCapture
* added options, use ``csspapture.py -h`` to view all options
- cssutils.css.CSSStyleSheet defines ``literalCssText`` property if property
``cssText`` is set. This is the unparsed cssText and might be different to cssText
e.g. in case of parser errors.

0.8a3

- custom log for CSSparser should work again
- calling script cssparser has 2 new options (not using optparse yet...)
cssparser.py filename.css [encoding[, "debug"]]
1. encoding of the filename.css to parse
2. if called with "debug" debugging mode is enabled and default log prints all messages

- cssutils.css.CSSUnknownRule reintegrated and Tests added
- cssutils.Comment reintegrated
implements css.CSSRule, there a new typevalue COMMENT (=-1) is added
- lexer does handle strings *almost* right now...
- bugfixes
- simplified lexer, still lots of simplification todo

0.8a2

- CSSParser may now directly be used from cssutils
cssutils.cssparser as a standalone script does work too.
- css.CSSStyleDeclaration.getPropertyCSSValue(name) implemented
- css.CSSValue updated
- xml.dom.InvalidModificationErr now raised by CSSRule subclasses instead of xml.dom.SyntaxErr in case a non expected rule has been tried to set
- test are updated to the new API and work (not complete and exhaustive though but a bit more than for 0.61)
- bugfixes in some classes due to reanimated tests
- moved module valuevalidator from cssutils.css to cssutils.
Should not be used directly anyway
- split CSSParser in actual CSSParser and utility module used by CSSParser and each css class cssText setting method
- loghandler.ErrorHandler does raiseExceptions by default now. Only CSSParser does overwrite this behaviour. Some tests still need to be looked into...

Page 20 of 21

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.