Log file Viewer

[14:28:43] <exarkun> I followed the pyproject.toml and setup.cfg instructions on https://pypi.org/project/setuptools-scm/ and ... nothing happened. What should I expect setuptools_scm to actually _do_?

[14:32:12] <ngoldbaum> define a __version__ attribute for your package that knows about your VCS

[14:33:27] <ngoldbaum> there’s some

[14:33:51] <ngoldbaum> discussion in the readme about how to get that setup, i think it requires some

[14:33:58] <ngoldbaum> code in your package

[14:41:27] <exarkun> I read the readme and followed the instructions and ran some packaging and install commands and nothing happened

[14:41:57] <exarkun> I just switched to versioneer, it seems to work.

[14:45:24] <ngoldbaum> watch out, it’s unmaintained

[14:46:07] <exarkun> tried to use the "good" option

[14:46:24] <exarkun> making more trouble for myself now to possibly avoid some trouble later doesn't seem productive

[21:42:04] <tos9> exarkun: hm

[21:42:22] <tos9> exarkun: can you show what you did

[21:42:48] <tos9> setuptools-scm does not in fact define a __version__ attribute, so don't expect that (if you want one though it's 1-3 lines of non-setuptools-scm-related things to do)

[21:43:02] <tos9> exarkun: but you mean you ran an install and you got a package with version 0.0.0?

[21:43:21] <tos9> exarkun: If so usually that means you forgot to put use_scm_version = True, and/or to have setuptools-scm in your pyproject.toml

[21:47:54] <tos9> exarkun: if you want a working setup as usual what I can say is "run my crazy package generating script you'll get a working thing and then you can copy the parts you want" -- i.e. `pip install mkpkg && mkpkg foo` will give you a `foo` package that uses setuptools-scm "properly"