Open
Conversation
Contributor
Author
|
@WarrierRajeev @ravipetlur I'm now remembering that there was a PEP issue with a version like |
38c9aa3 to
d3dfa30
Compare
avinassh
approved these changes
Mar 11, 2024
|
Can we get this merged? Adding via |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I'm not sure what the official release process is for this repo, but it's been nearly 2 years since the last release, and 3 months since the latest merge of changes that someone might want to use. Unfortunately it can't just be installed from git because
setup.pyfails due to a missingversion.txtfile. This PR just adds that file and removes it from.gitignoreso it can be installed without a PyPI release, and bumps the version