| Age | Commit message (Collapse) | Author |
|---|
|
Adds commit 58c65e0 ("Make REL_TO_STR public").
|
|
Generally useful, and not likely to need any internal hackery.
|
|
Do 'add = fields.append'. Pointless as an optimization, but shaves some
lines, and obvious in context.
Also add test coverage for __repr__() for string symbols with user
values.
|
|
|
|
|
|
Makes set_value() smarter about saving redundant work, in commit f2ac5e3
("Make set_value() no-change check work for "n"/"m"/"y" strings").
|
|
Worth pointing out explicitly.
|
|
Convert "n"/"m"/"y" to 0/1/2 earlier, so that e.g. sym.set_value("y")
is recognized as a no-op when sym.user_value == 2.
This also helps when loading several configuration files that assign
some of the same symbols, because load_config() calls set_value() with
"n"/"m"/"y".
This could also cut down on the number of times a particular warning is
displayed when loading lots of overlapping configuration files.
|
|
- Reorganize symbol fetching to remove some duplicated _undef_assign()
calls
- Move duplicated assignment warning generation into an
_assigned_twice() helper function
|
|
Might be less confusing in the context of locales.
|
|
Adds commit 0c79d23 ("menuconfig: Be silent when changing LC_CTYPE to a
UTF-8 locale").
|
|
Having LC_ALL=C and the like in Makefiles is probably pretty common, to
get consistent collation and messages from commands and stuff. It
currently makes menuconfig.py spit out a warning about changing the
locale to a UTF-8 locale though.
Just remove the message, and silently change the locale. The Python 3.7
PEP 538 code is silent as well.
|
|
|
|
It's pretty subtle that sym.config_string can be used instead of the
internal sym._write_to_conf variable in client code. Mention it in
comments near where _write_to_conf is used.
Seen client code access _write_to_conf a few times now. No plans to
remove it though, so it'll most likely keep working.
|
|
Tested, works fine.
|
|
Same behavior, simpler.
|
|
Adds a small error message improvement, in commit 49831dd ("Give the
'source ...' line being parsed when a file can't be opened").
|
|
Bit cleaner-looking.
|
|
Helpful when env. variables are involved. Previously only shown when the
file couldn't be found.
|
|
Factors out some common code.
|
|
Weirdly formatted _T_HELP tokens are supported for compatibility with
old versions of the C tools.
Also add a lone '#' after the tricky help text. Some reconsidered
refactoring choked on that.
|
|
Just cosmetic.
|
|
Match the order the flags are defined.
|
|
Adds a genconfig feature that can be used to avoid needless
reconfiguration, and improves the dumpvars output format.
- Commit dd1be54 ("genconfig: Support generating lists of files and
environment vars.")
- Commit f503ea3 ("dumpvars: Make the output format copy-pasteable")
|
|
This can be useful to avoid needless reconfiguration, by checking if any
Kconfig file or environment variable has changed value before running
genconfig.
|
|
Have it write assignments on a single line that can be copy-pasted
before a command.
|
|
Adds commit 443e6bb ("menuconfig: Fix help display on Python 2").
|
|
textwrap.indent() was added in Python 3.3.
|
|
|
|
Do the opposite of what other people are doing and make menuconfig.py
Python 2-compatible. Turns out it's not that tricky after all, and it
makes everything consistently Python 2/3-compatible and streamlines
things.
- Commit 41b5891 ("menuconfig: Get rid of 'nonlocal'")
- Commit b2e211d ("menuconfig: Fall back on getch() when get_wch()
isn't available")
- Commit c3162be ("menuconfig: Only decode curses.erasechar() on Python
3")
- Commit fe6ed99 ("menuconfig: Import print_function for Python 2
compatibility")
- Commit c209188 ("menuconfig: Have hashbang point to 'python' instead
of 'python3'")
- Commit d577865 ("Remove Python 3 menuconfig special-casing from
Makefile patch")
- Commit 319f7f0 ("Update various comments now that menuconfig is
Python 2-compatible")
- Commit 5fbd70e ("Update setup.py now that menuconfig is Python
2-compatible")
Also investigate exactly what the Python version requirements are and tweak
and document things a bit:
- Commit e0baa79 ("Tweak python_requires to 2.7/3.2+")
- Commit 3a772a6 ("Add a section on version compatibility to the
README")
|
|
Make it reflect various output improvements added since it was written
(e.g. 'depends on' not being shown on each property).
|
|
|
|
Many of the utilities need argparse, which was added in 3.2. Kconfiglib
itself is compatible with 3.1.
|
|
Remove the Python 3 installation prereq for windows-curses, and another
comment saying the menuconfig is Python 3 only.
|
|
|
|
Since it's now compatible with Python 2, it can use PYTHONCMD like the
other targets.
|
|
Consistent with the other utilities, and now works even when 'python' is
Python 2.
|
|
|
|
Avoids turning it into a Unicode string on Python 2, which gets messy
when strings are compared.
|
|
Preparation for Python 2 compatibility. Also indirectly makes it
compatible with Python 3.2 and earlier (get_wch() was added in 3.3).
|
|
Preparation for Python 2 compatibility.
|
|
Adds commit 22f2778 ("Mention that the load_config() message is
different for replace=False")
|
|
Handy to know when writing merging utilities.
|
|
|
|
Catch Exception instead, which avoids catching things like keyboard
interrupts.
|
|
Fixes two API issues. Some backwards compatibility breakage was required
for the load_config()/write_config() message change, though the only
effect on most scripts will be less output on stdout unless/until
they're modified.
- Commit bf36f5d ("Improve warning control API (with backwards
compatibility)")
- Commit 55bc8c3 ("Have load_config() and write_(min_)config() return
messages")
Kconfiglib now also makes the version number available:
- Commit 455e366 ("Add kconfiglib.VERSION")
These are longstanding issues. I don't know of any other ones that would
warrant breaking backwards compatibility. Not going on some API changing
spree.
|
|
A wart of the warning control API (enable/disable_*_warnings()) is that
the current warning settings can't be queried. Querying warning settings
is useful in functions that want to temporarily enable/disable some
warning and then put things back to how they were.
kconfiglib.load_allconfig() ran into this, for example.
Make the internal warning control variables public (improve the naming
at the same time), and encourage just setting them directly. Keep the
old API for backwards compatibility.
Also remove _warn_redun_assign() and _warn_override(). They're trivial
and were called in a single place.
|
|
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 >= (12, 0, 0).
|
|
Holds a (<major>, <minor>, <patch>) tuple, e.g. (12, 0, 0).
|
|
Fixes an obscure rsource crash, in commit 92791a3 ("Fix obscure crash
with rsource and $srctree pointing to a symlink").
|
