Dustin Dettmer cdb93eefec resolve() appears broken on Python 3.7+ ... On my machine it should have produced: /tmp/ltests-1p0v5z1j/.locks/lock-1631090663.1066182 but instead it produced: /private/tmp/ltests-1p0v5z1j/.locks/lock-1631090663.105848 The mismatch resulted in a hang inside flock. Path .resolve() seems to be causing problems for others as well. It appears the library was not meant to handle complex path situations and isn't maintained as such (see link reference). Since we have already built a full path here anyway, the call to .resolve() appears redundant. Tested on python 3.9.6 on my Mac OS X 11.4 (20F71), Xcode 12.5.1 (12E507) Relevant discussion: https://discuss.python.org/t/pathlib-absolute-vs-resolve/2573		2021-09-10 11:55:50 +02:00
..
__init__.py	pyln.{proto,client,testing}: bump version numbers to match release.	2021-07-30 19:17:47 +02:00
btcproxy.py	Skip following import and skip flask type to mypy code analysis.	2021-08-30 12:12:32 +09:30
db.py	chore: optimize postgres binary lookup	2020-10-27 10:40:52 +10:30
fixtures.py	doc/schemas: getsharedsecret, help, invoice, listchannels, listforwards	2021-06-25 09:49:33 +09:30
utils.py	resolve() appears broken on Python 3.7+	2021-09-10 11:55:50 +02:00