We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I see you copied over the notebook 6 setup.py to nbclassic. Now there are two files with inconsistend metadata in the repository.
The text was updated successfully, but these errors were encountered:
Yep, this confused me as well on conda-forge/nbclassic-feedstock#27
Sorry, something went wrong.
The setup.cfg is only use by the Check Release CI job to generate a hash for the key. The log says e.g.
setup.cfg
key
with: path: /home/runner/.cache/pip key: Linux-pip-0af18be079638b7a6856559a469eb62f0aa39d3065d0668e8b50af56daa98de3 restore-keys: Linux-pip- Linux-pip-
setup.cfg is also bundled in the SOURCES.txt.
SOURCES.txt
Would it be OK to simply remove setup.cfg and use setup.py to generate the hash?
setup.py
Successfully merging a pull request may close this issue.
I see you copied over the notebook 6 setup.py to nbclassic. Now there are two files with inconsistend metadata in the repository.
The text was updated successfully, but these errors were encountered: