-
-
Notifications
You must be signed in to change notification settings - Fork 216
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
git file finding will fail if there are no commits #587
Comments
New bug in the date handling Will fix over the weekend |
RonnyPfannschmidt
added a commit
to RonnyPfannschmidt/setuptools_scm
that referenced
this issue
Aug 26, 2021
on a repository without a commit we cannot tell the valid files, so we don't # Conflicts: # src/setuptools_scm/config.py # src/setuptools_scm/discover.py # src/setuptools_scm/git.py # src/setuptools_scm/utils.py # src/setuptools_scm/version.py
RonnyPfannschmidt
added a commit
to RonnyPfannschmidt/setuptools_scm
that referenced
this issue
Aug 26, 2021
on a repository without a commit we cannot tell the valid files, so we don't
RonnyPfannschmidt
added a commit
to RonnyPfannschmidt/setuptools_scm
that referenced
this issue
Aug 26, 2021
RonnyPfannschmidt
added a commit
that referenced
this issue
Aug 26, 2021
…o-commit fix #587 - stop file finding on missing commits
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It appears that this issue is back, in a sense. I'm seeing the same error with version 6.0.1 in a git respository that does not have any commits yet. The installation appears to succeed, but the error isn't handled.
/tmp/test
) andgit init
setup.py
:SETUPTOOLS_SCM_DEBUG=1 python3 setup.py develop
(Without debug mode, the output is the
wheel
warning,running develop
and the following four lines, and then everything fromfatal: not a valid object name: HEAD
onwards.)Versions of the possibly relevant software: Python 3.9.0, setuptools 57.0.0, pip 21.1.3, setuptools_scm 6.0.1, git 2.32.0
Originally posted by @JustAnotherArchivist in #298 (comment)
The text was updated successfully, but these errors were encountered: