-
Notifications
You must be signed in to change notification settings - Fork 162
Publishing v0.21.2
to PyPI
#268
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
Comments
I do not have access to publish on PyPI. See: #256 (comment). |
I'm not sure if it's related, but I noticed that pypi is missing the wheel file for the recent versions, eg: https://pypi.org/project/validators/0.20.0/#files |
If you look at 0.20.0...0.20.1 and 0.20.0...0.21.1, we're dropping support for every version below Now this is a huge of number users on GitHub alone. I suspect a majority of them are acquainted with I have a few things in mind, on how to go about addressing it, but I need to know where the author and other collaborators stand. |
If you're a new / returning $ pip install 'git+https://github.com/python-validators/validators.git'
$ pdm add 'git+https://github.com/python-validators/validators.git'
$ poetry add 'git+https://github.com/python-validators/validators.git'
$ pipenv install -e 'git+https://github.com/python-validators/validators.git'
$ rye add validators --git 'https://github.com/python-validators/validators.git' && rye sync Check version: $ python -c "from validators import __version__; print(__version__)"
0.21.2 Please leave a 👍 if latest version of |
Typically all dependencies update and drop the support for previous version of python and this is inevitable. Developers mostly lock their version and this might not be a big issue. These are my thoughts :) |
cc: @kvesteri |
@joe733 is there any way we can reach out to @kvesteri other than here? I suspect he gets lots of notifications and our mentions would get lost in them. |
Published: https://pypi.org/project/validators/ |
The build for v0.21.1 failed, which means the pypi version has not been updated.
Similar to #259
The text was updated successfully, but these errors were encountered: