02:39 <_whitenotifier-5> [fasm] mithro opened issue #54: Figure out why we now have three almost identical workflows - https://git.io/JtMvS

07:28 <_whitenotifier-5> [sv-tests] tgorochowik opened issue #1349: Consider deploying the report using the periodic kokoro runs - https://git.io/JtMOX

07:35 <_whitenotifier-5> [sv-tests] tgorochowik opened issue #1350: Build all the tools using github actions - https://git.io/JtMOj

15:44 <_whitenotifier-5> [fasm] mithro opened issue #56: Publish to PyPi step should be skipped if no authentication secrets are found - https://git.io/JtMiP

16:04 <_whitenotifier-5> [fasm] Mattia9875 opened issue #57: Broken installation due to probable circular import - https://git.io/JtMXe

17:40 <mithro> litghost: I'm wondering if we should use https://pypi.org/project/setuptools-scm/ -- I tried to use it a few years ago and was unhappy with it then but it seems to have improved since then....

17:40 <tpb> Title: setuptools-scm · PyPI (at pypi.org)

17:41 <litghost> I know very little about it. I'm inclined to not add a external dependency to the project itself for this. I just wish python would provide an answer without use having to re-invent the wheel

17:42 <mithro> litghost: Well, if we are about to make an "external dependency" by moving update_version into its own thing....

17:42 <litghost> I meant managed outside

17:43 <litghost> I'm conflicted

17:43 <mithro> Same :-)

17:44 <litghost> I'd say give it a shot

17:44 <mithro> litghost: nmigen seems to use setuptools_scm....

17:44 <litghost> If you can make it work, I'd say let'

17:45 <litghost> let's use it