Fork of https://github.com/zephyrproject-rtos/Kconfiglib.git https://git.mcdonnell.dev/Kconfiglib.git/atom?h=v12.2.0 2019-06-06T03:32:37Z 2019-06-06T03:32:37Z Ulf Magnusson ulfalizer@gmail.com 2019-06-06T03:10:10Z urn:sha1:fe91f478b5620235b8a462533850afef4731dac0 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") 2019-06-06T03:32:37Z Ulf Magnusson ulfalizer@gmail.com 2019-06-06T03:31:03Z urn:sha1:cf6527e6ae34c808e5209b71817a49b00b7479f4 Make it reflect various output improvements added since it was written (e.g. 'depends on' not being shown on each property). 2019-06-06T03:08:18Z Ulf Magnusson ulfalizer@gmail.com 2019-06-06T03:08:18Z urn:sha1:3a772a68de2320f58e52845bb4babbe66e89d7e2 2019-06-06T02:57:22Z Ulf Magnusson ulfalizer@gmail.com 2019-06-05T11:45:38Z urn:sha1:319f7f0f09a620e7cd9987d4834660598bfb7109 2019-06-04T09:00:13Z Ulf Magnusson ulfalizer@gmail.com 2019-06-04T08:58:52Z urn:sha1:7627bdfac95a4289570f3011840739be20544395 Adds commit 22f2778 ("Mention that the load_config() message is different for replace=False") 2019-06-03T04:55:22Z Ulf Magnusson ulfalizer@gmail.com 2019-06-03T03:37:14Z urn:sha1:102e518d4d9e8132fb258770373b8d4dc8fcf392 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. 2019-06-03T04:50:06Z Ulf Magnusson ulfalizer@gmail.com 2019-06-02T23:55:50Z urn:sha1:bf36f5de0f49d56975b1a844e25484ec385dc971 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. 2019-06-01T04:22:48Z Ulf Magnusson ulfalizer@gmail.com 2019-06-01T04:10:52Z urn:sha1:544888a059d1c066f00e2f0f174fb4199e349f52 Fixes an obscure rsource crash, in commit 92791a3 ("Fix obscure crash with rsource and $srctree pointing to a symlink"). 2019-05-31T00:16:52Z Ulf Magnusson ulfalizer@gmail.com 2019-05-31T00:16:52Z urn:sha1:f60f05c0ea0fcd0557b4e8f29f3b9d9471d011dd Adds commit 175c1f5 ("Leave unchanged output files untouched"). This avoids updating file modification timestamps when nothing has changed, which can make it easier to avoid triggering redundant rebuilds. 2019-05-30T22:08:14Z Ulf Magnusson ulfalizer@gmail.com 2019-05-29T05:29:20Z urn:sha1:175c1f5a363e51a76a7dc1fe807f7c3faf40ab23 Before writing a configuration file or header file, compare the old contents of the file against the new contents. If there's no change, skip the write, to avoid updating the file modification time. This might avoid triggering redundant rebuilds depending on how the build system is set up, and could allow for a simpler setup.