GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||||||||
GeezerVison is showing github.com — Modernize by alexfikl · Pull Request #2 · papis/python-doi ConversationThis updates The commits should be fairly self-contained. Let me know if you spot anything wrong!
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page. All reactions
Author
All reactions
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page.
All reactions
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page.
|
There was an error while loading. Please reload this page.
|
I'm afraid I don't have access to this repo to merge it. @alejandrogallo Any chance you can find some time to give it a look and merge it? 😁 EDIT: As far as I can tell the tests still pass (locally), but it's probably a good idea to re-run the CI anyway before merging. EDIT2: Enabled support for testing on Python 3.13 as well! 😁 |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Trying to use this, I notice I needed to pass Although the Anything left to get this merged @alejandrogallo ? |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
... Actually, it turns out that on my system, this PR suffices to get the tests to pass, with no other trickery needed. I don't know what happened in the last two months to make my bug no longer reproduce, but it seems #3 can be closed without merging it (or merged if we want that redundancy, though we'd probably want to drop the commit introducing |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Ah, I see what happened -- 844fdfd fixed the urls the tests point to, making the tests no longer break |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Just looked at
I think it's ok to change these because they're just checking that the DOI parsing works as expected. However, we might want to add some more tests to check that we manage to follow redirects properly and whatnot. Maybe a follow-up to #3 could go in that direction? |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Yeah, I see it's just checking the https://doi.org/api/handles/ endpoint works as expected. I am trying to investigate getting the redirect code to work for robustness' sake, but OTOH given the 403's the redirected URLs are giving, I'm suspecting some of these sites aren't very scraper-friendly, and so are likely to be difficult to support. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Closed in favor of #3. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.