Regression after #800

[KOLANICH]

After #800 got landed setuptools_scm has started breaking https://github.com/ofek/hatch-vcs (pypa/hatch#795) .

78e7d6b - can build itself, breaks hatch_vcs
bf0e813 - cannot build itself, version.py:15, ImportError: cannot import name '_call_version_scheme' from partially initialized module 'setuptools_scm._entrypoints'
45ad9c8 - cannot build itself, version.py:15, ImportError: cannot import name '_call_version_scheme' from partially initialized module 'setuptools_scm._entrypoints'
8e4e22f - cannot build itself, version.py:15, ImportError: cannot import name '_call_version_scheme' from partially initialized module 'setuptools_scm._entrypoints'
4208223 - cannot build itself, version.py:15, ImportError: cannot import name '_call_version_scheme' from partially initialized module 'setuptools_scm._entrypoints'
fd04e24 - cannot build itself, version.py:15, ImportError: cannot import name '_call_version_scheme' from partially initialized module 'setuptools_scm._entrypoints'
91061f9 - cannot build itself, version.py:18 ImportError: cannot import name '_get_ep' from partially initialized module 'setuptools_scm._entrypoints'
770d5dd - works fine

[RonnyPfannschmidt]

should e resolved on master now

[KOLANICH]

No, it's not resolved. I test on https://github.com/python/black and use the command python3 -m build -nwx.

[RonnyPfannschmidt]

ok, now i have a local reproducer and found 2 bugs that need extra tests, will implement tommorow

[RonnyPfannschmidt]

@ofek this comes down to hatch-vcs passing in a empty string, i'll make this something that triggers a deprecation warning and will fail in a year or so

[KOLANICH]

I confirm, that now it works. Thanks for investigating and fixing it.

[RonnyPfannschmidt]

@KOLANICH btw, it is uncommon to have unreleased versions in use, im curious as to what types of pipeline need/want that (setuptools_scm is currently are not set up for true CI , so thee is a certain risk with that)

[KOLANICH]

I just prefer using bleeding edge versions of software to

1. get the latest fixes and features
2. get aware of the bugs affecting me before they are standardized as "features" compatibility to which is carefully conserved ("we don't hide problems" principle, and IMHO bugs should be fixed, not standardized)
3. reduce risk of compromise due to relying on the blob in the package registry that noone audits

Some rare breakages are not considered so bad, but instead are viewed as an opportunity to interfere before bugs are cast in stone as "features". Except of them, just installing the most of Python packages from git works pretty fine and I'm making a package manager as a replacement (in fact not quite a replacement, since it relies on some pip machinery and also pip is used to install the packages the ususal way) for pip with the main focus to be used in CI pipelines.