brent s d7d85c7d9d future proofing is good, but... ... since print() was made a function in py3, i can predict at some point that return will be made a func as well. sure, good. but "return()" *currently* returns an empty tuple. We want to explicitly return None for testing purposes.		2019-12-11 04:33:15 -05:00
..
__init__.py	whoops, circular imports	2019-12-05 18:04:51 -05:00
_common.py	making a LOT of headway on the gi stuff but hitting a namespace issue	2019-11-04 23:18:28 -05:00
block_fallback.py	future proofing is good, but...	2019-12-11 04:33:15 -05:00
block.py	future proofing is good, but...	2019-12-11 04:33:15 -05:00
filesystem_fallback.py	future proofing is good, but...	2019-12-11 04:33:15 -05:00
filesystem.py	future proofing is good, but...	2019-12-11 04:33:15 -05:00
luks_fallback.py	future proofing is good, but...	2019-12-11 04:33:15 -05:00
luks.py	future proofing is good, but...	2019-12-11 04:33:15 -05:00
lvm_fallback.py	future proofing is good, but...	2019-12-11 04:33:15 -05:00
lvm.py	future proofing is good, but...	2019-12-11 04:33:15 -05:00
main.py	whoops, circular imports	2019-12-05 18:04:51 -05:00
mdadm_fallback.py	future proofing is good, but...	2019-12-11 04:33:15 -05:00
mdadm.py	future proofing is good, but...	2019-12-11 04:33:15 -05:00