jamielennox
Update on project maintenance
A follow-up to #148, I'm stuck awaiting a review of #220. I recall investing a lot of time and energy into getting that patch to an acceptable working state.
@jamielennox Would you consider adding me as a co-owner of the project or handing over the project? I'd really like to avoid depending on an abandoned project or forking this one.
I've heard back on the PEP 541 request. Jamie responded there, so it sounds like the project is actively stale and abandoned. Sounds like it's time to fork the project.
I don't know what the state of the project is but if it is indeed abandoned, responses (and pytest-responses) swapped in pretty easy for me, and is maintained by Sentry.
https://github.com/getsentry/responses
Thanks for the suggestion. I've definitely used responses in other projects. I can't recall if I tried using responses to address the use-case I had in https://github.com/jaraco/jaraco.abode/pull/11.
I can test to see if the repro for #17 has a suitable implementation in responses.
I did test and found that the repro for 17 does indeed pass under responses. In jaraco/jaraco.abode#40, I set out to migrate jaraco.abode to rely on responses instead of requests-mock. There were some nice things I had to lose from requests-mock, but there were some things that responses caught that requests-mock missed (unused responses, bug in cookie handling). Overall, it's a suitable replacement, so I recommend it and will be abandoning this project.