<feed xmlns='http://www.w3.org/2005/Atom'>
<title>Kconfiglib.git/defconfig.py, branch v14.1.1a4</title>
<subtitle>Fork of https://github.com/zephyrproject-rtos/Kconfiglib.git</subtitle>
<id>https://git.mcdonnell.dev/Kconfiglib.git/atom?h=v14.1.1a4</id>
<link rel='self' href='https://git.mcdonnell.dev/Kconfiglib.git/atom?h=v14.1.1a4'/>
<link rel='alternate' type='text/html' href='https://git.mcdonnell.dev/Kconfiglib.git/'/>
<updated>2020-01-24T20:33:47Z</updated>
<entry>
<title>Use 'python3' instead of 'python' in hashbangs</title>
<updated>2020-01-24T20:33:47Z</updated>
<author>
<name>Ulf Magnusson</name>
<email>ulfalizer@gmail.com</email>
</author>
<published>2020-01-24T20:33:47Z</published>
<link rel='alternate' type='text/html' href='https://git.mcdonnell.dev/Kconfiglib.git/commit/?id=9e0a8d29fa76adcb3f27bb2e20f16fefc2a8591e'/>
<id>urn:sha1:9e0a8d29fa76adcb3f27bb2e20f16fefc2a8591e</id>
<content type='text'>
It's not obligatory for distributions to have a 'python' binary these
days, but 'python3' is likely to be available:
https://www.python.org/dev/peps/pep-0394/#for-python-runtime-distributors.
Change all hashbangs to point to 'python3'.

This will break running

    $ ./script.py

on *nix systems that don't have a 'python3' executable. Changing it to

    $ python script.py

is pretty painless at least.

This change won't break Python 2 when installing via 'pip', because
entry_points creates bounce scripts with their own hashbangs.

The major version will be increased, in case someone looks at the major
version but doesn't install via 'pip'.

Fixes: #89
</content>
</entry>
<entry>
<title>Make help for Kconfig file argument consistent in tools</title>
<updated>2020-01-12T09:33:35Z</updated>
<author>
<name>Ulf Magnusson</name>
<email>ulfalizer@gmail.com</email>
</author>
<published>2019-12-22T17:30:44Z</published>
<link rel='alternate' type='text/html' href='https://git.mcdonnell.dev/Kconfiglib.git/commit/?id=d613b746e8b76bb8733254318591f07303465404'/>
<id>urn:sha1:d613b746e8b76bb8733254318591f07303465404</id>
<content type='text'>
Say 'top-level' instea of 'base'.
</content>
</entry>
<entry>
<title>Add Kconfig.__init__() helper flag for suppressing tracebacks</title>
<updated>2019-12-14T17:12:07Z</updated>
<author>
<name>Ulf Magnusson</name>
<email>ulfalizer@gmail.com</email>
</author>
<published>2019-12-14T17:04:09Z</published>
<link rel='alternate' type='text/html' href='https://git.mcdonnell.dev/Kconfiglib.git/commit/?id=1ec91703ecdb4c369212fabe2ca0a68f040b7697'/>
<id>urn:sha1:1ec91703ecdb4c369212fabe2ca0a68f040b7697</id>
<content type='text'>
Tools that don't use standard_kconfig() currently generate spammy
tracebacks for e.g. syntax errors.

Add a suppress_traceback flag to Kconfig.__init__() for catching
"expected" exceptions and printing them to stderr and exiting with
status 1. Use it to make all tools consistently hide tracebacks.
</content>
</entry>
<entry>
<title>Have load_config() and write_(min_)config() return messages</title>
<updated>2019-06-03T04:50:06Z</updated>
<author>
<name>Ulf Magnusson</name>
<email>ulfalizer@gmail.com</email>
</author>
<published>2019-06-02T16:15:59Z</published>
<link rel='alternate' type='text/html' href='https://git.mcdonnell.dev/Kconfiglib.git/commit/?id=55bc8c380869ea663092212e8fe388ad7abae596'/>
<id>urn:sha1:55bc8c380869ea663092212e8fe388ad7abae596</id>
<content type='text'>
Hardcoding load_config() and write_(min_)config() to write any message
to stdout is awkward, because it means that the message can't be easily
reused when stdout is the wrong place to write it to (e.g. in
menuconfig/guiconfig). This gets extra bad now that there's also the "No
change to ..." message.

Modify load_config() and write_(min_)config() to return the message as a
string instead, and have them always return a message, instead of just
when 'filename' is None and verbose=True. This makes things flexible and
straightforward.

Use the new behavior in menuconfig.py and guiconfig.py. They now show
"No change to ..." when saving a file doesn't modify it.

Tools that want to write messages to stdout should now do
print(kconf.load_config()) / print(kconf.write_config()).

There's no clean way to preserve perfect backwards compatibility here,
but keep accepting the 'verbose' argument and print a deprecation
warning if a value is ever passed for it. That way, scripts will keep
running, though possibly with less output on stdout.

This changes the meaning of the load_config() return value as well,
though I suspect it was only ever used by the menuconfig/guiconfig
interfaces.

The new behavior applies for kconfiglib.VERSION &gt;= (12, 0, 0).
</content>
</entry>
<entry>
<title>defconfig: Add script</title>
<updated>2019-04-27T13:09:08Z</updated>
<author>
<name>Ulf Magnusson</name>
<email>ulfalizer@gmail.com</email>
</author>
<published>2019-04-27T12:16:10Z</published>
<link rel='alternate' type='text/html' href='https://git.mcdonnell.dev/Kconfiglib.git/commit/?id=4f1674fc32224003931af4a74aa18168786ec9a2'/>
<id>urn:sha1:4f1674fc32224003931af4a74aa18168786ec9a2</id>
<content type='text'>
Simple script for initializing the configuration from an existing
configuration file (usually a minimal configuration).

Just copying the minimal configuration to .config would usually work,
due to Kconfig semantics, but having it be a full configuration file
from the start might be handier and less confusing.
</content>
</entry>
</feed>
