Pete Zaitcev 0f13db30b6 Import directly from the inside of the ring module ... An odd thing happened: when my code did only "from swift.common.ring import Ring", and nothing else, the interpreter looped on the CPU. The import from the top of the ring module is our standard protocol for Ring. It causes no problem in places like container updater or list_endpoints.py. It is a big mystery why it causes Python 3.7.3 to loop, and only in specific circumstances. But we noticed that the recursive import is unnecesasry in this case, so an obviously harmless fix exists. Change-Id: I7373bbb0a50d090d6becf141e5832f8ae98381a4		2020-01-03 18:34:11 -06:00
..
__init__.py	Add license in swift/common/ring	2017-04-18 12:14:01 +00:00
builder.py	Import directly from the inside of the ring module	2020-01-03 18:34:11 -06:00
composite_builder.py	py3: port common/ring/ and common/utils.py	2018-02-12 06:42:24 +00:00
ring.py	py38: Provide readinto() interface for RingReader	2019-10-14 18:00:11 -07:00
utils.py	Add Docstrings to validate_replicas_by_tier	2018-01-19 08:59:17 +00:00