-
Notifications
You must be signed in to change notification settings - Fork 5
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
PyPI package name #6
Comments
Hey @kislyuk, that sounds like a great idea. Only thing I want to make sure is that any potential active users don't have their stuff broken overnight. The easy part is renaming this package to The hard part is signalling that this is a potentially BC-breaking replacement of the full implementation. A major version bump could be one way, but I guess you wouldn't want to publish 1.0.0 right away? But then we can only do a minor version bump, which totally breaks semver. Worst case, we can just bite the bullet and replace the package with a minor version bump and a big loud notice in the readme. What do you think? |
My proposal would be to begin my release series with v2.0.0 to comply with semver and avoid any ambiguity about the meaning of "v1.0.0". I would also put together a disclaimer about backwards compatibility in the readme/pypi/docs. |
Sounds good, let's do that. Let me know your pypi username, and I'll make you an owner of the package - you can go ahead and make the changes without blocking on me. Thank you, this is making the world a better place :) |
My PyPI username is kislyuk. Thank you! |
And done. Go forth and do good! ;) Also, feel free to remove me as "owner" once all is set. |
New package is up at https://pypi.python.org/pypi/yq! |
Hello,
I would like to provide a lightweight Python package that accomplishes the role of "jq for YAML documents" in a minimalistic way by transcoding YAML to JSON and piping it through jq. For that purpose it would be useful to be able to publish to the "yq" package name on PyPI.
Since you are not intending to maintain this package further, I was wondering if you'd be interested in transferring the package name to me.
Thanks!
The text was updated successfully, but these errors were encountered: