-
Notifications
You must be signed in to change notification settings - Fork 6
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
Server is down #53
Comments
Thanks for letting me know. App engine dashboard mentions this since 7 days ago:
Also I see PyPI api failures since Feb 16th. I might just archive the recent snapshot and be done with it. |
Understood... All that remained red was Supervisor that is near to their Python 3 release and the Moz tools. Not bad given that there are 619 days until Python 2 end of life. from datetime import date ; print((date(2020, 1, 1) - date.today()).days,
'days until Python 2 end of life.') |
We're back online. Again thank you @cclauss for letting me know. This is the offending line, PyPI deprecated the function: I took some recent download numbers from Big Query https://bigquery.cloud.google.com/table/the-psf:pypi.downloads20180422 using this query:
I then downloaded the JSON, ran the rest of the code using the above data, got the template data that would have been used to render html, saved that, and from now on we're forever using that stale snapshot of data. I added some deprecation and stale data warning to the top of the site. |
Saving the template data to a file I built this final data set from Google Big Query More info at #53
For fresh data, you could do something like meshy/pythonwheels#100. |
... but I think it's fine to say "mission over" and keep it as is. Thank you very much for making this in the first place and helping to get to Python 3! |
I wonder whether the libraries.io API https://libraries.io/api would be a useful substitute? |
(For other folks interested in the PyPI API changes: https://warehouse.readthedocs.io/api-reference/integration-guide/#migrating-to-the-new-pypi and https://warehouse.readthedocs.io/api-reference/xml-rpc/#changes-to-legacy-api may be helpful.) |
@ubershmekel Can you please regenerate the page? I believe there has been some improvement. |
I would rather create a "wall of shame" for still-popular modules who haven't adopted a proper python3 path versus starting this up again. Great job all around on this, I visited this site monthly for ages. It solidified my push to use python3 exclusively in all my projects a long time ago. |
http://python3wos.appspot.com
The text was updated successfully, but these errors were encountered: