-
-
Notifications
You must be signed in to change notification settings - Fork 131
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
Local ape version uses whatever tag is latest [APE-114] #90
Comments
I can't see this notice getting read too much since it is hidden in the backlog of issues. I think a note like this belongs in the ^ If we agree on that, let's convert this issue to a ticket item (remove the |
What if we just pinned the issue? |
I agree, seems to be an issue that would be more specific to Contributors and putting in the guide would cut down on the frustration of trying to look for the issue. I'm removing wontfix and making this a ticket to add the language to the |
Just keeping this around as a notice
You might run into issues where you have a local install and are trying to work with a plugin pinned to a specific version.
While the code might be correct, the version will be off because of how
setuptools-scm
uses git tags to generate the latest version.The easy solution to this is simple fetch the tags via
git fetch upstream --tags
and reinstall viapip install .
. You will then have the correct versionThe text was updated successfully, but these errors were encountered: