Kconfiglib.git, branch v1.0.0

Add installation instructions for PyPI

2017-09-23T16:32:03Z

Along with the v1.0.0 tag. First version has been pushed to PyPI.

Modernize and update installation files

2017-09-23T15:09:03Z

Preparation for adding to PyPI. Switch to setuptools and add a bunch more metadata. Use semantic versioning (http://semver.org).

Use a separate LICENSE.txt for the ISC license

2017-09-23T12:55:06Z

Packaging preparation. Unspams the README a bit (but spams the tree...). Should make GitHub display the license automatically.

README formatting nit

2017-09-23T12:37:11Z

Switch README format to reStructuredText

2017-09-23T12:34:35Z

In preparation for creating a PyPI package. This is the documentation format PyPI expects. Some automatic conversion workarounds can be found on Google, but keep it simple and eliminate a step. Add a fancy table of contents using ::contents too.

Fix README typo

2017-09-22T07:46:40Z

Explain why _make_and() can return None

2017-09-22T05:58:06Z

Makes ANDs between nonexistent expressions yield a nonexistent expression.

Explain the expression structure clearer

2017-09-22T05:11:56Z

Simplify _expr_to_str()

2017-09-22T05:02:05Z

- Get rid of _sym_str_string(), which was only used here. - Remove 'if expr is None' case that could never trigger - Add a test for printing string symbols, as they are a bit tricky: Default values should not be evaluated to tristate values.

Simplify expression representation

2017-09-21T18:21:00Z

Store simple (, , ) tuples instead of (, [list of operands]) tuples. The thought process behind the original representation was to avoid creating lots of nodes for long X && Y && Z && ... chains that sometimes appear, and possibly speed up evaluation. In retrospect, it's pretty bad, for the following reasons: 1) _make_and() and _make_or() created lots of new merged lists instead of simply reusing the tuples already allocated for the subexpressions. This is slow and memory hungry. 2) Any gain in evaluating long expressions would barely offset slower evaluation of short expressions. 3) The code became more complex. Most importantly, this change makes expressions more straightforward to work with for people peeking into internals.