-
Notifications
You must be signed in to change notification settings - Fork 76
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
pushing v5.1.0 to pip #204
Comments
Sorry to nag here about this, but some distros are begging to package a patched 5.0.6, and this is creating breakage in downstream apps. The latest stable release is simply too old. Would you mind pushing a 5.1.0 based on the current master? Or at least maybe a 5.1.0b1? |
👍 |
CC @jhermann |
@jhermann I believe you have the relevant permissions to push to pypi? |
I think this is basically the same sentiment as #213 which now holds the most recent discussion where I lay out that I'm going to put at one last maintenance release (5.1.0) before making it explicit that the project needs a full-time maintainer to take it to the next phase |
in reading this a bit more, I think the more fundamental point is that there are people who depended on |
Hi,
Sorry to intrude with a naïve question. When installing configobj, the latest version is 5.0.6. This version doesn't support validate and I can't install validate either in python 3.7 making the combo configobj==5.0.6+validate incompatible with python 3.7
Is it possible to push 5.1.0 of configobj to pip? This version would basically solve this issue. I wonder if this version is still in beta or not.
The text was updated successfully, but these errors were encountered: