-
Notifications
You must be signed in to change notification settings - Fork 40
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
missing git tags to corresponding pypi releases #49
Comments
So apparently @wilhelmer has taken over the PyPI, made a new release but there's no sdist, no git tag, no issue tracker on their fork and all the URLs are pointing back there. Sigh. |
Thank you. Unfortunately, since your fork is installed as On top of that, every distribution will probably need to patch |
Oops, didn't know that, thanks for the explanation! So I should rename everything in the fork from |
That's one possibility. Unfortunately, it's not a very good option because we'll effectively have two almost identical That said, it may be worthwhile to ask maintainers of |
Chiming in here in the middle of the workday: I have been negligent in my duties to this project. I am willing to discuss sharing or handing-over ownership of this project. I wrote this years ago when I worked on Google's Pagespeed and "fast webpages" was at the forefront of my mind. I haven't worked on that project - or anything web related even - in almost 8 years. Between work and life responsibilities, this project doesn't get the attention it deserves from me. Couple that with the fact that I am not entirely "proud" of this code anymore, and my motivation to commit time to it is delinquient. If you're interested, let's find a way to make that work. |
Ah wonderful, hi Dave! 👋 I see two solutions here:
|
@mankyd, ping. |
@mankyd ping |
@mankyd Yo! Give me a fat beat! |
@mankyd I'd be ok taking over maintenance of this repo |
Releases published on pypi should also have their corresponding commits tagged in git and published to github for transparency.
Please push missing tags (especially latest)
The text was updated successfully, but these errors were encountered: