Skip to content
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

Update URL and name for python-Levenshtein #86

Merged
merged 4 commits into from
Sep 28, 2023

Conversation

musicinmybrain
Copy link
Contributor

First, update the python-Levenshtein GitHub URL. The current URL corresponding to https://pypi.org/project/python-Levenshtein/ is https://github.com/maxbachmann/python-Levenshtein.

Next, switch dependencies and GitHub URLs from python-Levenshtein to Levenshtein. From https://github.com/maxbachmann/python-Levenshtein/blob/de2b1d5fcd1d4d8fc376f2c6c9d9f8901e68d14b/README.md:

The package was renamed to Levenshtein and can be found here. The python-Levenshtein package will continue to be updated alongside the new package

While both names work for now, it seems best to use the one that the package’s maintainers consider to be the primary name.

@orsinium
Copy link
Member

The current URL corresponding to https://pypi.org/project/python-Levenshtein/ is https://github.com/maxbachmann/python-Levenshtein.

I wonder why 🤔

@maxbachmann do you know why python-Levenshtein now points to your project? It's not the same project, right?

@maxbachmann
Copy link
Contributor

maxbachmann commented Sep 27, 2023

I am the new maintainer of python-Levenshtein. The project is available both as Levenshtein and python-Levenshtein. However Levenshtein is the recommended one (python-Levenshtein is simply an installer for Levenshtein)

@orsinium orsinium merged commit 5f793e1 into life4:master Sep 28, 2023
10 checks passed
@orsinium
Copy link
Member

Thank you both, folks! For the contribution and for making great projects. Keep it up :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants